Solflare
Senior Quality Engineer
Remote role where the employee must remain based in a particular country.
Listed for Serbia
From the employer's advert: 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. 
Employer listed it 13 days ago · Added 12 days ago
Listed for 5 days before it closed.
This job has closed
Solflare has taken this listing down, so it is no longer accepting applications. The details below are kept for reference only.
Browse open rolesSalary
Not stated
Location
Listed for Serbia
Timezone
Not stated
Contract
Full-time
Experience
Senior
Category
Software
The employer did not publish a salary, and we have too few comparable roles to estimate one.
What the advert says
Quoted word for word from the employer's advert. Where it says nothing, we say so.
- Working hours
- Not mentioned in the advert
- Where you can work from
What started as a team of 6 in 2020 building Solana's first wallet, has grown into a team of 150 worldwide.
- Contract
- Not mentioned in the advert
- Experience asked for
- Not mentioned in the advert
- Pay
Around 4 million users control $20 billion in funds through our wallet.
Remote flexibility
Work from home
This is a remote role, but the employee must be based in Serbia. It is work from home rather than work from anywhere.
What the employer says
- Source listing states candidate location: "Belgrade, , Serbia, Belgrade, rs, Remote"
What Nomaders makes of it
- Residency required in Serbia
- Payroll and tax are likely handled in that country only
The quotes above are the employer's own words; the reading is ours. Always check the original listing and employment terms before working from another country.
Before you apply
Questions worth asking: Nomaders interpretation
- The advert does not say whether this is employment or a contractor arrangement. Ask, as it affects tax and benefits.
Produced automatically from this advert's text; not reviewed by a person. The employer's own page is the final word.
About the role
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.
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.
Benefits
No benefits package published with this listing. Ask about it at first interview.
Applying
This listing has closed, so there is no application link. The details above are kept for reference only.
Found 13d ago. Last checked 17 Nov. Always confirm the details on the original posting, salary and location can change after publication.
Listing sourced from Company boards.
Similar open jobs
This role is closed, applications are no longer accepted.