Senior Quality Engineer

About us

Solflare is a Solana self-custody wallet that puts people in control of their digital assets. Around 4 million users control $20 billion in funds through our wallet.

What started as a team of 6 in 2020 building Solana's first wallet, has grown into a team of 150 worldwide. We’re remote-first, but if you happen to stop by in Zagreb, Croatia, or Belgrade or Novi Sad, Serbia, we have an office you can work from if that’s what you prefer.

Wherever we work, we share the same goal: a Web3 wallet for everyone, with financial freedom in their hands.

The role

This is not a testing role in the traditional sense. We're not looking for someone to catch bugs at the end of the pipeline and hand them back. We're looking for someone to own how quality happens across the entire product. As we like to put it: QA owns the testing strategy, not product quality. Product quality is shared by Product and Engineering.

Your job is to make sure the whole system is set up so that everyone can build confidence in what we ship, from the moment a feature is designed to the moment it's released. That means enabling engineers to test effectively, driving a quality mindset across teams, and building the systems and processes that support it, not just writing and running test cases.

We think about quality the way our users experience the product: as complete journeys, not as a checklist of acceptance criteria. If you read this and think "quality is someone else's problem once I've logged the bug," this role isn't for you. If you think in terms of "can the user actually achieve their goal here, and how do I make the whole team confident that they can," keep reading.

This is a senior role because it demands ownership. Not the word, the behavior: seeing what needs to happen and making it happen without being told, working across Product, Engineering, Data as a matter of course, and taking responsibility for the testing strategy of a feature end to end.

Core responsibilities

• Own the testing strategy for the features and areas you work on. Decide how confidence gets built, which validation happens at which layer (unit, component, integration, API, golden, E2E, accessibility, performance, security, manual, exploratory), rather than defaulting everything to end-to-end testing.
• Get involved early. Join discovery and specification reviews before development starts: clarify assumptions, surface edge cases, identify risks and dependencies, and ask the hard questions ("what happens if the API fails, if permissions are denied, if the user abandons the flow?").
• Design test cases as part of feature development, not after it. Covering user journeys, happy paths, edge cases, error handling, recovery, and regression.
• Enable engineers to own their part of quality. Give developers the test suites, regression packs, environments, and mock data they need to validate their own work before it reaches you, and help build a culture where they do.
• Do the testing that matters. Structured execution of prepared cases plus mandatory exploratory testing to find what predefined cases can't predict, like usability issues, cross-feature interactions, and wrong assumptions.
• Maintain a living view of test coverage per feature. So release decisions are based on measurable confidence rather than "the ticket is closed."
• Continuously improve the automation strategy and the process itself. Reduce flakiness, close coverage gaps, cut repetitive manual regression, and free up time for exploratory, accessibility, security, and performance work.
• Bring AI/LLM tools into the workflow. Use them to speed up test case design, automation scripting, and exploratory testing, and keep pushing the team's QA practices forward as new tools emerge.

Requirements:

• A minimum of a Bachelor's degree in Computer Science or a related field.
• Senior level experience in QA. You've owned quality for real features or products, made your own calls on testing strategy, and been accountable for the outcome, not just executed test plans someone else wrote.
• A genuine ownership and proactivity mindset. You spot gaps and close them, you drive things rather than wait to be assigned, and you don't treat quality as "done" the moment a bug is filed.
• A user- and product-first way of thinking. You test journeys and business outcomes, not just acceptance criteria, and you keep the user at the center of every decision about what and how to test.
• Security mindset.
• Comfort with the "shift-left" idea: quality is built throughout development, not verified at the end.
• Hands-on experience with automation tools such as WebdriverIO, Patrol, Selenium, Cypress, Appium, or Playwright.
• Experience writing backend tests (API, unit, database) and testing RESTful services with tools such as Postman or similar
• Experience with CI/CD platforms such as Jenkins or GitHub Actions.
• We prioritise strong automation skills, but if your background is mostly manual, a proactive attitude, a solid technical base, and a real drive to pick up automation quickly - will still get our attention.

Nice to have:

• Experience in web3 or fintech, or anywhere you've tested products that handle real money. When money is on the line, there's no room for "probably fine," so it sharpens your attention to detail and your instinct for edge cases in a way that carries over well here.
• Experience with testing across multiple layers (API, integration, golden/screenshot, performance, accessibility).
• Experience with security testing

You might not like it here…

But you might love it. Working at Solflare comes with trade-offs, and we’re open about them.

Crypto moves fast, and our priorities can shift with it. We launch new features and rethink existing projects as our users’ needs evolve, in bull and bear markets alike. That means a project you expected to work on may give way to a more pressing priority. We understand this can be energizing if you can adapt and reset as you go, and frustrating if you prefer long-term predictability.

We also highly rate how people work together. Yes, individual work matters, but so does helping others succeed. We share responsibility for the outcome, and we share credit for the wins.

Our remote-first setup gives you flexibility over how you work. It also means owning your role and proactively communicating with your team, not waiting for check-ins or constant direction.

A Web3 background isn’t a must, but interest in Solflare and the industry is. Using the product, asking questions, and contributing ideas is part of every role.

You don’t have to prefer this setup. But understanding it should help you decide whether you’d enjoy working here.

Millions already use what we build. Help shape what comes next. Apply below, or check out our careers site to learn more about our culture and benefits.