QA Engineer Roadmap 2026: Become a QA Engineer Step by Step

Short answer: learn in this order — (1) testing fundamentals, (2) SQL, (3) API testing, (4) one programming language, (5) one automation tool (Playwright or Selenium), (6) Git and a CI pipeline, then (7) build a small public portfolio and (8) practice interview answers out loud. Each stage has a concrete piece of proof you should be able to show before moving on, listed in the table below.

How long it takes depends on your starting point and weekly hours, so treat any timeline in this guide as a planning estimate, not a promise. Career changers studying part-time usually plan in months, not weeks. If you want structured lessons, the SoftwareTestPilot Academy follows the same order.

What does a QA engineer do?

• Analyse requirements and turn them into test scenarios and test cases
• Run manual and automated tests, and decide which tests are worth automating
• Report bugs with clear steps, expected result and actual result, then retest fixes
• Work with developers and product managers on acceptance criteria before code is written
• Check behaviour across browsers, devices and APIs

Common QA roles

Pay varies widely by city, company type and skills, so check current ranges in the QA tester salary guide for India or the US QA salary guide rather than relying on one number.

A. Software testing fundamentals

• SDLC and STLC phases
• Test case design techniques (BVA, EP, decision tables)
• Bug life cycle and reporting
• Types of testing (smoke, sanity, regression, exploratory)

Check yourself against the top 50 software testing interview questions.

B. Manual testing in practice

• Writing test scenarios and test cases
• Test management tools (Jira, TestRail, Zephyr)
• Requirements traceability
• Testing inside Agile/Scrum sprints

Go deeper with these manual testing questions and answers.

C. Automation testing

• Playwright with TypeScript — built-in auto-waiting, tracing and parallel runs
• Selenium WebDriver with Java or Python — still widely used in enterprise teams
• Page Object Model (POM) and basic framework design

Start with the Playwright guide for QA engineers, and read Playwright vs Selenium if you are unsure which to pick.

D. API testing

• REST fundamentals, HTTP methods and status codes
• Postman collections and environment variables
• REST Assured (Java) or Playwright's request API for automation

E. SQL for testers

• Basic queries (SELECT, INSERT, UPDATE, DELETE)
• Joins, subqueries, aggregations
• Verifying data written by the application

F. Git, CI/CD and containers

• Git and GitHub pull requests
• GitHub Actions or Jenkins to run tests on every change
• Docker basics for repeatable test environments

G. AI-assisted testing

• Using assistants such as GitHub Copilot to draft tests — and reviewing every line they produce
• Testing features that use AI models (non-deterministic output, safety checks)

See the GitHub Copilot guide for QA testers and the official GitHub Copilot docs.

The durations below are rough planning estimates for someone studying around 8–10 hours a week. Adjust them to your own pace.

Path A: Manual testing first, then automation (most common)

1. Manual testing fundamentals (about 2 months)
2. SQL basics (about 1 month)
3. One programming language (about 2 months)
4. Playwright or Selenium (about 2 months)
5. Small framework with CI (about 1 month)
6. Apply for junior QA or automation roles

Path B: Direct SDET (harder, coding-first)

1. Programming in Java, Python or TypeScript (about 3 months)
2. Core data structures and problem solving (about 2 months)
3. Playwright or Selenium plus API automation (about 3 months)
4. CI/CD and a complete test suite (about 2 months)
5. Apply for SDET roles

Already a manual tester? Read manual vs automation testing career path before choosing.

A short, runnable repository is stronger evidence than a long list of tools on a resume. Aim for:

• One UI automation repo (Playwright or Selenium) with a README explaining how to run it
• One API testing project (Postman collection or code-based tests)
• One written bug analysis: what you found, how you reproduced it, and why it mattered

Your first runnable Playwright test

Requires Node.js 22, 24 or 26 (see the Playwright installation docs). Run npm init playwright@latest, then add tests/first.spec.ts:

import { test, expect } from '@playwright/test';

test('home page has the expected title', async ({ page }) => {
  await page.goto('https://playwright.dev/');
  await expect(page).toHaveTitle(/Playwright/);
});

test('Get started link opens the installation page', async ({ page }) => {
  await page.goto('https://playwright.dev/');
  await page.getByRole('link', { name: 'Get started' }).click();
  await expect(page.getByRole('heading', { name: 'Installation' })).toBeVisible();
});

Run: npx playwright test tests/first.spec.ts

Expected result: both tests pass in each browser project configured in playwright.config.ts (Chromium, Firefox and WebKit by default), and npx playwright show-report opens the HTML report.

Common first-week failures

• "Executable doesn't exist" — browsers were not downloaded. Run npx playwright install.
• Strict mode violation — your locator matched more than one element. Make it more specific, for example with getByRole and an exact name.
• Timeouts on assertions — the text or role you expect is different on the live page. Use npx playwright codegen to inspect the real locator.
• Tests pass locally but fail in CI — usually missing browsers or system dependencies. Use npx playwright install --with-deps in the pipeline.

For a guided version of this project, follow the Playwright course.

Certifications do not replace hands-on skills, but ISTQB Foundation Level is a common baseline in enterprise and European hiring and gives you shared vocabulary for interviews.

• ISTQB Foundation Level — testing fundamentals. Fees vary by country and exam provider; see our ISTQB certification cost guide and the official ISTQB site.
• ISTQB Advanced or specialist modules — test management, test automation engineering; useful after a few years of experience.
• Cloud or container certifications — helpful for SDET roles that own test infrastructure, not needed for a first QA job.

A typical QA interview process

1. Recruiter or HR screen — background, notice period, expectations
2. Technical round 1 — testing concepts, scenarios, SQL
3. Technical round 2 — automation, API testing, framework walkthrough, sometimes live coding
4. Manager round — collaboration, prioritisation, a difficult bug you handled
5. Offer discussion

Topics that come up most often

• Testing fundamentals: "What is the difference between smoke and sanity testing?"
• Scenario design: "How would you test a login page?"
• SQL: "Write a query to find duplicate emails."
• API: "How do you test pagination on an API?"
• Automation: "How is your Page Object Model structured, and how do you handle waits?"
• Behavioural: "Tell me about a bug that reached production."

Answer timed questions by skill and level in Interview Prep, then drill the Playwright, Selenium and API testing question guides. Practice out loud: knowing an answer and explaining it clearly under time pressure are different skills.

1. Use the words in the job description — Selenium, Playwright, API testing, SQL, CI/CD, regression — but only for skills you can demonstrate.
2. Describe outcomes you can explain — for example, what your suite covers, how long it runs, and a bug it caught. Do not invent percentages.
3. Link your portfolio at the top of the resume.

Follow how to write an ATS-friendly QA resume for formatting.

Where to find QA jobs

• Jobs Radar — QA and SDET openings in one place, filterable by skill and location
• LinkedIn, Naukri (India), Indeed and company career pages

Job titles to search

QA Engineer, Software Tester, Quality Assurance Analyst, Test Automation Engineer, SDET, API Test Engineer.

Titles and year ranges differ between companies; this is a typical shape of the ladder at product companies, not a fixed rule.

If you are aiming for the coding-heavy track, continue with the SDET career roadmap.

An example for a beginner studying part-time. Move faster or slower depending on how quickly you can produce each deliverable.

Want structured revision material? The QA Notes Vault has downloadable notes on SQL, API testing, Selenium and Playwright.

• Learning three automation tools at once. Pick one and finish a project with it.
• Skipping SQL and API testing. Both appear in many QA interviews, including for UI-focused roles.
• Copying a framework you cannot explain. Interviewers ask why each part exists.
• Using fixed sleeps in tests. Learn your tool's waiting model instead.
• Only reading, never answering out loud. Practice explaining answers before real interviews.

Related reading: What Degree Do You Need to Become a QA Engineer in 2026?.