QA Engineer
AI summary
FairMoney, a Nigerian fintech platform, is hiring a QA Engineer to own mobile testing across iOS and Android. You will build and maintain the automation suite, run pre-release regression, use AI tooling to scale coverage, and make release-readiness decisions. The role suits an experienced mobile QA professional comfortable testing on low-end devices and poor networks.
- Own pre-release regression and release-readiness decisions for iOS and Android
- Build and maintain the mobile automation suite running in CI/CD
- Use AI tooling across the testing cycle, from test generation to crash triage
- Test on real low-end Android devices and poor network conditions
- 5+ years mobile QA experience with iOS and Android required
- Fintech, payments, or lending background is a plus
AI job guide
Use this guide to check salary signals, requirements, documents, application steps and safety before you apply.
AI salary guide
Not enough public dataNot enough public salary data is available for this exact role. Before applying, prepare to ask about gross pay, benefits, contract length, probation period, transport and any allowances.
Can you qualify for this role?
- Required5+ years of relevant experienceThe job post includes a minimum experience signal.
- PreferredPractical evidence in QA Engineer, Mobile Tester, Automation EngineerThe tags and summary point to skills connected with this role.
- RequiredAvailability to work in Not specifiedThe vacancy is associated with this location.
Documents to prepare
- Likely requiredUpdated CV
- Role specificCover letter or short employer message
- OptionalProfessional references
- VerifyID or passport only after verifying the employer
Application tips for this job
- Place your strongest QA Engineer evidence in the first half of your CV.
- In your cover letter or employer message, connect your experience to FairMoney and the role in Not specified.
- Add concrete examples related to QA Engineer, Mobile Tester, Automation Engineer, ideally with measurable outcomes or clear responsibilities.
- Follow the instructions from LatestJobsNG; avoid sending documents to unofficial contacts or copied links.
- Confirm the deadline, interview location and employer contact before sharing personal documents.
- Prepare a polite question about pay, benefits and contract terms for later interview stages.
Source and safety check
- LatestJobsNG
- Original source link available
- Application method is clear
- Deadline not specified
- No major risk signal was detected in the captured text.
Never pay for interviews, shortlisting, medical checks, uniforms, or job placement. Confirm every application at the original source before sharing personal documents. Report suspicious listing.
Interview preparation
- What experience makes you a strong fit for this QA Engineer role in QA Engineer, Mobile Tester?
- How have you handled responsibilities similar to those in this job post?
- Are you available to work in Not specified under the listed contract or schedule?
- Prepare examples with clear responsibilities, tools used and measurable outcomes.
- Review the source and research FairMoney before the interview.
Ask what the first priorities will be in the role and how success will be measured.
Similar jobs to consider
Use AI to apply better
After confirming the original source, use Career Assistant to check role fit, tailor your CV and prepare a cover letter or employer message.
Original source description
FairMoney is a digital platform in Nigeria that allows you access instant loans in a few minutes through our android app. 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 Requirements: 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