Binance is hiring a QA Engineer - Automation Backend Testing, Coding (Fully Remote) in Engineering — Asia. The overview below is synthesized from the employer posting on jobs.lever.co: factual requirements and scope are preserved, but prose is rewritten with editorial context. Verify details and apply via the employer link.
Binance is a leading global blockchain ecosystem behind the world’s largest cryptocurrency exchange by trading volume and registered users. We are trusted by 300+ million people in 100+ countries for our industry-leading security, user fund transparency, trading engine speed, deep liquidity, and an unmatched portfolio of digital-asset products.
Binance is a leading global blockchain ecosystem behind the world’s largest cryptocurrency exchange by trading volume and registered users. We are trusted by 300+ million people in 100+ countries for our industry-leading security, user fund transparency, trading engine speed, deep liquidity, and an unmatched portfolio of digital-asset products.
Responsibilities
Day-to-day scope for the QA Engineer - Automation Backend Testing, Coding (Fully Remote) as described in the posting:
- Own end-to-end quality assurance for BigPay (Fiat) business: requirements review → test planning → case design → execution → release sign-off
- Lead cross-platform testing (App / Web / Backend / Admin), identifying Fiat risk across the full stack
- Drive Fiat feature testing: stream start/end, co-streaming, cross-room connections, playback, compliance — including edge cases like weak network, stream drops, backgrounding, and high concurrency
- Maintain and extend our automation regression framework (Python + pytest + k6)
- Collaborate closely with PMs, engineers, compliance, and operations to close quality loops fast
- Contribute to AI-assisted testing initiatives and team knowledge base
Requirements
Experience and skills the team lists as required:
- At least 3 years QA experience in internet / fintech / Pay/ Payment platform companies
- Automation testing experience (required)
- Comfortable with agile release cycles (2–3 week sprints, grey rollouts, full releases)
- Able to independently own test coverage and review others' test cases/code
- Strong cross-functional communication — you proactively flag risk, not just report bugs
- Python automation basics — read, extend, and maintain existing test scripts (no need to build from scratch)
- Strong sense of ownership: you care about quality, not just coverage number
Why Binance
- Shape the future with the world’s leading blockchain ecosystem
- Collaborate with world-class talent in a user-centric global organization with a flat structure
- Tackle unique, fast-paced projects with autonomy in an innovative environment
- Thrive in a results-driven workplace with opportunities for career growth and continuous learning
- Competitive salary and company benefits
- Work-from-home arrangement (the arrangement may vary depending on the work nature of the business team)
Binance is committed to being an equal opportunity employer. We believe that having a diverse workforce is fundamental to our success.
By submitting a job application, you confirm that you have read and agree to our Candidate Privacy Notice.
Build a standout application
For the QA Engineer - Automation Backend Testing, Coding (Fully Remote) at Binance, reviewers look for concise evidence over buzzwords. Mirror the language of the posting sparingly, quantify support or delivery outcomes, and show how you handled ambiguity, time-zone collaboration and user empathy. Keep your resume to impact, keep your cover note to one page, and link to artifacts — tickets resolved, docs shipped, dashboards owned — that prove you can operate in a fast-moving Web3 team. Prepare to discuss a time you turned a confusing user report into a clear fix and how you measure quality in support and operations.
Web3 hiring values reliability: on-time follow-through, clear writing, and a track record of improving runbooks and tooling. Treat the application as a work sample. For interviews, be ready to walk through how you prioritize across time zones, handle a difficult user, and decide when to escalate versus resolve directly. Show how you document decisions so the next teammate benefits.
In a distributed Web3 org, trust builds through written clarity. Use the cover note to demonstrate it.