Engineering
QA Engineer
Break Duel before players do. Casino, sportsbook, PvP, payments — you own the confidence that ships with every release.
- Department
- Engineering
- Location
- Remote
- Type
- Full-time
- Level
- Mid
- Posted
- 1 Apr 2026
The role
You are the last line before players. Every game launch, every promo, every payment change goes through you, and ‘it worked on staging’ is not a result.
This is not a scripted-regression role. You decide what’s worth testing, build the automation that keeps it honest, and chase every issue until it’s actually dead.
What you’ll do
- Own the test strategy across casino, sportsbook, PvP games, and live experiences
- Build and maintain end-to-end automation that runs on every release
- Test payment flows exhaustively — deposits, withdrawals, edge cases, failure modes
- Verify game math against theoretical models: RTP, hit frequency, bonus triggers
- Validate provably fair verification end to end from the player’s side
- Triage production issues, reproduce them, and drive them to a fix
- Improve the process, not just the ticket queue
What you’ll need
- 3+ years in QA for web or mobile products, ideally gaming, gambling, or fintech
- Strong automation skills — Playwright, Cypress, or equivalent, with real suites you maintained
- You test payments properly: partial failures, timeouts, retries, double-submits, stuck withdrawals
- Comfortable reading logs, network traces, and API responses rather than filing ‘it doesn’t work’
- Understanding of RTP configs, bonus mechanics, and how a promo goes wrong
- Crypto-comfortable. You can test a deposit flow without asking what a confirmation is.
- Relentless. A bug you raised once and never followed up on is a bug you didn’t find.
Come find what everyone else shipped past.
The stack
- Playwright
- TypeScript
- Postman
- CI/CD
What Duel offers
- Remote-first work from anywhere
- Direct to founders no reporting chains
- Crypto payouts paid how you want
- Real ownership own a surface end-to-end
- Ship weekly iterative release cycles
- Build the function most teams start at zero