What is Bitrefill?
Bitrefill lets people spend crypto on real stuff: gift cards, mobile top-ups, subscriptions, bill payments. 180+ countries. Profitable since launch. Over 12 years in and still building.
The team is about 90 people, fully distributed. You'd be joining QA, which is small, hands-on, and in the middle of building out test automation infrastructure. Few meetings. Lots of autonomy.
The job
Our QA team is shifting from manual testing toward automated, AI-augmented workflows. The infrastructure is already in place: E2E web testing frameworks, a mobile test automation tool, an internal MCP orchestration layer, and a test management platform integrated via API. The tooling exists. What's missing is someone dedicated to writing, maintaining, and scaling the automated test suites that sit on top of it.
Right now, test automation competes with QA planning, manual execution, and tooling development. We need someone who can own regression coverage, shrink manual test cycles, and free up the rest of the QA team to focus on strategy, exploratory testing, and pushing our AI-driven QA work forward. We're hiring an SDET: a QA engineer who is also a real developer.
This is a mid-level role, but it's central to how QA works at Bitrefill going forward. Early months will be heavier on building. That shifts toward maintenance as things stabilize. The role will evolve as the team and tooling mature. That might mean picking up dev work beyond QA, depending on where the needs are.
What you'll do
- Author and maintain E2E automated tests with Playwright and Maestro.
- Build out regression, smoke, and sanity suites for critical flows: checkout, payments, gift card redemption, account management
- Integrate automated test execution into CI/CD so tests run on every deployment to staging
- Work with our internal tooling (MCP server) to support API-driven test case management in Qase
- Hunt down and fix flaky tests. Improve stability and execution speed
- Collaborate with developers to understand new features and turn requirements into automated coverage
- Contribute to test planning, risk assessments, and the ongoing question of what to automate vs. what to test manually or exploratively
- Report on test results, coverage gaps, and automation health
Who you are
Experience
- 2-4 years writing and maintaining E2E automated tests. Actually writing them, not watching someone else do it
- Coding skills beyond test scripting, you come from a dev background and test automation is where you apply it
- Already using AI tools and agentic clients (Claude Code, Codex, Cursor, or similar) to write and debug tests, because it makes you faster, not because someone told you to
- Strong experience with at least one modern test automation framework (Cypress, Playwright, Selenium, or similar). Solid web scraping or automation experience counts too
- Mobile test automation experience or genuine interest (Maestro, Appium, Detox, or similar)
- Comfort operating in early-stage QA environments where process isn't fixed: you'll help define what ”done” means
- Comfortable with JavaScript/TypeScript
- Dev experience that leans toward backend and infrastructure
- Experience with API testing (REST, request/response validation)
- Familiar with CI/CD concepts and running tests in pipelines
- Solid understanding of test workflows: cases, suites, runs, reporting
Nice to have
- Experience with Spur or Maestro specifically
- Experience with test management tools and APIs (Qase, TestRail, or similar)
- Interest in Bitcoin/crypto, or experience testing payment/fintech products
- Experience testing e-commerce or marketplace platforms
Mindset
- Self-driven. Comfortable owning your work in a small, remote team
- You see flaky tests as a problem to solve, not a fact of life
- Curious about how AI is changing QA. Excited about AI-augmented workflows, not intimidated by them
- You write solid automation code today and you're already thinking about how you'll work differently tomorrow
