Senior Quality Assurance Engineer (Remote)

Why we need you

• Our users don’t file bug reports. They just leave. Many are on a mid-range Android, two bars of network, and a battery at 14%. They’re funding a card before a subscription renews, selling a gift card before the rate changes, or buying data with the last money in their wallet.
• If a button double-submits, a balance shows the wrong figure, or a payment says “failed” when it went through, that’s real money and real stress for a real person. We need someone who finds those problems before our customers do, and takes it personally when one slips through.

What you’ll actually be doing

• You’ll own quality across products people already use every day, not a demo app. That means testing across iOS, Android and web, covering:
• The consumer app: wallet, gift cards, Virtual Dollar Cards, bills, gadgets, eSIM. Used by customers in Nigeria and Ghana.
• The partner / B2B side: merchants and developers on our Gift Card API, who need endpoints that behave the same way every single time.
• The internal admin dashboard: the tools Operations use to help customers. Privileged, sensitive, and not a place for surprises.
• Some days that’s writing test plans for a new feature before a single line of code exists. Some days it’s building automated suites so the team stops manually clicking through the same flows every release. Some days it’s testing a withdrawal on a slow network, killing the app halfway, reopening it, and checking whether the money still tells the truth.
• You’ll test flows where mistakes cost money: payments, wallet funding, withdrawals, KYC, rates, card funding with Naira and stablecoins, and ₦, $ and ₵ amounts that must be right to the last kobo.
• You’ll also help shape how we ship. Our apps go to production through a CI/CD pipeline into Kubernetes via Argo CD, and you’ll make sure quality checks are built into that path, not tacked on at the end.

You’ll probably do well here if

• You’ve spent 5+ years in QA, with real time on both manual and automated testing for apps people use.
• You write automation code that other engineers can read and maintain, and you know which tests are worth automating and which aren’t.
• You think in edge cases: no network, slow network, two taps, expired session, wrong currency, empty state, the partner that never responds.
• You can write a bug report so clear that an engineer fixes it without asking a single follow-up question.
• You can push back on “let’s just ship it” with evidence, not panic, and you know when a risk is acceptable.
• You care about what happens after release, not just whether the test run was green.
• You use AI tools (Cursor, Copilot, Claude, ChatGPT, whatever works) to write tests and move faster, and you still check what they give you. You do not paste customer data (PII) or secrets into a model.

The tools you’ll walk into:

• Web automation with [confirm: Cypress / Playwright / Selenium].
• Mobile testing on iOS and Android with [confirm: Appium / Detox / Maestro], plus real devices, including the cheap ones our users actually own.
• API testing with Postman (or similar) against our Node.js REST APIs and partner webhooks.
• Performance and load testing with [confirm: k6 / JMeter].
• Bug tracking and test management in [confirm: Jira / ClickUp]. GitHub pull requests. CI pipelines where your tests actually run.

Bonus points if:

• You’ve tested fintech or payment products.
• You’ve set up a test automation framework from scratch.
• You’ve done security testing or know your OWASP Top 10. You’ve tested in-app purchases, KYC flows or card payments.
• You’ve worked with feature flags or staged rollouts.
• You’ve built QA into a CI/CD pipeline. None of these are dealbreakers. They just make us smile.

This probably isn’t for you if:

• You think QA means clicking around for an hour before release.
• Or you’d rather report a bug than help understand why it happened.
• Or automation feels like someone else’s job. Or “works on my phone” sounds like a sign-off. No shade. Just not the fit.

What’s in it for you

• Fully remote, Nigeria-based. Your commute is from bed to desk (or bed to bed, we don’t judge).
• HMO. Annual leave. Work equipment and a learning budget.
• Your work protects the experience of over a million users, plus the Operations team who rely on our tools working properly.
• Teammates who will actually notice when you do something great (including the bugs you caught that nobody ever saw).

Application Closing Date
28th october, 2026.

How to Apply
Interested and qualified candidates should:
Click here to apply online

How to apply (and stand out):

• We’ll ask for your GitHub, portfolio, or a sample of your test work, plus one short question: tell us about a bug you caught before it reached users, or one that got past you, and what you changed afterwards.
• Three to five sentences is plenty.
• This is the part we read most closely, so skip the generic answer. If it involved money, a slow device, or a release you had to stop, even better.

Share this job: