Skip to content
Road MatesRoad Mates Enter

QA Engineer Roadmap

How to become a QA Engineer, phase by phase: what you do in each one, how long it takes, and the proof that shows you're done.

6 phases11–24 months14 resources

The road, phase by phase

  1. Phase 1: Learning Manual Testing Fundamentals

    1–2 months

    Studying testing concepts like test design techniques, bug lifecycle, SDLC, and agile, while practicing on real websites and apps. By the end, the person can write structured test cases and clear, reproducible bug reports.

    You're done when you can show

    A public document with test cases and bug reports written against a real web app.

    Resources

  2. Phase 2: Testing Real Software Publicly

    1–2 months

    Finding and reporting real bugs through crowdtesting platforms, open-source issue trackers, or volunteer projects. This proves the person can find meaningful defects in software they didn't build.

    You're done when you can show

    Links to accepted bug reports on a crowdtesting platform or open-source issue tracker.

    Resources

  3. Phase 3: Writing Automated Test Suites

    2–4 months

    Learning a programming language and building UI and API automation with tools like Selenium, Playwright, or Postman, plus SQL for data checks. The output is a working automation framework against a demo application.

    You're done when you can show

    A GitHub repo with a runnable UI and API test framework and a README.

    Resources

  4. Phase 5: Interviewing for QA Roles

    1–3 months

    Applying to QA and test automation positions, presenting portfolio projects, and practicing testing scenarios and coding questions. Ends with an accepted job offer.

    You're done when you can show

    A signed offer letter for a QA engineer position.

    Resources

  5. Phase 6: Owning Quality on Production

    6–12 months

    Testing features in a real team, writing and maintaining automation, triaging bugs, and collaborating with developers on releases. By the end, the person independently owns test strategy for a product area.

    You're done when you can show

    A test plan or automation contribution you authored for a shipped feature at work.

    Resources

Similar roads

Walk this road with people on it.

Track each phase, post your proofs, and get matched with people in the same phase.

Join this road — free →