- QA Testing Blogs -

How to Become a Manual Tester in 2026: Skills, Roadmap, Tools & Career Path

How to Become a Manual Tester in 2026: Skills, Roadmap, Tools & Career Path

Manual testing looks like the easiest door into tech because you do not need to write code on day one. Yet most beginners stall before they test a single feature. They are not sure what to learn first, which tools matter, or how to show an employer they can test when they have never held a testing job.

That is the real question behind how to become a manual tester: what to learn, in what order, and how to prove you can do the work. The answer is the same whether you are searching for how to become a manual QA tester, how to become a manual software tester, or how to become a QA tester with no experience.

This guide walks through the path in practical steps. It covers testing fundamentals, test design, bug reporting, tools, certification, a portfolio, and job preparation. It is also honest about the market. Entry-level roles are competitive in current market, AI is changing how test ideas get drafted, and many employers like testers who also understand basic API, SQL, or automation concepts. The advice here leans toward building proof, not collecting certificates.

Is a Manual Tester Career Right for You?

What Manual Testers Do

Check whether the daily work appeals to you before you invest months of study. A manual tester sits between the people who define how software should behave and the people who build it. The job is to find out, by hand and with a user’s eyes, where the two do not match.

What Manual Testers Do

A manual tester checks software by using it, without running automated scripts. Core responsibilities are:

  • Reading requirements and user stories to understand what the software should do

  • Designing test scenarios and test cases

  • Executing tests and recording the results

  • Reporting defects clearly so developers can reproduce them

  • Retesting fixes and running regression checks before a release

  • Joining stand-ups, planning sessions, and sometimes user acceptance testing (UAT)

A normal day mixes all of these. You might test a new feature in the morning, retest three fixed bugs after lunch, and spend the afternoon on a regression pass before a release.

Who Is a Good Fit?

You may enjoy this work if you:

  • like finding the one case nobody thought about

  • notice small mismatches, such as a wrong label, a broken tab order, or a total that is off by one cent

  • enjoy putting yourself in a user’s place

  • can explain a problem clearly in writing

  • stay patient with repetitive checks such as regression passes

  • are comfortable telling people something they may not want to hear

The role has pressure too. Deadlines squeeze testing time, requirements are sometimes unclear, and repeated regression passes can feel monotonous. If that balance sounds acceptable, keep reading.

Why Are Manual Testers Still in Demand?

Why Are Manual Testers Still in Demand?

Every release needs someone to ask whether the software works for a real person. Automation handles repeatable checks well. Humans are still needed for new features, usability, exploratory testing, and anything that depends on judgment.

The labor data needs careful reading. The U.S. Bureau of Labor Statistics (BLS) reported a median annual wage of $104,300 for software quality assurance analysts and testers in May 2025. It projects 10 percent growth from 2025 to 2035 for the combined group of developers, QA analysts, and testers. That growth figure includes developers, so it does not describe testers alone. BLS counted about 187,600 software QA analyst and tester jobs in 2025. JanBask’s own reading of the BLS data puts growth for testers specifically near 6% over ten years. That is steady, not explosive. Neither BLS figure separates manual from automation roles. Department of Labor Logo United States Department of Labor +3

AI is the other half of the story. Assistants can draft test ideas and test cases quickly, which means routine test-case typing is the part of the job most likely to be sped up. Understanding the product, spotting risk, judging whether a result “feels right,” and writing a bug report a developer can act on are harder to hand over. That is why this guide focuses on hands-on proof and on skills that last.

If you are weighing manual against automation, read our manual vs automation testing comparison before you decide how far to go.

Can You Become a Manual Tester Without Experience?

Can You Become a Manual Tester Without Experience?

Yes. Most of the tools are free, and the core skills can be practiced at home. One honest caveat is that BLS lists a bachelor’s degree as the typical entry-level education for this occupation group. “Typical” is not “required,” and many employers hire on demonstrated skill, but a degree-less candidate needs stronger proof. Hiring managers want to see that you can test, not just that you completed a course. 

How to Become a QA Tester With No Experience

If you are starting from zero, follow this order:

  1. Learn what testing is for. Testing finds risk and defects before users do. Learn the vocabulary: test case, test scenario, bug report, regression, smoke test, severity, priority.

  2. Learn how software gets built. Understand the software development life cycle and where testing fits.

  3. Practice on real applications. Pick a public demo shop or a free app and write test cases for it.

  4. Write bug reports. Find real defects in real apps and document them clearly.

  5. Keep everything in one public place. A shared folder or repository with your test cases and bug reports is your first experience.

Your first goal is to explain, in plain words, how you would test a login page, what you would check, and how you would report what you found.

Fresh Graduates

You have time and recent study habits on your side. Build a small portfolio during your final semester, and apply to QA, UAT, and support roles at the same time.

Career Switchers

Support engineers reproduce bugs, business analysts read requirements, operations staff know how work flows, and teachers and retail managers are used to spotting what goes wrong. If you have done any of that, you already understand why testing exists. Describe your past work in testing terms, for example “reproduced and documented customer-reported defects.” For a first-person story of moving into testing from outside IT, see what one career switcher learned on the way to becoming a software tester.

Developers and Business Analysts

Developers and analysts already know the product side. The gap is test thinking: coverage, risk, and writing cases a stranger can run. Many move into test analyst or QA lead roles quickly.

Transferable Skills

These carry over from almost any job:

  • Attention to detail: noticing small mismatches

  • Analytical thinking: breaking a feature into the cases that could fail

  • Written communication: explaining a failure to someone who did not see it

  • Documentation: writing down what was tested and what happened

  • Curiosity: asking “what if I do this instead?”

  • Process thinking: seeing how data and work move through a system

What Skills Does a Manual Tester Need?

The skills employers ask for fall into ten areas, and they build on each other in roughly this order.

Skill area

What it covers

Testing fundamentals

Testing principles, QA vs QC, risk-based thinking, test levels

SDLC, STLC and Agile

Life cycle models, Scrum roles, sprints, where testing fits

Test design techniques

Equivalence partitioning, boundary value analysis, decision tables, state transition, error guessing

Test documentation

Test scenarios, test cases, test data, traceability matrix, test plan

Types of testing

Functional, regression, smoke, sanity, UAT, usability, compatibility, exploratory

Defect management

Bug life cycle, severity vs priority, reproducible bug reports

Test and bug tools

Jira, Bugzilla, a test management tool or spreadsheets

Web and data basics

Browser DevTools, HTTP basics, simple API checks in Postman, basic SQL

Communication and domain knowledge

Clear writing, status reporting, understanding banking, health, retail, or other domains

AI literacy and automation awareness

Reviewing AI-drafted tests, understanding what automation can and cannot cover

Two areas deserve extra attention. The first is test design. Anyone can click around an app, but choosing the smallest set of cases that finds the most bugs is what separates a tester from someone who “tried it.” The second is written communication. A bug nobody can reproduce is a bug nobody fixes.

Manual Testing Roadmap: How to Become a Manual Tester in 10 Steps

Manual Testing Roadmap

This manual testing roadmap has ten steps, and each one prepares you for the next. Treat it as your manual tester roadmap: move on when you can explain a step out loud and do it on a fresh application, because gaps in early steps show up as weak test cases later.

Step 1: Learn Testing Fundamentals

Learn what testing is, why it matters, and the principles behind it, such as “testing shows the presence of defects, not their absence” and “exhaustive testing is impossible.” Learn the difference between quality assurance (preventing defects through process) and quality control (finding defects in the product).

Practice: explain to a friend, in two minutes, why a company would pay someone to test software.

Step 2: Learn SDLC, STLC, and Agile

Testing happens inside a development process. Learn the common models (Waterfall, V-model, Agile) and the phases of the software testing life cycle: requirement analysis, test planning, test case development, environment setup, execution, and closure. Then learn how Scrum teams work: sprints, stand-ups, backlog grooming, and retrospectives.

Practice: draw the STLC on one page and note what you would produce in each phase.

Step 3: Learn Test Design Techniques

This is the heart of manual testing. Start with these:

  • Equivalence partitioning: group inputs that should behave the same and test one from each group.

  • Boundary value analysis: test at the edges. If an age field accepts 18 to 60, test 17, 18, 19, 59, 60, and 61.

  • Decision tables: list combinations of conditions and the expected outcome of each.

  • State transition testing: test how the system moves between states, such as an order going from placed to paid to shipped.

  • Error guessing and exploratory testing: use experience and curiosity to hunt for problems no script predicted.

Practice: apply boundary value analysis and equivalence partitioning to a date-of-birth field and a password field.

Step 4: Write Test Scenarios and Test Cases

A test scenario says what to test (“verify login”). A test case says exactly how: preconditions, steps, test data, and expected result. Learn to write cases that someone else can run without asking you questions. Learn the requirements traceability matrix, which links every requirement to the cases that cover it.

Practice: write 25 test cases for a login page. Expect to cover valid login, wrong password, empty fields, case sensitivity, password masking, account lockout, “remember me,” session timeout, and what happens when you press Back after logging out. Mark the cases you would run first if you had only 30 minutes.

Step 5: Learn the Types and Levels of Testing

Learn the levels (unit, integration, system, acceptance) and the main types:

  • Functional testing: does each feature do what it should?

  • Smoke and sanity testing: is the build stable enough to test at all?

  • Regression testing: did the new change break something that used to work?

  • Retesting: is the fixed bug really fixed?

  • Usability and compatibility testing: is it easy to use, and does it work across browsers and devices?

  • UAT: does it meet the needs of the business users?

  • Non-functional basics: performance, security, and accessibility awareness.

Practice: take one app and write one smoke test, one regression test, and one compatibility check for it.

Step 6: Learn Defect Management

Learn the bug life cycle (new, assigned, open, fixed, retest, closed or reopened). Learn the difference between severity (how bad the impact is) and priority (how soon to fix it). A typo in the company logo can be low severity but high priority. A crash in a rarely used report can be high severity but low priority.

A good bug report has a clear title, environment details, numbered steps to reproduce, expected result, actual result, and evidence such as a screenshot or short recording.

Practice: find five real bugs in a public demo app and write each one in a tracker such as Jira, Bugzilla, or a spreadsheet.

Step 7: Learn Web Basics, Simple API Checks, and SQL

You do not need to be a developer, but a few technical skills lift you above other beginners. Learn to open browser DevTools and read the network tab. Learn what HTTP methods and status codes mean. Learn to send a simple request in Postman and check the response. Learn enough SQL (SELECT, WHERE, JOIN) to confirm that data landed in the right table after a test.

Practice: submit a form in a demo app, find the matching request in DevTools, and check the response status and body.

Step 8: Learn Test Planning, Execution, and Reporting

Learn what goes into a test plan: scope, approach, environments, schedule, risks, and entry and exit criteria. Practice executing a cycle: mark cases pass, fail, or blocked, link failed cases to bugs, and produce a short test summary report that says what was tested, what was found, and what risks remain.

Practice: write a one-page test plan and a one-page summary report for a small app.

Step 9: Learn the Basics of Automation Awareness

You do not have to become an automation engineer. But understand what automation does well (repetitive regression checks) and what it cannot do (judge usability or explore). Many employers prefer testers who can read a simple script or support an automation team, and JanBask’s guide to the QA software tester career path also recommends learning both manual and automation testing.

Practice: pick ten of your test cases and mark which ones are worth automating and why.

Step 10: Learn AI-Assisted Testing

Use an AI assistant to draft test ideas, edge cases, and sample data. Then review everything it produces. Treat AI output as a draft from a fast but inexperienced colleague. It will miss business rules, invent requirements, and repeat obvious cases.

Practice: ask an AI tool for test cases for a checkout page, run them on a demo shop, and document what it missed and what it got wrong.

One honest note on timing: there is no fixed timeline. As a planning assumption rather than a measured average, many beginners budget roughly two to four months of steady study before applying, and less if they already work in a related role.

Which Tools Should You Learn First?

Which Tools Should You Learn First?

Learn tools by the problem they solve. Start with these:

  • Jira or Bugzilla: defect tracking and, in many teams, user stories and sprint boards.

  • A test management tool or a spreadsheet: many teams use a dedicated tool, and many beginners start with Excel or Google Sheets for test cases and traceability.

  • Browser DevTools: inspect elements, read the console, and watch network requests.

  • Postman: send simple API requests and check responses without writing code.

  • A SQL client: run simple queries against a practice database.

  • A screenshot and screen-recording tool: evidence makes bug reports faster to fix.

  • An AI assistant: useful for drafting test ideas, as long as you review the output.

Tool names change from employer to employer, so read job postings in your market and learn the one or two that appear most often. The concepts, such as writing a good defect or tracing a requirement, transfer from one tool to another.

Do You Need a Manual Testing Certification?

No rule requires one, but a certification can help a resume get past screening. A certificate shows you studied the theory. A portfolio shows you can apply it. Employers see many resumes with certificates, so projects you can explain are what set you apart.

Certification

Exam format

Prerequisite

ISTQB Certified Tester Foundation Level (CTFL) v4.0

40 questions, 60 minutes, 26 points to pass (extra time is available for non-native English speakers)

None, and it is the prerequisite for the other ISTQB Certified Tester exams

CTFL is vendor-neutral and a sensible first exam because it needs no prior experience and covers the vocabulary and techniques in Steps 1 to 8 above. Other credentials, such as CAST or the ISTQB Agile Tester certification, are options for later. Check ISTQB’s site for current fees and syllabus versions before you book.

Remember that a course completion certificate from a training provider is separate from an ISTQB exam. Both can help, but neither replaces real work samples.

How to Get Hands-On Manual Testing Experience

Anyone asking how to become a manual tester without a job history gets the same answer: practice on real software, keep proof, and make it visible.

Practice Targets

Use public demo sites built for testing practice, such as Sauce Demo and Restful-Booker. They are stable and safe. Do not run aggressive tests on live production sites, and only test systems you have permission to test.

Example Manual Testing Projects

  • Test case suite: 30 well-organized test cases for a demo e-commerce site, with a traceability matrix.

  • Bug report pack: 10 clearly written defects with screenshots or short recordings, kept in a tracker.

  • Test plan and summary report: a plan before testing and a report after it, for a small app.

  • Exploratory testing session: a written charter, your notes, and the bugs you found in a 60-minute session.

  • Compatibility matrix: the same flow checked across two browsers and a phone, with results.

  • Postman collection: a short set of API requests with the checks you did by hand.

  • AI-assisted test review: AI-drafted cases, your edits, and a list of what the AI got wrong.

For each project, add a short README covering scope, what you tested, how to read the results, and known gaps. That document is what you show in interviews. Volunteering to test a friend’s app, a nonprofit’s website, or a beta product also counts as experience if you document it.

What Does the Manual Tester Career Path and Salary Look Like?

If you are mapping out how to become a manual QA tester and where the role leads, the path is not one fixed ladder. JanBask’s QA software tester career guide walks through the wider field, and most people move through stages like these:

Stage

Typical titles

What you do

What to add next

Entry

Junior QA Tester, Manual Tester, QA Analyst

Execute test cases, log bugs, run regression

Stronger test design, SQL, API checks

Mid

QA Analyst, Test Analyst, Senior Manual Tester

Design tests, own a feature area, mentor juniors

Test planning, Agile practices, some automation

Senior

Senior QA Analyst, QA Lead, Test Lead

Set test strategy, review work, report to stakeholders

Risk management, metrics, team leadership

Lead and beyond

Test Manager, QA Manager

Plan quality across projects, manage people and budgets

Leadership, budgeting, vendor management

Many testers also branch into automation or SDET roles, performance testing, security testing, business analysis, product ownership, or domain specialties such as healthcare or finance.

What Does Pay Look Like?

Salary sources measure different things, so treat them as benchmarks, not promises:

  • BLS reports a May 2025 median wage of $104,300 for software QA analysts and testers. This covers all testers, including automation roles and experienced staff.

  • ZipRecruiter’s manual testing salary data showed an average of $87,173 per year as of July 2026, with most salaries between $70,000 and $101,500.

  • Other ZipRecruiter pages describe manual tester pay as typically between $40,000 and $70,000, with entry-level testers closer to $40,000.

These numbers disagree, and that is the point. Entry-level offers depend heavily on location, industry, and employer, and they usually sit below the national medians. Check postings in your own market before you set expectations.

How to Get Your First Manual Testing Job

How to Get Your First Manual Testing Job

The final part of how to become a manual tester is getting hired. It takes a wide search, a portfolio, and patience. Given the competition at entry level, spread your effort across several kinds of roles.

Job Titles to Search

  • Manual Tester

  • QA Tester

  • QA Analyst

  • Software Tester

  • Test Analyst

  • Junior QA Engineer

  • UAT Tester

  • Quality Analyst

Titles vary by employer, so read the duties. A “QA Analyst” posting may be mostly manual testing, and a “Manual Tester” posting may quietly ask for SQL or Postman.

Resume and LinkedIn

Lead with what you did, not only what you studied. Write bullets such as “wrote 40 test cases with a traceability matrix for an e-commerce demo app and logged 12 defects in Jira with reproduction steps.” Name the tools, link your portfolio, and use a headline that names your target role, such as “Manual QA Tester | Test Design | Jira | Postman.”

Portfolio

Choose two or three projects from section 9 and present each on one page: the problem, what you tested, and the result. Screenshots of a well-written bug and a clean test summary report help a reviewer see your work quickly.

Interview Preparation

Expect scenario questions such as these:

  • How would you test a login page, an elevator, or a search box?

  • What is the difference between severity and priority?

  • A bug is found in production a day after release. What do you do?

  • How do you decide what to test first when time is short?

  • What belongs in a good bug report?

Practice answering out loud, using your own projects as examples. Working through manual testing interview questions and answers is a good rehearsal.

Alternative Routes Into Testing

  • Start in support or UAT: many teams promote people who already know the product.

  • Contract and short-term roles: these often care more about hands-on skill than degrees.

  • Internal moves: if you already work at a software company, ask about a QA rotation.

  • Crowdtesting and beta programs: these give you real bug reports to show.

  • Internships and apprenticeships: worth applying for even if you are changing careers.

What Mistakes Should New Manual Testers Avoid?

What Mistakes Should New Manual Testers Avoid?

Most people following a manual testing roadmap stumble by collecting tutorials instead of testing. Watch for these:

  • Memorizing definitions without testing real software

  • Writing vague test cases that only you can understand

  • Skipping test design techniques and clicking around at random

  • Writing bug reports with no steps to reproduce

  • Confusing severity and priority

  • Ignoring SQL, API, and DevTools basics

  • Treating AI-generated test cases as finished work

  • Believing “manual only” is enough forever and never learning how automation fits

  • Treating a certificate as the finish line

  • Waiting to feel “ready” before applying

How Do You Turn Manual Testing Skills Into Job-Ready Skills?

How Do You Turn Manual Testing Skills Into Job-Ready Skills?

There is a big difference between knowing the manual tester roadmap on paper and being able to show you can do the job. Employers hire for the second. Your skills only lead to a job when they end in evidence.

The reliable path is a loop: learn, practice, document, certify, and interview.

  1. Learn: study one step of the roadmap at a time.

  2. Practice: repeat the hands-on task on a new application until it feels routine.

  3. Document: save test cases, bug reports, a plan, and a summary report.

  4. Certify: take an exam such as ISTQB CTFL once you can answer the questions with confidence.

  5. Interview: rehearse explaining your projects out loud.

Many learners do this alone with free resources, and that works. Others prefer live instruction, deadlines, and someone to answer questions, which is where an online QA training program can help.

Build Your Manual Testing Skills With JanBask Training

If you want live instruction, JanBask Training offers programs for different starting points.

JanBask Training’s Manual Testing Training course page lists test case development, testing types and methodologies, test case design techniques, levels of testing, and real-time project work. If you want manual testing plus automation, the QA Software Testing Training program is the broader option. JanBask’s current course pages describe an 8-week program that goes from QA fundamentals and STLC through Selenium, Playwright, API testing, Git, and Jenkins, with a 4-week job assistance program.

Before you enroll in any course, ask three questions. First, does the syllabus match the jobs you are targeting, and will you write real test cases and bug reports during the course? Second, what exactly does job assistance include (resume review, mock interviews, referrals?) and how is it delivered? Third, what are the current batch dates, duration, and fee, since course pages are updated at different times? Syllabi change, so ask for the current curriculum for your batch.

Frequently Asked Questions

1. How to become a manual tester with no experience?

Learn testing fundamentals, SDLC and STLC, test design techniques, and defect reporting. Then write test cases and bug reports for public demo apps, and keep them in a portfolio. Because entry-level roles are competitive, apply to several job titles, such as QA analyst, UAT tester, and junior QA, and consider adjacent roles while you build your proof.

2. How to become a QA tester with no experience?

Start with the same fundamentals, then build two or three documented projects: a test case suite, a bug report pack, and a test plan with a summary report. Use that portfolio on your resume and in interviews to show that you can test, even without a job title.

3. How to become a manual QA tester without a degree?

It is possible. BLS lists a bachelor’s degree as typical for this occupation group, but many employers hire on skills. Without a degree, you need stronger proof: a portfolio, a certification such as ISTQB CTFL, and clear interview answers.

4. How to become a manual software tester if I have never coded?

You do not need to code to start. Learn test design, documentation, and defect reporting first. Then add light technical skills such as browser DevTools, simple Postman requests, and basic SQL, which make you more employable.

5. Which manual testing skills matter most?

Test design, clear written communication, defect reporting, and understanding of how software is built matter most. Basic SQL, API checks, and awareness of automation come next.

6. How long does the manual testing roadmap take?

There is no fixed timeline. As a planning assumption, many beginners budget two to four months of steady study. A better measure is the ten-step manual testing roadmap in section 6: when you can do each step on a fresh application, you are close to applying.

7. Do I need to learn automation too?

You can start in manual testing without it, but many employers prefer testers who understand automation. Treat it as the next step after you are solid in manual fundamentals.

8. Do I need an ISTQB certification to become a manual tester?

No, but the Foundation Level certificate is a low-barrier, vendor-neutral signal. It has no formal prerequisites, and it is needed before the other ISTQB Certified Tester exams. Pair it with projects, since a certificate alone does not show you can write good test cases.

9. How much do manual testers earn?

Benchmarks vary by source. BLS reports a median of $104,300 for all software QA analysts and testers (May 2025), while ZipRecruiter figures for manual testing range widely. Entry-level pay is usually lower and depends on location, industry, and employer.

10. Will AI replace manual testers?

The current evidence points to changing roles, not disappearing ones. AI can draft test ideas and cases quickly, but testers who understand the product, judge risk, review AI output, and write clear bug reports are better placed than those who only execute scripted steps.

11. How competitive is the entry-level market?

It is competitive, and many candidates have similar certificates. Build proof, apply across several job titles, and consider routes such as UAT, support, or internal transfers.

12. What does the manual tester career path look like after the first job?

Most people move from junior tester to QA analyst or test analyst, then to senior and lead roles. Many branch into automation, performance, security, business analysis, or product roles. Building depth in test design and communication, and adding technical skills along the way, helps you choose your direction.

Shubham Singh

Written by

Shubham Singh

With his detailed research and unique insights into IT and Technological trends, Shubham has been producing high-quality and engaging content that meets the standards of its end-users.

Leave a comment

QA Testing Career Programs

Live, mentor-led QA Testing programs designed around the same skills this blog covers.

Explore QA Testing courses

Explore more topics

Browse Blog Categories

Jump to another subject — AI, Cloud, Salesforce, Data, Testing, and more — and keep learning by topic.

Interviews

Browse Categories