Key takeaways
- A junior QA CV should prove three things fast: you understand testing, you've practised it (portfolio), and your past experience brings transferable skills. Keep it to one or two pages.
- Write bullet points as action + what + result, and use the keywords from the job ad (test cases, bug reports, Jira, Postman, SQL, Agile) truthfully. Many companies filter CVs with software before a person reads them.
- On LinkedIn, use a clear headline, a short About section, your portfolio under Featured, and turn on Open to work for recruiters.
What a recruiter looks for in 30 seconds
Recruiters often skim a CV in well under a minute. For a junior tester, they're looking for:
- A clear target: "Junior QA Engineer", not "looking for opportunities in IT".
- Evidence of testing: a portfolio link, real bug reports, tools used.
- Signals of the tester mindset: attention to detail, clear writing, curiosity.
- No errors. A typo in a tester's CV is noticed.
The structure
- Header: name, city (or "remote"), email, phone, LinkedIn URL, portfolio/GitHub link.
- Summary (2–3 lines): who you are, what you can do, what you're looking for.
- Skills: grouped and honest: testing, tools, technical, languages.
- Testing projects / portfolio: the work that proves your skills. For career changers, put this before work experience.
- Work experience: reverse chronological, with bullets that highlight transferable skills.
- Education and certifications: degree, courses, ISTQB if you have it.
Example summary
Junior QA tester with hands-on practice in manual and API testing. Designed 60+ test cases and reported 25 bugs across two web apps; built a Postman collection and a Playwright suite running in GitHub Actions. Five years of customer-facing experience in retail, used to finding and explaining problems clearly. Looking for a junior QA role in an Agile team.
Testing projects: bullets that show results
| Weak | Strong |
|---|---|
| "Did testing on a website." | "Designed 22 test cases for the checkout of a demo shop using equivalence partitioning and boundary values; found 4 bugs, including a discount applied twice." |
| "Used Postman." | "Built a 15-request Postman collection with automated checks for status codes, validation errors and response structure; runs with Newman." |
| "Know Playwright." | "Wrote 8 Playwright UI tests (TypeScript) covering login, cart and checkout; running on every push with GitHub Actions." |
Translating your past experience
You've already done tester-like work. Name it:
| Previous role | Transferable skill | Example bullet |
|---|---|---|
| Customer support | Reproducing and describing problems | "Logged 30+ customer issues a week with reproduction steps, cutting back-and-forth with the tech team." |
| Retail / hospitality | Attention to detail, process | "Ran weekly stock audits, finding discrepancies and tracing them to their cause." |
| Accounting / admin | Precision, checking against rules | "Reconciled monthly invoices against contracts, catching billing errors before payment." |
| Teaching / training | Explaining clearly, structured thinking | "Wrote step-by-step training guides used by 15 new staff." |
| Any job with software | Using and noticing software problems | "Was the go-to person for problems with the booking system; reported issues to the vendor with screenshots and steps." |
Keywords and automated filters
Many companies use an applicant tracking system (ATS) that scans CVs for keywords before a person reads them.
- Read the ad and mirror its words where they're true: "test cases", "bug reports", "regression testing", "Jira", "Postman", "SQL", "Agile/Scrum", "API testing".
- Use a simple layout: one column, standard headings, no text inside images, and save as PDF unless the ad asks otherwise.
- Adapt the CV for each application. Reorder skills and the summary to match the ad. It takes 10 minutes and makes a real difference.
- Headline: "Junior QA Tester | Manual & API testing | Postman, SQL, Playwright". Not just "Looking for a job".
- About: 4–6 lines: your story in brief, what you can do, what you're looking for, and a link to your portfolio.
- Featured: pin your portfolio, your best bug report (as PDF), and your GitHub.
- Skills: add the same keywords as on your CV.
- Open to work: set your target roles and locations. You can choose to show it only to recruiters.
- Activity: an occasional short post about something you learned ("3 bugs I found testing sign-up forms") makes your profile more visible.
Ioana (an illustrative example) worked for six years in a call centre. Her first CV listed her duties: "answered calls", "used CRM", "met targets". It also had "Completed QA course" under education. She applied for 25 junior QA roles and got no replies.
She rewrote it. The summary now started with "Junior QA tester". A Testing projects section came first, linking her portfolio. Her call centre bullets became: "Documented 40+ technical issues a week with exact steps and screenshots for the IT team" and "Spotted a recurring CRM error affecting refunds; my report led to a fix that reduced related complaints."
Within three weeks she had three interview invitations. In two of them, the first question was about the CRM bug.
Lesson: the experience was the same. The second CV showed it through a tester's eyes.
Do
Lead with a testing summary and your portfolio, use specific numbers and tools you've really used, and adapt the CV for each ad.
Don't
Send one generic CV everywhere, listing duties without results, with a skills section full of tools you've only heard of.
Check yourself
A job ad asks for 'experience with SQL'. You've practised SELECT, WHERE and JOIN on a sample database for two weeks. How do you put it on your CV?
Show answer
Be specific and honest: under skills, "SQL (SELECT, WHERE, JOIN, GROUP BY) – practised on sample databases", and under projects, a bullet like "Wrote SQL queries to verify test data and order totals in a demo shop's database". That uses the keyword truthfully, and gives the interviewer something concrete to ask about.
