Most tester resumes in India read the same: “Executed test cases, logged defects in JIRA, performed regression testing.” Recruiters screening hundreds of QA profiles cannot tell candidates apart from lines like these. This guide shows how to turn testing work into specific, believable evidence, with examples for manual testers, automation engineers and SDETs.
Certification and tool details mentioned here were checked against official sources in October 2026. For general formatting, see our separate guides on ATS-friendly and fresher resumes.
Start with the role you want, not the role you have
Write a two-line summary aimed at your next job. A manual tester moving to automation should lead with automation skills and projects, even if they are newer. Compare:
- Weak: “QA professional with 4 years of experience in manual testing seeking a challenging role.”
- Strong: “QA engineer with 4 years in banking web and mobile testing, now automating regression with Selenium (Java) and REST Assured; reduced a 2-day manual regression to 3 hours of automated runs.”
Write outcome-based bullet points
Use the pattern action + scope + tool + result. Testing results can be measured more often than people think.
| Duty-style bullet (avoid) | Outcome-style bullet (use) |
|---|---|
| Executed regression test cases | Ran risk-based regression of 400 cases per sprint for a UPI payments module; zero severity-1 escapes in 6 releases |
| Logged defects in JIRA | Raised 120+ defects in 2025, 30% caught at requirement review stage before coding |
| Worked on Selenium automation | Built 180 Selenium (Java, TestNG) tests with Page Object Model; cut regression from 2 days to 3 hours |
| Did API testing | Automated 90 REST Assured tests for order and payment APIs in GitHub Actions, running on every pull request |
| Responsible for test planning | Wrote test plans and estimates for 4 releases; delivered all on schedule with documented residual risks |
Use only numbers you can defend in an interview. Approximate honestly (“about 30%”) rather than inventing precision.
Skills section: group it, keep it honest
Group skills so a recruiter can scan them in seconds:
- Testing: test design (boundary values, decision tables, state transitions), risk-based testing, exploratory testing, defect management.
- Automation: Selenium WebDriver (Java), Playwright (TypeScript), TestNG, pytest.
- API and data: Postman, REST Assured, SQL.
- DevOps: Git, GitHub Actions or Jenkins, Docker basics.
- Domains: banking, insurance, e-commerce, healthcare.
List only tools you could discuss for ten minutes. Interviewers in India commonly pick a tool from the skills list and ask you to code with it.
Presenting certifications
- Write the exact name and version: “ISTQB Certified Tester Foundation Level (CTFL) v4.0”, with the year passed. ISTQB certificates do not expire, according to the Indian Testing Board.
- If you have advanced or specialist certificates, list them by name, for example CTAL-TAE v2.0 or CT-GenAI.
- ITB runs a certificate verification service and a certified testers directory, so recruiters can check your claim.
- Free tool certificates, such as TestMu AI’s Selenium or Playwright certificates with practical assignments, go in the same section but lower down.
- Do not list course completion certificates as certifications. Put them under “Training” if they are relevant.
Add a portfolio link that works
For automation and SDET roles, a GitHub link is often the most persuasive line on the page:
- Pin one or two repositories. Quality matters more than quantity.
- Write a README covering what the project tests, the tech stack, how to run it and a short architecture diagram or description.
- Include a CI badge or workflow so reviewers can see tests running.
- Remove client code and data. Never upload employer code.
Examples by career stage
Manual tester (3-5 years)
Lead with domain knowledge and test design. Include one automation or API line if you have started learning, and be honest about the level (“scripting basic Selenium flows in Java”).
Automation engineer
Lead with framework ownership: what you built or improved, how it runs in CI, how you reduced flakiness and the time saved.
SDET
Show engineering depth: languages, test levels (unit, API, contract, UI), tooling you built, pipeline work and any performance or reliability testing.
Test lead
Show planning and leadership: team size, releases delivered, process improvements and stakeholder reporting, with results.
Tailor it for each application
Keep a master resume, then adjust it for each job in five minutes:
- Mirror the job post’s tool names where they are true for you (“Playwright with TypeScript”, not just “Playwright”).
- Move the most relevant project to the top of your experience section.
- Swap your summary line to match the role type: manual QA, automation, SDET or lead.
- Check that the domain matches. A banking role should see your banking work first.
Mentioning AI tools
It is reasonable to list AI-assisted testing if you have done it. Describe how you controlled quality: “Used AI to draft API test cases, then reviewed and corrected assertions and negative scenarios before merging.” Avoid vague claims like “expert in AI testing”.
Final checklist before sending
- Two pages at most; one page if you have under three years of experience.
- Every bullet starts with a verb and, where possible, has a result.
- Tools in the summary match the job description and you can actually use them.
- Certificates have exact names and versions.
- Portfolio link opens and the README is clear.
- No confidential client names if your contract forbids them. Describe the domain instead.
Frequently asked questions
Should a manual tester include automation skills that are still being learned?
Yes, if you label the level honestly and can demonstrate something, such as a GitHub project. Overstating skills usually comes out in technical rounds and hurts more than it helps.
Is ISTQB worth mentioning on a resume?
Yes. It is a recognised, verifiable certificate, and recruiters can filter resumes on the keyword. Include the version and year, and back it with project examples of the techniques.
How do I describe testing work under NDA?
Describe the domain and scale without naming the client, for example “a retail banking mobile app used by customers across India”. Include user numbers only if they are public and you can verify them. Focus on your actions and results.
Official sources
- Indian Testing Board: FAQs (certificate validity)
- Indian Testing Board: Certificate verification
- ISTQB: All certifications
- TestMu AI: Free certifications

Leave a Reply