QA and Software Testing Jobs in Kenya: The Overlooked Entry Point

A QA tester's job is to break things. Before a feature ships to users, someone needs to try every possible way it could go wrong. That someone is the QA tester.

At a Nairobi fintech, a tester might check an M-Pesa payment flow by trying valid amounts, zero amounts, negative amounts, amounts above the transaction limit, amounts with decimal points, and amounts entered while the phone has no network. They check what happens when a user taps the pay button twice. What happens when the session expires mid-transaction. What happens on Android 10, Android 13, and iOS 17.

The day involves reading requirements for new features, writing test cases (structured checklists of what to test), executing those tests, documenting bugs with screenshots and steps to reproduce, and verifying that fixed bugs are actually fixed. It is detail-oriented, repetitive, and genuinely important. A bug that slips past QA and reaches users costs the company money, reputation, and sometimes regulatory trouble.

Manual testers do this by hand, clicking through the application like a user would. Automation testers write code that runs these tests automatically, which is faster and more consistent. Most people start manual and transition to automation as they learn programming.

QA testers sit within the development team. They attend standups, sprint planning, and retros. They work closely with developers, filing bugs and discussing edge cases. This exposure to the full development process is why QA is such a powerful entry point. You learn how software gets built by being part of the team that builds it.

Social media glorifies developers and designers. Nobody posts "Just landed my first QA testing role" on Twitter/X and gets 500 likes. The lack of glamour means fewer people pursue QA, which means less competition for open positions.

At McTaba, we have seen graduates struggle to land developer roles against hundreds of applicants, then get hired as QA testers within weeks because only a handful of people applied. Same company, same team, same office. Just a different role that most people did not consider.

Once you are inside, the doors open. You are learning the codebase, understanding the product, building relationships with developers and product managers, and absorbing knowledge about how the company works. After six to twelve months, you are in a stronger position to move into development, product, or automation engineering than someone applying from outside with no industry experience.

Kenyan banks are especially keen on QA testers. The Central Bank of Kenya's prudential guidelines require financial institutions to test their systems thoroughly. Regulatory compliance creates QA roles that must be filled. Equity, KCB, NCBA, and Stanbic all maintain QA teams, and they often struggle to find enough qualified testers.

Fintechs and startups that process payments need QA for a practical reason: a payment bug can lose customers real money. Companies like M-KOPA, Branch, and Flutterwave take testing seriously because the cost of getting it wrong is immediate and measurable.

Attention to detail. If you are the kind of person who spots typos in menus, notices when a button is misaligned, or catches errors in receipts, you have the core QA instinct. Testing requires noticing what most people overlook.

Systematic thinking. You cannot test randomly and hope to catch bugs. You need to think about test cases methodically: positive cases (valid inputs), negative cases (invalid inputs), boundary cases (limits and edges), and integration cases (how different parts of the system interact).

Clear written communication. Bug reports are documents. A good bug report includes: a clear title, steps to reproduce, expected behaviour, actual behaviour, environment details (browser, OS, device), and screenshots or recordings. A developer who receives "the app crashed" cannot fix anything. A developer who receives "the app crashes when a user with no saved cards attempts to add a Visa card on Chrome mobile, Android 13, after the session has been idle for 15 minutes" can fix it in an hour.

Basic technical knowledge. You do not need to write code for manual QA, but understanding the basics helps. Know what an API is, what a database does, what HTTP status codes mean, and how to use browser developer tools to inspect network requests. This knowledge helps you file more informative bug reports and communicate with developers.

Patience. Testing the same flow 50 times with different inputs is tedious. Testing it again after the developer says they fixed the bug is more tedious. But finding the one edge case that would have cost the company KES 10 million in incorrect transactions makes it worthwhile.

Week 1-2: Learn testing fundamentals. Free resources work fine. Read about test case design, bug reporting, the software testing lifecycle, and test levels (unit, integration, system, acceptance). The ISTQB Foundation Level syllabus is free to download and covers everything a junior tester needs to know. You do not need to take the exam, but the syllabus is a solid textbook.

Week 3-4: Practice on real apps. Pick any app you use daily, like the M-Pesa app, a banking app, or an e-commerce site. Write 20 test cases for one feature. Then execute them. Find real bugs (you will, even in polished apps) and write them up as formal bug reports. This practice builds both your testing skills and your portfolio.

Week 5-6: Learn testing tools. Get familiar with Jira (most companies use it for bug tracking), learn to use browser DevTools for inspecting network requests and console errors, and try a screen recording tool like Loom for capturing bug demonstrations. These are the tools you will use daily on the job.

Week 7-8: Build a portfolio and apply. Create a simple document or website showcasing your test cases and bug reports. Apply for junior QA roles, internships, and attachment positions. Search for "QA Tester," "Software Tester," "Test Analyst," and "Quality Assurance" on job boards and LinkedIn.

The entire learning path costs nothing and takes less than two months. Compare this to the 6 to 12 months needed to become a hireable developer, and you see why QA is the faster entry point.

Manual testing gets you in the door. Automation testing is where the money and career growth live.

Automation testers write code that runs tests automatically. Instead of clicking through a payment flow 50 times by hand, you write a script that does it in seconds. The script runs every time code changes, catching regressions before they reach production.

The most common automation tools in Kenya are Cypress (for web applications), Selenium (older but still widespread), Playwright (growing rapidly), and Appium (for mobile testing). Most teams use JavaScript or Python for test automation scripts, so learning one of these languages is the bridge from manual to automation.

The typical transition takes 6 to 12 months of learning alongside your manual QA job. Start by learning JavaScript or Python basics, then pick Cypress (it has the gentlest learning curve). Write automated tests for the same features you test manually. Show your lead. Gradually, you take on more automation work and less manual testing.

The salary jump is significant. A manual QA tester earning KES 60,000 can reach KES 150,000 to KES 250,000 as an automation engineer within 2 to 3 years. Senior automation engineers and SDET (Software Development Engineer in Test) roles command KES 250,000 to KES 400,000 in Nairobi.

Some companies call this role "QA Engineer" (automation-focused) versus "QA Analyst" (manual-focused). Others use "SDET" for testers who write significant amounts of code. The titles vary, but the progression is consistent: manual to automation to potentially full development or DevOps if you want to keep climbing.

Junior Manual QA (0-1 year): KES 35,000 to KES 80,000. Entry-level positions at startups and agencies. Some of these are labelled "intern" and pay at the lower end. Banks pay higher even at this level.

Mid-Level QA (1-3 years): KES 80,000 to KES 200,000. At this level, you write test plans independently, mentor new testers, and may begin automation. Companies expect you to handle complete feature testing without supervision.

Senior QA / Automation Engineer (3-5 years): KES 200,000 to KES 400,000. You lead QA for your product or team, build and maintain automation frameworks, and define testing strategies. These roles often include CI/CD integration work, which overlaps with DevOps.

QA Lead / Manager (5+ years): KES 300,000 to KES 500,000. You manage a team of testers, set quality standards across the engineering organisation, and report to engineering leadership. These roles exist at banks, telecoms, and large tech companies.

The career outlook for QA in Kenya is strong. As Kenyan companies grow their digital products and face increasing regulatory requirements, testing becomes more critical, not less. The push toward digital banking, insurtech, healthtech, and government digitisation all create demand for people who can verify that these systems work correctly.

Remote QA roles also exist. International companies hire remote QA testers, especially those with automation skills and experience testing payment systems. The M-Pesa integration testing experience that Kenyan QA testers develop is genuinely unique and valued by companies building for African markets.