Software Testing
Learn the essentials5 min readPublished November 12, 2026

From zero to your first QA job: a step-by-step roadmap

A realistic path for people with no IT background: what to learn and in what order, which articles to read, what to build to prove your skills, and when to start applying. Five phases, with time estimates and checkpoints.

On this page

Key takeaways

  • You don't need a computer science degree to become a tester. You need solid testing fundamentals, basic technical skills (web, APIs, SQL, a tracker), proof you can do the work, and a clear way to show it.
  • The path has five phases: foundations → test design and bugs → tools → proof → applying and interviewing. At about 8–10 hours a week, many people need roughly 3 to 6 months; your pace may differ.
  • Don't wait until you "know everything" to apply. Start applying once you have a small portfolio and can explain the basics with examples.

Before you start: is this for you?

Testing suits people who are curious, notice details and can explain a problem calmly. Read what it means to be a software tester and QA job titles explained first. If it sounds like work you'd enjoy, this roadmap is for you.

Phase 1: Foundations (about 3 weeks)

Goal: understand what testing is, how software is built, and the vocabulary used in job ads and interviews.

Read, in order:

  1. What is software testing?
  2. The 7 principles of testing
  3. Error, defect, bug, failure
  4. The SDLC and testing
  5. The software testing life cycle (STLC)
  6. Agile and Scrum for new testers
  7. Levels of testing and functional vs non-functional testing
  8. Verification vs validation and static testing

Checkpoint: can you explain, out loud and with an everyday example, the difference between a defect and a failure, what happens in a sprint, and why exhaustive testing is impossible?

Phase 2: Test design and bugs (about 3 weeks)

Goal: design good tests and report bugs clearly. This is the core of the job.

  1. Black-box, white-box and experience-based testing
  2. Requirements and traceability and acceptance criteria and BDD
  3. Test case, test plan and test strategy and how to write a good test case
  4. Equivalence partitioning and boundary value analysis
  5. Exploratory testing and how to think like a tester
  6. How to write a great bug report, the bug life cycle and severity vs priority
  7. Regression vs retesting and smoke vs sanity

Practice: pick a website you use. Write 15 test cases for one feature (search, sign-up, cart), run them, and write up every real bug you find.

Phase 3: Tools and technical basics (about 4 weeks)

Goal: be comfortable with the tools listed in most junior job ads.

  1. How the web works
  2. Browser DevTools
  3. Jira and bug trackers
  4. Test environments
  5. SQL and test data
  6. Your first API test with Postman
  7. Manual vs automated testing, the test pyramid and your first automated test

Checkpoint: can you find a failing request in the Network tab, write a simple SQL query with a JOIN, and run a Postman collection with tests?

Phase 4: Build proof (about 2–3 weeks, overlapping with phase 5)

Goal: create work an employer can see. Without job experience, your portfolio is your experience.

Follow how to build a QA portfolio with no experience: a test plan, test cases, bug reports, a Postman collection and a small Playwright project on GitHub.

Optional: consider the ISTQB Foundation certificate. It helps in some markets and some companies, but it doesn't replace a portfolio.

Phase 5: Apply and interview (ongoing)

  1. Write your QA CV and LinkedIn profile.
  2. Find openings: job boards, internships, crowdtesting, internal moves.
  3. Prepare with junior QA interview questions and practical interview tasks.
  4. Once hired: your first 90 days.

A weekly rhythm that works

DayActivity
2–3 eveningsRead 2–3 articles; take notes in your own words
1 eveningPractise on a real or demo app: test cases, bugs, tools
Weekend blockBuild a portfolio piece; review the week
Every weekExplain one concept out loud, as if in an interview
Real-world exampleFrom shop floor to QA team

Andreea (an illustrative example) worked as a retail store manager and wanted a career change. She studied in the evenings, about 8 hours a week.

In the first two months she worked through the fundamentals and test design. She practised by testing her favourite online shop and the store's own ordering app, writing up 12 bug reports in a shared document.

In month three she learned DevTools, Postman and basic SQL, and built a small portfolio: a test plan, her best bug reports, a Postman collection and a five-test Playwright project on GitHub. She rewrote her CV to highlight what transferred: handling customer complaints (describing problems clearly), stock audits (attention to detail), training new staff (communication).

She applied to around 40 positions over two months, got five interviews and accepted a junior QA role at the end of month five. In the interview, she was asked to walk through one of her bug reports, and that was what got her the offer.

Lesson: a steady routine, a visible portfolio and a CV that translates your past experience matter more than how fast you finish the reading.

Do

Learn, practise, build proof and start applying in parallel once you have the basics. Interviews themselves teach you what to study next.

Don't

Spend months collecting courses and certificates without ever testing a real app or showing anything you made.

Check yourself

You've finished phases 1 and 2, but you're nervous about applying because you haven't learned automation yet. Should you wait?

Show answer

Not necessarily. Many junior roles are manual or mixed, and employers hire for solid testing fundamentals, clear bug reports and willingness to learn. Build a small portfolio (test cases plus bug reports) and start applying while you work on phase 3. Mention honestly that you're learning Postman and Playwright, and show what you've done so far.