About us
Immersve is a global card-issuing payment institution and principal partner of Mastercard, built to make digital assets spendable in real time on the Mastercard network. We power some of the largest crypto card programs in the world, including Binance, KuCoin, Bitget Wallet and MetaMask; with no bank and no fiat rail involved. We own the full stack, end to end.
Money is evolving. Its moving onchain faster than most financial systems can keep up with. Stablecoins settle in seconds, run around the clock, and don't care about time zones or banks. Immersve is the last mile: the bridge between web3 infrastructure and the Mastercard acceptance network; turning stablecoin balances into money people can spend today, everywhere Mastercard is accepted.
Our partners don't have to teach their users a new way to pay. We handle the plumbing so the experience feels exactly like the one people already know. Even works with Apple and Google Pay.
The next wave of financial institutions won't win by asking customers to change their habits, they'll win by rebuilding what's underneath while everything on the surface stays familiar. That's the problem we're solving at Immersve, and why we're hiring people who want to build it.
The Role
- Owns execution of test efforts across the QA portfolio: partner certifications, market and region validation, release verification, and investigation of reported behaviour. There's strategy work in the role, but execution is the core, and it's what lets the team's strategy capacity grow.
- Absorbs context from the engineering teams as they work. Part of the value of the role is having more of QA present where decisions get made, so knowledge doesn't bottleneck on one person.
- Always thinks about how a test transitions into BAU or the CI pipeline, without letting that limit scope. Exploration and manual testing are critical even for things we'll eventually automate: learn it by hand, then decide what deserves to live forever.
- Exercises judgement about ownership. When it's unclear whether something is ours, the right move is to flag it for routing, not quietly absorb it. Protecting the team's capacity is part of the job.
Qualities we're looking for
- Testing is a natural instinct, not a process you follow. You genuinely want to know whether something behaves the way stakeholders intended, and you go looking rather than waiting to be told what to check.
- Pragmatic. The best testing is the testing that actually gets to happen. You can imagine the ideal coverage, accept what reality allows, make sure everyone understands the gap, and squeeze the most value out of what's left.
- Comfortable working from evidence rather than a UI. A lot of our verification happens through production logs, raw payloads, and third-party webhooks, not through clicking around an app. You don't need to arrive knowing NRQL or ISO 8583, but you need to be happy going to that level.
- At ease in a system you don't fully control. Our stack spans Mastercard, processors, wallet providers, and partners. Much of our testing is observation rather than stimulus-response, and a big part of the job is working out whose side a problem sits on, and saying so with evidence.
- You understand that a correct negative outcome is a pass. In our world "it declined" is often the intended behaviour. We need someone who grades a test against its intent, not against surface success, which filters for testers who think rather than execute scripts.
- Writes clearly. Test results, issue reports, and certification evidence get read by engineers, partners, and compliance. An issue that names its impact is worth ten that describe symptoms.
- Curious about the domain. The work spans card rails, wallet tokenization, regional KYC, and crypto funding, often in the same week. Someone who finds payments-meets-crypto interesting will thrive; someone who wants a stable, well-documented system under test will not.
- You reach for tooling to scale themselves. Our day-to-day runs on AI tooling, internal CLIs, and query languages. We're not asking for an automation engineer, but someone who defaults to amplifying their own effort will fit how the team already works.
Some of our perks
- Flexibility - Work from anywhere in NZ for that perfect work-life balance and 5 weeks Annual Leave; ⚖️
- Support - People first approach 💗 with investment in personal growth, ongoing learning and development; 📚
- Reward - Competitive salary and share options; 📈
- Technology - MacBook Pro (Silicon 🤩) and a home office budget. ⌨️
Application Process
Three interviews and one coding task.
First is a general interview: who you are, who we are, whether this looks like a fit from both sides.
Then the coding task. It's a small API testing exercise, around two hours, in whatever language you're comfortable in. We're interested in how you structure a repeatable test harness and how you communicate what you found, not in polish. We'll send you the repo link when you reach this stage.
The second interview is technical. We'll walk through your code from the task together and dig into other technical questions.
The third is a chance to meet more of the team you'll be working with.
We’d love to hear from you! Please send your CV to careers@immersve.com.
At this stage, we are only considering candidates who are currently based in New Zealand and have valid working rights in New Zealand.
We look forward to hearing from you!
