QA Engineer at FairMoney in Lagos, Lagos, Nigeria

FairMoney is a pioneering mobile banking institution specializing in extending credit to emerging markets. Established in 2017, the company currently operates primarily within Nigeria, and it has secured nearly €50 million in funding from renowned global investors, including Tiger Global, DST, and Flourish Ventures.

In alignment with its vision, FairMoney is actively constructing the foremost mobile banking platform and point-of-sale (POS) solution tailored for emerging markets. The journey began with the introduction of a digital microcredit application exclusively available on Android and iOS devices. Today, FairMoney has significantly expanded its range of services, encompassing a comprehensive suite of financial products, such as current accounts, savings accounts, debit cards, and state-of-the-art POS solutions designed to meet the needs of both merchants and agents.

FairMoney thrives on its diverse workforce, bringing together talent from over 27 nationalities. This multicultural team drives the company’s mission of reshaping financial services for underserved communities.To gain deeper insights into FairMoney’s pivotal role in reshaping Africa’s financial landscape, we invite you to watch informative video.

About the role

Our mobile apps are how millions of people access credit and move money. When something breaks, it’s

someone’s disbursement or someone’s repayment.

You’ll shape how we test mobile: the regression process, the automation suite, and how we use AI tooling

to cover more than a small team otherwise could.

What you’ll do

• Own pre-release regression and validation for iOS and Android, and make the release readiness call

• Build and maintain our mobile automation suite, and get it running in CI against every release candidate

• Decide what gets automated and what stays manual, and keep the suite reliable enough that people trust it

• Design end-to-end coverage across our core user journeys

• Exploratory testing on high-risk changes: interrupted flows, dropped connections mid-transaction, unusual account states

• Test on real devices, including low-end Android and poor network conditions.

• Use AI across the testing cycle: generating test cases from specs, drafting automation with coding agents, triaging crashes and clustering support tickets at volume, summarizing logs during exploratory sessions

• Audit AI-generated adversarial tests

• Verify fixes and confirm nothing new has broken

• 5+ years mobile QA, iOS and Android, as your primary discipline
• Strong experience building and maintaining automation suites. Maestro, Appium, Espresso or XCUITest,
• with maintainable code in Kotlin, Swift, Python or TypeScript
• CI/CD experience and the ability to keep a suite stable
• Judgement on what to automate. The failure mode we’re avoiding is a slow flaky suite nobody trusts
• Hands-on experience using AI tooling in testing work, and the judgement to tell where it helps from where it produces confident nonsense
• Experience testing on low-end Android devices and poor networks
• You diagnose before escalating: adb/logcat, Xcode console, Charles or Proxyman
• API-level testing
• Exceptional bug reports. No engineer has come back to you asking for basic details
• Strong exploratory instinct. You can explain why you looked somewhere, not just what you found
• Fintech, payments or lending background
• Clear written communication

Soft skills

• Sound judgement under pressure. You can hold a release decision when a senior stakeholder is pushing back, state the risk plainly, and let it escalate without it becoming personal
• Adversarial about the product, generous with the people building it. Engineers should want you looking at their work
• Ownership. You don’t wait for a queue of assigned tickets. You find the gap and close it
• Influence without authority. Much of this role is getting other teams to change how they work, which is done with evidence and relationships rather than process
• Curiosity and persistence. You keep asking what happens if, long after the checklist is done, and you’ll chase an intermittent bug on one specific device until you have it
• User curiosity. You read support tickets and app store reviews, because that’s where the real problems surface first
• Comfortable with ambiguity. We’re building this function as we go, and parts of it don’t exist yet

• Private Health Insurance
• Paid Time Off
• Pension Plan
• Work From Home
• Training & Development

Recruitment Process

• Screening call with a member of the recruitment team for 30 minutes.
• Technical interview with members of the Engineering team for 45-60 minutes.
• Interview with key stakeholders for 45-60 minutes.