A fresher can be ready for QA interviews in about four months of focused work if the skills arrive in the right order: testing fundamentals, manual testing on a real app, SQL and API testing, one automation stack, CI basics, AI-assisted testing, and a portfolio. This roadmap sets out that order, what each stage should leave you with, and how hiring managers check for it.
Is testing still a career when AI writes tests?
Yes, and the job has moved. AI tools now draft test cases, suggest locators and explain failures. They do not decide what matters to test, notice that a requirement contradicts itself, or take responsibility for a release. Teams are hiring testers who can use those tools and still own quality. In practice, the fresher QA job post now reads: manual testing, SQL, API testing, one automation tool, and "familiarity with AI testing tools". That list is longer than it was five years ago, which is exactly why the order you learn it in matters.
Stage 1: fundamentals and the ISTQB vocabulary (2 weeks)
Learn the words before the tools, because interviews are conducted in them. The ISTQB Foundation Level syllabus (version 4.0) covers fundamentals of testing, testing through the development lifecycle, static testing, test analysis and design, managing test activities, and test tools. You do not need the certificate to get hired, but you do need to explain a test case against a test scenario, severity against priority, regression against retesting, the test levels from unit to acceptance, and black-box techniques like boundary value analysis and equivalence partitioning. Read the syllabus, make your own flashcards, and apply each technique to one feature of an app you use every day.
Stage 2: manual testing on a real app (3 weeks)
Pick a real web application with a public demo or test environment, write a short test plan, and test it properly: a requirement walkthrough, test scenarios, test cases with steps and expected results, then execution with a defect log. Report bugs the way a developer needs to read them: title, steps to reproduce, expected against actual, environment, severity, screenshot. Track them in Jira or a free equivalent. Keep the plan and the bug reports in a folder you can show. This stage is where you learn to think like a tester, and it is the part most freshers skip to reach automation sooner. Hiring managers notice.
Stage 3: SQL and API testing with Postman (3 weeks)
Testers check data, and data lives in databases and behind APIs. For SQL, learn SELECT with WHERE, ORDER BY and GROUP BY, the common JOINs, and enough to verify that the record the UI shows matches the row in the table. For APIs, learn HTTP methods, status codes, headers, JSON bodies and token-based authentication. In Postman, build a collection against a public API: a login request that stores a token, requests that use it, and test scripts that assert on status codes and response fields. Chain the requests so one feeds the next. This is the first automation you will write, and it is what most fresher interviews turn to after the manual round.
Stage 4: one automation stack, Playwright with TypeScript (5 weeks)
One stack learned deeply beats three learned shallowly. For a fresher in 2026 that stack is Playwright with TypeScript; our Playwright vs Selenium comparison explains why. Learn programming basics first: variables, types, conditionals, loops, functions, async and await. Then Playwright itself: locators, auto-waiting, assertions, codegen, the trace viewer, fixtures, parallel runs, and a Page Object Model so your tests stop repeating themselves. Finish with a framework that covers one application end to end, with UI and API tests in the same project.
Stage 5: CI basics (1 week)
A suite that runs only on your laptop is a demo. Put the project on GitHub and add a workflow that runs the tests on every push. Playwright generates a GitHub Actions file at setup; read it line by line until you can explain each step: check out the code, install Node, install dependencies and browsers, run the tests, upload the report. Then make one test fail on purpose and read the report from the Actions tab. That is the whole of CI for a fresher interview.
Stage 6: AI-assisted testing (alongside stages 2 to 5)
Use AI tools the way working testers do, with a check on everything. ChatGPT or Gemini to draft test cases from a requirement, then you cut the weak ones and add the edge cases it missed. GitHub Copilot or Cursor to draft a Page Object, then you fix the locators. The Playwright MCP server lets an AI assistant drive a browser through the page's accessibility tree, which is useful for exploring a screen and drafting a first test. In an interview, be ready to explain where the tool was wrong and how you caught it. That answer shows judgement, and judgement is what the AI line in the job post is screening for.
Practical tip. Keep a file called ai-misses.md in your project. Every time an AI tool gives you a wrong locator, a test that passes for the wrong reason, or a test case that misses a boundary, write one line about it. After a month you have a page of specific examples for the "how do you use AI in testing" question, and nobody else in the room will have one.
Stage 7: a portfolio on GitHub
By the end you should have four things a recruiter can open: a test plan with bug reports for a real app, a Postman collection with scripted assertions, a Playwright framework with a README that explains how to run it, and a green CI run with an HTML report. Write the README for someone who has two minutes. Pin the repository on your GitHub profile and link it from your resume and LinkedIn.
Stage 8: interview prep (2 weeks)
Fresher QA interviews usually run in this order: an HR screen, a manual round with scenarios, test case writing and bug reporting, a technical round with SQL queries, API questions and either a short automation exercise or a walk-through of your project, then a manager round. Practise explaining your project out loud in three minutes. Do mock interviews with someone who works in testing and ask them to interrupt you. Collect the questions you could not answer and close those gaps the same week.
What hiring managers screen for
In the first ten minutes of a fresher interview, in rough order of weight:
- Whether you can write a clear test case for a feature you have never seen.
- Whether you can report a bug so a developer can reproduce it without asking you.
- Whether you know what a status code is and can write a JOIN.
- Whether you have automated anything you can show, and can explain any line of it.
- Whether you use AI tools, and know when they are wrong.
- Whether you can talk about what you built without reading from your resume.
Certificates come after all of that.
Common mistakes
- Starting with automation and skipping manual testing. You end up able to click buttons in code without knowing which buttons matter.
- Learning two or three tools at once. Selenium, Cypress and Playwright in the same month leaves you unable to explain any of them.
- Watching instead of building. Forty hours of videos leaves nothing a recruiter can open. Ten hours of building does.
- A resume that lists tools without a project behind each one. Interviewers now ask "show me" and the list collapses.
- Treating ISTQB as the goal. It is vocabulary, and a useful one. It is not evidence that you can test.
- Hiding the AI tools you use, or trusting them blindly. Both lose you the AI question. Use them, check them, and say so.
A four-month plan
This is the order we run the QA Career Track in, and it works just as well on your own if you keep to it.
| Month | Focus | You end with |
|---|---|---|
| 1 | Testing fundamentals, STLC, manual testing on a real app, Jira, web and database basics, SQL, Git and GitHub | A test plan, Jira bug reports, your first SQL queries, a GitHub account with your first commits |
| 2 | AI in testing, TypeScript essentials, first Playwright tests, API testing with Postman, an exit project | A Postman collection with assertions, your first Playwright scripts, a complete test plan for one app |
| 3 | Parallel and cross-browser Playwright, a Page Object Model framework, API automation in code | A framework on GitHub that covers one application's UI and API |
| 4 | GitHub Actions and Docker, performance testing basics, a capstone, resume and mock interviews | A CI pipeline, a capstone project, and a three-minute walk-through you can give from memory |
Four months assumes two hours on weekday evenings plus weekend assignments, and that you build something every week rather than finishing a module and moving on.
What to do next
If you want this plan with a trainer, graded assignments and someone to check your test cases, the QA Career Track follows these four months exactly, and finishes with placement assistance through our network of 100+ hiring partners. A counsellor can tell you on one call where to start from where you are now: request a call-back. We also run a free three-hour Playwright + AI masterclass on Zoom, where you write a real automated test.