A useful starting point
Show the product, the risk you covered, and automation if you have it. Two pages for SDETs; one for manual-only juniors. Skip “I have an eye for detail” with no cases. Skip this if you want a developer role — testing proof is not a substitute for shipped features.
These examples illustrate structure, not a real applicant’s history. Replace every sample detail with your own evidence. Follow the employer’s instructions on qualifications, registration, document length and file format.
Evidence to consider
- Manual and/or automated tests
- A defect you caught with impact
- CI hook
- Domain (payments, health, games)
Illustrative achievement bullets
- Wrote 60 Playwright cases for checkout; caught a tax-rounding bug before Black Friday
- Owned regression for a fortnightly release across iOS and Android
- Logged 140 issues in Jira with repro steps; 90% accepted first time
- Pair-tested accessibility on 12 core screens with engineering
Relevant skills to substantiate
Exploratory testing · Playwright · Jira · API tests · Accessibility checks · Release sign-off
What to leave out
- Photos
- Unowned “the team automated everything”
- Skill bars
Choose a layout
Explore the modern template or use it in the CV builder. This is a suggested layout; follow the vacancy’s requirements.