About Immersve

Immersve is a global payments company and Mastercard principal member, 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 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 between web3 infrastructure and the Mastercard network, turning stablecoin balances into money people can spend today, everywhere Mastercard is accepted, including Apple Pay and Google Pay.

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. The next wave of financial institutions will win by rebuilding what’s underneath while everything on the surface stays familiar. That’s the problem we’re solving, and why we’re hiring people who want to build it.

The role

• Own test execution across our QA portfolio: partner certifications, market and region validation, release verification, and investigating reported behaviour. There’s strategy in the role, but execution is the core, and it frees up the team to do more strategic work.
• Absorb context from the engineering teams as they work. Part of the value of this role is having QA present where decisions get made, so knowledge doesn’t bottleneck on one person.
• Think about how each test moves into business-as-usual or the CI pipeline, without letting that limit scope. Exploratory and manual testing matter, even for things we’ll eventually automate: learn it by hand, then decide what deserves to live forever.
• Use good judgement about ownership. When it’s unclear whether something is ours, flag it for routing rather than quietly absorbing it. Protecting the team’s capacity is part of the job.

What we’re looking for

• Testing is an instinct, not a process you follow. You want to know whether something behaves the way people intended, and you go looking rather than waiting to be told what to check.
• Pragmatism. The best testing is the testing that actually happens. You can picture the ideal coverage, accept what reality allows, make sure everyone understands the gap, and get the most value out of what’s left.
• Comfort working from evidence, not a UI. Much of our verification happens through production logs, raw payloads and third-party webhooks. You don’t need to arrive knowing NRQL or ISO 8583, but you need to be happy working at that level.
• Ease in a system you don’t fully control. Our stack spans Mastercard, processors, wallet providers and partners. A lot of our testing is observation rather than stimulus and response, and a big part of the job is working out whose side a problem sits on, and showing the evidence.
• An understanding that a correct negative outcome is a pass. In our world, “it declined” is often the intended behaviour. You grade a test against its intent, not against surface success.
• Clear writing. Test results, issue reports and certification evidence are read by engineers, partners and compliance. An issue that names its impact is worth ten that describe symptoms.
• Curiosity about the domain. The work spans card rails, wallet tokenisation, regional KYC and crypto funding, often in the same week. If payments meeting crypto interests you, you’ll thrive. If you want a stable, well-documented system under test, this isn’t it.
• A habit of reaching for tools. Our day-to-day runs on AI tooling, internal CLIs and query languages. This isn’t an automation engineering role, but you’ll fit best if your default is to amplify your own effort.

Perks

• Flexibility: work from anywhere in New Zealand, with five weeks’ annual leave.
• Support: a people-first approach, with investment in your growth, learning and development.
• Reward: a competitive salary and share options.
• Kit: a MacBook Pro and a home office budget.

How to apply

Our process is three interviews and one coding task.

• General interview: who you are, who we are, and whether this looks like a fit from both sides.
• Coding task: a small API testing exercise of around two hours, in whatever language you’re comfortable with. 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.
• Technical interview: we walk through your task together and dig into other technical questions.
• Team interview: a chance to meet more of the people you’ll be working with.

We’d love to hear from you. Send your CV to careers@immersve.com.

At this stage, we’re only considering candidates who are based in New Zealand and have the right to work here.

Apply now →