Analyst, Quality Assurance at Babban Gona

Babban Gona, which means "Great Farm" in the Hausa language, is a social enterprise organization that provides support for smallholder farmers in Nigeria to become more profitable. 
The Role

We are looking for a QA Analyst to join our Lagos-based technology team and help protect the quality of software that matters. You will work within an existing QA team, reporting to the Product Manager, and take ownership of testing across our mobile (Android/iOS) and web product suite. This is not a passive role — you will be actively building test coverage, developing automation capability, and partnering with engineers and product managers to catch failures before they reach the field.
This role is right for someone early in their QA career who brings solid fundamentals, a genuine hunger to learn, and enough curiosity about the real world to care about who uses the software they test.

Key Responsibilities

Design and execute test cases for mobile (Android/iOS) and web applications, covering functional, regression, edge-case, and exploratory testing scenarios.
Document and maintain test coverage across core user flows — ensuring the Product Manager and Engineering Lead have a clear, current view of what is tested and what is not before every release.
Identify, log, and track bugs with clear reproduction steps, severity ratings, and evidence — prioritising issues with the highest potential impact on field officers and farmers in low-connectivity environments.
Build and maintain automation scripts in the team's chosen framework, starting with high-frequency regression scenarios and progressively expanding coverage.
Participate in sprint cycles — reviewing requirements and user stories before development begins, flagging ambiguity or edge cases that could become quality risks downstream.
Conduct release readiness assessments — providing a structured sign-off or risk summary to the Product Manager before each production deployment.
Investigate root causes of recurring bugs and test failures, distinguishing between isolated incidents and systemic issues that require process or code fixes.
Test specifically for low-resource conditions — simulating low-bandwidth environments, older device models, and intermittent connectivity scenarios representative of Babban Gona's field context.
Collaborate with engineers on defect resolution — providing the detailed reproduction evidence needed to diagnose and fix issues efficiently.
Contribute to QA team knowledge — documenting test approaches, sharing learnings from new tools or techniques, and helping to raise the team's overall capability over time.

What Success Looks Like
In your first 6 months:

80%+ of core user flows documented with test cases across the two highest-priority applications, with zero critical flows untested.
Minimum 20 confirmed production-risk bugs identified and logged before they reached the field.
At least one automation script running reliably in CI, covering a high-frequency regression scenario.

In Your First 12 Months

Fewer than 2 critical regression failures per quarter attributable to test coverage gaps.
A living test coverage document actively maintained and used in release decisions.
End-to-end ownership of the test suite for at least one product area, with automation capability meaningfully expanded from your starting point.

Requirements
Experience & Qualifications
Required

0–4 years of QA or software testing experience, with hands-on exposure to structured test case design and defect logging.
Experience testing mobile applications (Android and/or iOS) and web-based interfaces.
Familiarity with at least one test management or bug tracking tool (e.g., Jira, TestRail, or equivalent).
Basic understanding of automation testing concepts — you don't need to be an automation engineer, but you must be willing and able to learn and contribute.
Strong analytical thinking — able to identify what could break, not just what is obviously broken.
Clear written communication — bug reports that engineers can act on without a follow-up conversation.

Preferred

Exposure to any automation framework (Selenium, Appium, Cypress, Playwright, or similar) — framework-agnostic candidates welcome.
Experience testing in low-connectivity or mobile-first environments.
Familiarity with Agile/Scrum development cycles.
Prior experience in a mission-driven, startup, or high-growth organisation