How to become a remote manual QA tester from Nigeria

To get a remote manual testing job, learn to write clear test cases and bug reports, get comfortable in Jira and a test management tool like TestRail, and collect proof that you find real bugs, usually through crowdtesting platforms and a small public portfolio. You don't need to code to start, and you don't need a computer science degree.

There is a catch. Most QA job ads now ask for at least some automation (Playwright, Cypress or Selenium), and the jobs that are purely manual are fewer and pay less. Manual testing is a good first rung. Plan to add API testing and some automation within your first year or two, or move towards QA engineering, which we cover in its own guide.

Updated October 2026 by the WorkRemote careers team

Ask AIChatGPT Claude Gemini Copilot Perplexity Grok

Typical remote pay (Nigeria-based): Median about $30,900 a year (Plane, QA tester base salary)
Core skills: Test cases, bug reports, exploratory testing, Jira, TestRail
Entry certificate: ISTQB Foundation (CTFL v4.0), online exam from about $84
Degree needed: No; proof that you find and report bugs well matters more
Honest outlook: Manual-only roles are shrinking; most QA ads now want some automation
Easiest first step: Crowdtesting on uTest, Test IO or Testlio

On this page

What a manual qa tester does
A day in the role
Skills
Tools
Where to learn
Career path
Getting hired from Nigeria
Pitfalls
FAQs
Sources

What a remote manual qa tester does

A manual tester uses the product the way a customer would, on purpose and with a plan. You take a new feature, say a transfer screen in a banking app, work out what could go wrong (wrong amount, network drop halfway, expired session, a name with an apostrophe), test each case and report what breaks.

The work splits into two kinds. Scripted testing means writing and running test cases: numbered steps with an expected result, stored in TestRail, Zephyr or Xray so the team can rerun them before every release. Exploratory testing means testing without a script for a fixed session, following your instinct about where bugs hide, and writing up what you tried.

The bug report is your real product. Developers in another time zone read it without being able to ask you anything, so it has to say exactly what you did, on which device and build, what happened, what should have happened, and include a screenshot or screen recording.

A day in the role

Read a ticket in Jira for a new feature and turn its acceptance criteria into test cases in TestRail or a spreadsheet
Run the regression suite before a release, marking each case passed, failed or blocked
Spend a timed session exploring one area of the app on a real Android phone and an iPhone, noting what you tried
Log bugs in Jira with steps, expected and actual results, environment details and a screen recording
Retest fixed bugs on the new build and close them, or reopen them with a clear comment
Join the daily stand-up and sprint planning on Zoom or Google Meet, often in UK or European hours
Check API responses in Postman or the browser's DevTools Network tab when a screen shows the wrong data

Skills you need

Core skills

Test case design: Interviewers check that you know the standard techniques: equivalence partitioning, boundary value analysis, decision tables and state transition testing. For a field that accepts ages 18 to 65, you should instantly think of testing 17, 18, 65 and 66.
Bug reporting: A good report has a specific title, numbered steps with one action each, expected and actual results, the environment (device, OS, browser, build) and evidence. Test IO's public bug report requirements are a good model to copy.
Exploratory testing: Remote teams value testers who find the bugs nobody wrote a test case for. Learn to work in time-boxed sessions with a charter ("explore checkout with expired cards for 45 minutes") and write short session notes.
Regression, smoke and retesting: Know the difference. Retesting confirms a specific fix; regression testing checks that the fix didn't break something else; a smoke test is a quick check that a build is stable enough to test at all.
Web and mobile basics: Use Chrome DevTools to read console errors and network requests, test responsive layouts, and know how Android and iOS differ. Crowdtesting pays more when you own the devices clients ask for.
API testing with Postman: This is the step that lifts you above pure click-testing. Learn to send GET and POST requests, read JSON, and know what 200, 201, 400, 401, 403, 404 and 500 status codes mean.
Basic SQL: Many teams expect testers to check that an action actually saved the right data. A SELECT with a WHERE clause and a simple join covers most of it.
How Agile teams work: Most remote QA roles sit inside Scrum or Kanban teams. Know what a sprint, a user story and acceptance criteria are, and where testing fits before a release.

Soft skills

Writing that needs no follow-up: Your developer may be asleep in Lagos time when they read your report. If they have to ask what you meant, the bug waits a day.
Tactful pushback: Sometimes you have to tell a product manager a release isn't ready. Say what you found, how bad it is for users and what you'd test next, without drama.
Patience with repetition: Regression runs are repetitive. Testers who stay careful on the 200th test case catch what others miss.
Curiosity: The best bugs come from asking "what if?": what if I press back during payment, switch to flight mode, or paste an emoji into the name field?

Tools you'll use

Jira
Where most teams log bugs and track stories; learn filters, workflows and how to link a bug to a story
TestRail
Paid test case management tool that many ads name; practise the same structure in a spreadsheet if you can't get access
Zephyr or Xray
Test management add-ons that live inside Jira, common in teams that don't use TestRail
Postman
For sending API requests and checking responses; the free tier is enough to learn
Chrome DevTools
Console errors, network requests and device emulation, built into the browser
BrowserStack or LambdaTest
Cloud access to real devices and browsers; employers usually provide accounts
Android Studio emulator
Free way to test on Android versions and screen sizes you don't own
Loom, OBS or a phone screen recorder
Short screen recordings make bugs easy to reproduce and get accepted faster
Confluence or Notion
Where test plans and release notes often live in remote teams

Where to learn

ISTQB Certified Tester Foundation Level (CTFL v4.0) (opens in a new tab)
ISTQB Syllabus is free; exam fees are set by each exam provider (see below)
The most widely recognised testing certificate. The exam is 40 multiple-choice questions in 60 minutes, with 25% extra time for non-native English speakers, and you need 26 of 40 to pass. There are no formal prerequisites.
CTFL exam, online proctored (opens in a new tab)
iSQI US$83.95 when we checked in October 2026; confirm the price shown at checkout
iSQI offers the exam by remote proctor or at a test centre, and Nigeria is in its list of available countries.
CTFL exam through AT*SQA (opens in a new tab)
ASTQB $229
ASTQB says anyone from any country can take its exam online, with 75 minutes for non-native English speakers. Pricier than iSQI, so compare before you pay.
Test IO Academy (opens in a new tab)
Test IO Free to read
Written guides on bug types, severity, bug reports and attachments. Even if you never test on Test IO, its bug report rules are a good standard to train yourself on.

Career path

How remote manual qa testers usually move up, with the years it tends to take, and where people move sideways.

Entry
Crowdtester / Junior QA Tester
0-1 year
Runs test cases and exploratory sessions, logs bugs, often paid per bug or per hour on platforms
Mid-level
QA Analyst / Test Analyst
1-3 years
Owns testing for a feature area, writes test plans, tests APIs and joins sprint planning
Senior
Senior QA Analyst
3-6 years
Decides what gets tested and how deeply, reviews others' test cases and signs off releases
Lead
QA Lead / Test Manager
6+ years
Runs the QA process for a product, manages testers and reports quality risk to leadership

Sideways moves

QA Automation Engineer · from 1-2 years
The best-paid move; needs JavaScript, TypeScript or Python plus Playwright, Cypress or Selenium
Business Analyst or Product Owner · from 3 years
Testers who know the product inside out often move into writing the requirements instead

Getting hired from Nigeria

Start with crowdtesting to get proof. uTest (run by Applause, with testers across more than 200 countries and territories), Test IO and Testlio all take freelancers. The pay models differ: uTest and Test IO pay mainly per accepted bug, with the amount set by how valuable or severe the bug is and, on Test IO, by the device you used; Testlio pays by the hour for assigned test runs, weekly through PayPal or Payoneer, and says it works with freelancers from countries not under US sanctions. Duplicate or rejected bugs on per-bug platforms earn nothing, so income swings a lot. Treat it as paid practice and a reference, not a salary.

Build a small portfolio. Pick two public apps you use, write a short test plan, 20 to 30 test cases in a shared Google Sheet, and five to ten well-written bug reports with screenshots. Put it on GitHub or Notion with a short note on how you chose what to test. Keep to normal user testing: don't try to break login security or overload a live site that hasn't invited testers.

Expect a practical test. Remote employers often send a buggy demo site or app and ask you to find and report as many issues as you can in one or two hours, or to write test cases for a login or checkout screen. Clear titles and exact steps score more than a long list of vague bugs.

Where Nigerians find these roles. LinkedIn with location set to Remote and filters for EMEA or worldwide; Himalayas, which lists remote QA tester jobs filtered for Nigeria; Upwork, where small testing gigs (test this app before launch, check this site on iPhone) are common; and Nigerian fintechs and software houses, which hire testers locally and remotely. Many ads titled "QA tester" turn out to want automation, so read the requirements before you apply.

Devices, power and time zones. Own at least one recent Android phone and, if you can, an iPhone, because many test cycles are device-specific. Keep an inverter or solar backup and two internet connections, since test cycles have deadlines. UK and European teams share your working day for most of the year; US teams mean evening overlap.

Getting paid. Platforms pay out through PayPal, Payoneer or their own systems; full-time contractor roles usually pay through Deel, Remote.com or a direct transfer into Payoneer, Grey, Raenest or a domiciliary account. Before you sign up anywhere, check that at least one payout method works with your Nigerian accounts.

Pitfalls to avoid

Staying manual for years. The pay gap with automation testers widens over time, and manual-only roles are the first to be cut or outsourced.
Logging vague bugs like "payment not working". Reviewers reject them, and on crowdtesting platforms a rejected bug pays nothing.
Paying for expensive "QA bootcamps" that promise placement. The ISTQB syllabus is free and the exam can cost under $100 online.
Treating crowdtesting income as a salary. Test cycles come and go, and earnings depend on bugs being accepted before other testers find them.
Testing only on one browser and one phone. Many real bugs only appear on Safari, older Android versions or small screens.
Applying to every ad with QA in the title. If it lists Playwright, Cypress or Selenium as required, a manual-only CV usually won't get through.

Questions people ask

Can I become a QA tester without coding?

Yes, for manual testing. You need sharp observation, test design and clear writing, not programming. But basic SQL and API testing help a lot, and you'll need some coding if you want to move into automation, where most of the better-paid QA jobs are.

Is manual testing dying?

It's shrinking, not disappearing. Fewer jobs are purely manual, and many teams now expect testers to automate repeat checks. Exploratory testing, user acceptance testing, accessibility, localisation and device testing still need people, so manual skills stay useful as part of a wider QA role.

How much is the ISTQB Foundation exam for Nigerians?

There's no single Nigerian price. When we checked in October 2026, iSQI listed its online-proctored CTFL exam at US$83.95 and ASTQB's online exam through AT*SQA cost $229. ISTQB also has a Nigerian board with accredited training providers in Lagos, who quote their own course and exam fees.

Is ISTQB worth it for a remote testing job?

It helps, especially with European employers and outsourcing firms that list it in job ads, but it won't get you hired on its own. Pair it with crowdtesting experience and a portfolio of real bug reports.

Which crowdtesting sites accept testers from Nigeria?

uTest says its community spans more than 200 countries and territories, and Testlio says it works with freelancers from countries not under US sanctions, which includes Nigeria. Test IO invites testers to cycles based on language, devices and location. Sign-up rules change, so check each platform's form yourself and never pay to join a testing platform.

How long does it take to learn manual testing?

Most people can learn the basics in two to three months of steady study and practice. Getting your first paid work usually takes longer, because you need a few accepted bugs or a portfolio before employers take you seriously.

Should I learn manual or automation testing first?

Manual first, for a few months. Automation is only useful once you know what to test and why. Then start automation early rather than late: JavaScript or TypeScript with Playwright is a common modern starting point.

Sources

Certified Tester Foundation Level (CTFL) v4.0, ISTQB (accessed October 2026)
ISTQB member boards and accredited providers directory (Nigerian Software Testing Qualifications Board) (accessed October 2026)
ISTQB Certified Tester Foundation Level 4.0 exam, iSQI (accessed October 2026)
Foundation Level certification, ASTQB (accessed October 2026)
Join the community, Testlio (accessed October 2026)
Comparison of uTest and Test IO platforms for testers, Test IO Academy (accessed October 2026)
Frequently asked questions, Test IO Academy (accessed October 2026)
Bug report requirements, Test IO Academy (accessed October 2026)
Applause testing community (uTest) (accessed October 2026)
Remote QA tester jobs in Nigeria, Himalayas (accessed October 2026)
Remote QA tester salaries in Nigeria, Plane (accessed October 2026)