Senior Frontend Engineer

Why we need you

Our users are not sitting on MacBook Pros with fibre internet. Many are on a mid-range Android, two bars of network, and a battery at 14%. They're trying to fund a card before a subscription renews, or sell a gift card before the rate changes.

If our web experience is slow, confusing, or breaks halfway through a payment, that's real money and real stress for a real person. We need someone who takes that personally.

What you'll actually be doing

You'll build and maintain the web products people already use — not a greenfield toy app. That means three production surfaces, all talking to the same backend:

· The consumer web app — wallet, gift cards, virtual dollar cards, bills, gadgets, eSIM. This is a Next.js app, used by customers in Nigeria, Ghana, Kenya, and South Africa.

· The partner / B2B dashboard — merchants and developers on our Gift Card API. Vite, React, TypeScript, internationalised.

· The internal admin dashboard — the screens Operations use to help those customers. Vite, React, TypeScript. Privileged.

Some days that's turning a Figma file into components so clean our designers send you voice notes of appreciation. Some days it's figuring out why a page takes 6 seconds to load on a Tecno and getting it down to 2. Some days it's sitting with backend engineers arguing (respectfully) about what an API response should look like.

You'll also work on flows where mistakes cost money: payments, wallet funding, withdrawals, KYC, rates, ₦, $ and ₵ amounts that must not lie.

These apps are containerised and ship to our Kubernetes cluster through Argo CD. You don't need to be a platform engineer. You do need to be comfortable that “done” includes a Docker build and a rollout, not only a green preview URL.

The stack you'll walk into

· React 18/19 TypeScript. You will also read, fix, and improve a large JavaScript Next.js codebase.

· Next.js and Vite + React Router. Comfort with both matters more than a favourite.

· Redux Toolkit for client state. react-hook-form + Yup for forms. Sass. REST against our Node APIs.

· Yarn, ESLint, Prettier, Husky, conventional commits. GitHub pull requests with a real review.

· Docker. GitOps (Argo CD) for what actually reaches production.

You'll probably do well here if

· You've spent 3+ years shipping React that real people use, and you can write TypeScript without fighting it.

· You have production time in Next.js or Vite (both is better). You know your way around Redux, REST APIs, Git, and code reviews.

· You care about what happens after the code ships, not just whether the PR got approved.

· You can explain a technical decision to a PM without making them feel small, and you will ask “but why?” when a ticket has no country, no currency, or no success state.

· You have felt a slow page or a broken amount on a real phone, and you treated it as your problem.

· You use AI tools (Cursor, Copilot, Claude, ChatGPT — whatever works) to move faster, and you still read what they give you. You do not paste customer data (PII) or secrets into a model.

Bonus points if

You've worked in fintech or payments. You've built or maintained a design system. You know your XSS from your CSRF. You've shipped i18n. You've read a Dockerfile or an Argo rollout without panic. You've dabbled in React Native — we have a mobile app, this role is not that job. None of these are dealbreakers. They just make us smile.

This probably isn't for you if

You want a role where tickets come in perfectly specced and you never have to ask “but why?” Or you think performance is something to look at later. Or you've never shipped anything outside a tutorial. Or you only want to write greenfield TypeScript and refuse to touch the JavaScript that already serves customers. 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 in the hands of over a million users — and in the hands of Operations, on admin screens where a bad empty state becomes a support queue.

· Teammates who will actually notice when you do something great.

How to apply (and stand out)

We'll ask for your GitHub or portfolio, plus one short question: tell us about a bug or performance problem that humbled you, and how you fixed it. 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 production rollback, even better.

Application Link: https://forms.gle/L8RV1ssaFBZaioV2A

Applications close: 15 October 2026.