Straight answer: you become a remote manual software tester by learning to write proper test cases and bug reports, getting comfortable in one bug-tracking tool like Jira, building two or three portfolio examples on real apps, then applying through crowdsourced testing platforms like uTest and Testlio before you chase full-time remote QA roles at companies like GitLab or Automattic. It takes most people three to six months of deliberate practice to land a first paid gig. The bit nobody tells you upfront: entry-level pay is low and shrinking because of offshore competition, so treat manual testing as a doorway to something better, not the destination.
What a manual software tester does all day
Forget the image of someone randomly clicking buttons. A manual tester’s job is to break software on purpose, write down exactly how they broke it, and hand that information to developers in a form they can act on without asking ten follow-up questions.
A normal day looks like this: you get a new feature or a bug fix to test, you read the ticket and the acceptance criteria, you write test cases covering the obvious path plus the edge cases (empty fields, wrong file types, slow connections, screen readers), you run them, and you log every failure with steps to reproduce, expected result, actual result, screenshots, and environment details (browser, OS, device). Then you retest once the fix goes in. That’s it, repeated fifteen or twenty times a day.
The skill isn’t finding bugs. Anyone can find bugs. The skill is writing a bug report a developer can reproduce in under two minutes without messaging you.
Do you need a degree or a certification
No degree required, full stop. I’ve worked alongside testers who came from retail management, teaching, and customer service. What matters is attention to detail and the ability to write clearly under pressure, not a computer science background.
Certifications are more useful as a signal to recruiters scanning CVs than as actual training. The one worth having is ISTQB Foundation Level, which costs around £180 to £250 for the exam and covers the vocabulary and process every job description assumes you already know (test levels, defect life cycle, boundary value analysis). It won’t teach you to test well. It will stop a recruiter’s applicant tracking system from binning your CV before a human sees it.
Skip anything that costs more than £300 and promises a “guaranteed job.” Those courses exist because manual testing has a low barrier to entry and a high number of people trying to break in fast, and someone always monetises that desperation.
The skills that get you hired
Test case writing
Learn to write a test case with a clear precondition, steps, and expected result. Practice on apps you already use. Write ten test cases for the login screen of your banking app. Include what happens with a wrong password, a locked account, a special character in the username field, and a session timeout mid-login.
Bug reporting in a real tool
Jira is the industry standard by a wide margin. Get a free trial or the free tier and log fake bugs against a demo app until the format is second nature: summary, steps to reproduce, expected vs actual, severity, priority, environment.
Basic understanding of APIs
You don’t need to code, but you need to open Postman, send a GET request, and read a JSON response without panicking. More and more “manual” testing job descriptions now expect you to check that an API returns the right data even if you’re not automating anything. This is the single biggest skill gap I see in people trying to break in.
Accessibility testing
This is the one area of manual testing that’s growing rather than shrinking, because of legal pressure. In the US, ADA lawsuits over inaccessible websites have gone up every year for over a decade, and in the UK and EU the same pressure exists through the Equality Act and the European Accessibility Act. If you learn to test with a screen reader (NVDA is free), check colour contrast, and verify keyboard-only navigation, you become useful in a way most junior testers aren’t. I wrote a longer breakdown of what compliant means in practice in my accessiBe review on ADA-compliant websites, and it’s worth reading even if you never touch that specific tool, because the manual checks it describes are exactly what testers get asked to verify.
A real example: how one client’s tester got hired
A few years ago I was consulting for a small SaaS company doing employee scheduling software, maybe eighteen people total, fully remote. They needed a tester and couldn’t afford a senior QA salary. The person they hired, I’ll call her Priya because that’s not her real name but the details are, had zero professional testing experience. She’d been a hotel receptionist.
What got her the interview wasn’t a CV line, it was a two-page document she sent unprompted: she’d tested their actual sign-up flow (which was public), found four real bugs including one that let you submit a form with no email address, and wrote them up exactly like proper Jira tickets, numbered, with screenshots. The founder told me later he’d had eleven applicants with ISTQB certificates and none of them had bothered to open the product. Priya was hired at £24,000 for a fully remote UK role, and within fourteen months she’d taught herself enough API testing in Postman to get a £31,000 offer elsewhere.
The lesson isn’t “be a natural talent.” It’s that a real, specific bug report on the actual product you’re applying to test beats a certificate every time, because it proves you’ll do the job rather than just describe it.
Step by step: how to break in with no experience
- Week 1 to 2: learn the vocabulary and process. Free resources on ISTQB syllabus PDFs (available free online, you only pay for the exam) plus YouTube channels dedicated to manual QA basics will cover this.
- Week 3 to 4: pick a free Jira account and a demo e-commerce site or app, and write and log 15 to 20 realistic bugs.
- Week 5 to 6: learn Postman basics. Send requests to a free public API (many exist for practice, like reqres.in) and document what you find.
- Week 7: build a one-page portfolio, either a simple website or a shared Google Doc, showing three worked examples: a set of test cases, a bug report with screenshots, and a short accessibility audit of a real website using a free screen reader.
- Week 8 onwards: apply. Start with crowdsourced testing platforms, then move to full-time remote QA roles once you have paid work on your CV.
Where the actual remote jobs and pay are
There are two very different markets here and conflating them is where most guides go wrong.
Crowdsourced and gig testing platforms: uTest (owned by Applause) and Testlio pay per approved bug or per test cycle, and this is the easiest door in. Realistic pay is $10 to $25 an hour equivalent once you’re consistently finding valid bugs, sometimes less when you’re new and your reports get rejected. It’s inconsistent work, not a salary, and it’s a starting point, not a career.
Full-time or contract remote QA roles: companies with fully distributed teams regularly hire remote manual and hybrid testers. GitLab, Automattic (WordPress.com), Zapier, and Toptal-listed clients all run entirely remote QA functions. UK-based junior remote QA roles typically pay £22,000 to £30,000. With twelve to eighteen months of experience and some API testing ability, £32,000 to £42,000 is realistic. In the US, junior remote QA tends to sit at $45,000 to $60,000, rising to $65,000 to $80,000 with automation exposure. Freelance day rates in the UK for manual testers with a few years behind them run £150 to £280 a day.
If you’re weighing this against other remote options entirely, it’s worth reading my breakdown of real work-from-home jobs and their actual pay, because manual testing sits in the middle of that pack, better paid than most entry-level remote admin work, less lucrative than remote sales or specialist consulting.
The uncomfortable part nobody puts in these guides
Here’s what most articles about becoming a remote manual tester conveniently leave out: pure manual testing, on its own, with no automation and no specialisation, is a shrinking job category. AI-assisted test generation tools now write basic regression test cases in minutes, and companies with tight budgets are quietly using them to cut the number of junior testers they need. Offshore testing agencies in India, the Philippines, and Eastern Europe compete on rates that a UK or US-based tester simply cannot match on manual work alone.
This doesn’t mean don’t do it. It means don’t stop here. The testers I’ve watched build actual careers used manual testing as the entry point, then added one differentiator within their first year: API testing, basic automation with a tool like Selenium or Playwright, accessibility auditing, or security testing basics. The ones who stayed purely manual for three or four years without adding a skill are the ones I’ve seen get made redundant when budgets tightened, because that role is the easiest one to cut or outsource.
If you’re building this as a freelance business rather than chasing employment, you’ll also need basic client-finding skills, which is closer to sales than most testers expect. Writing a short, specific outreach email to an agency owner about the bugs you found in their client’s site works far better than a generic pitch, and the structure in my guide on writing a sales email sequence that converts applies just as well to a solo tester pitching contract work as it does to a business selling a product.
Tools worth learning
- Jira or a similar tracker (ClickUp and Azure DevOps also common) for bug logging and ticket workflow
- TestRail or Zephyr for organising test cases at a company that’s more structured
- Postman for basic API checks
- BrowserStack or LambdaTest for cross-browser and device testing without owning fifteen phones
- NVDA (free) or VoiceOver (built into Mac) for accessibility testing
You don’t need to master all five before applying anywhere. Two, done, beats a shaky familiarity with all of them.
What I’d tell someone starting from zero this year
Don’t spend money on a course before you’ve spent a weekend testing a real, live website for free and writing up what you find. If you can’t get yourself to do that unpaid, the paid work won’t feel different, it’ll just feel like more of the same thing you were avoiding. Manual testing rewards people who are naturally a bit pedantic and a bit stubborn about detail. If that’s you, the entry point is low, remote roles do exist and pay a livable if modest wage, and the path upward is clear if you keep adding one new skill every year instead of standing still.
Frequently asked questions
Can I become a remote manual tester with no coding skills at all?
Yes, and most junior manual testing roles are explicitly non-technical, but basic comfort with a tool like Postman for checking API responses will get you shortlisted over candidates who can only test through a browser.
How long does it realistically take to get a first paid testing job?
Most people who study test case writing, learn Jira, and build a small portfolio of real bug reports land their first paid work, often through a crowdsourced platform, within eight to twelve weeks of consistent effort.
Is manual testing a good long-term remote career?
On its own, no, because AI-assisted testing tools and low-cost offshore agencies are shrinking pure manual roles, but as a starting point that you build on with API testing, basic automation, or accessibility auditing within your first year, it leads to solid remote roles paying £35,000 to £45,000 or more.
What’s the fastest way to get paid testing experience without a job?
Pick a real public website, test its sign-up or checkout flow, write up the bugs exactly as you would in Jira with steps and screenshots, and send it directly to the company or use it as your portfolio piece when applying to crowdsourced platforms like uTest or Testlio.
Related reading: 4 Must-Know Tips for Working Remotely and Why Manual File Sharing Becomes a Risk as Your Business Scales.
For the bigger picture, see my full guide to productivity.
