Technology · Mid-career
QA Engineer Resume Example
A resume for a QA engineer whose strength is deciding what to test and finding what others miss, set in government digital services. It shows how to describe risk-based strategy, exploratory sessions, defect management and release reporting with real outcomes, without leaning on automation keywords.
The example resume
Laid out in the Schematic template. The person, employers, schools and figures in this example are invented for illustration. Any resemblance to real people or organisations is unintended.
Fatima Rahimi
QA Engineer
Contact
- fatima.rahimi@example.com
- +1 555 0181
- Ottawa, Canada
- linkedin.example.com/in/fatima-rahimi
Skills
Test design: test strategy, risk-based testing, exploratory testing, boundary value analysis, decision tables
Types of testing: functional, regression, accessibility (WCAG 2.1), usability, UAT, API, data migration
Tools: Jira, TestRail, Postman, SQL, browser developer tools, BrowserStack, NVDA
Ways of working: Scrum, defect triage, release readiness reporting
Certifications
ISTQB Certified Tester Foundation Level
ISTQB
2019
Languages
English: fluent, French: professional, Dari: native
Professional summary
QA engineer with eight years of experience testing public-facing government services, from benefits applications to pension administration. Plans risk-based test strategies, leads exploratory and accessibility testing, and runs defect triage with delivery teams. Writes bug reports developers can act on at first reading and gives a plain release readiness report for every release.
Work experience
QA Engineer
Cedar Row Digital Services, Ottawa
Oct 2021 – Present
- Wrote the test strategy for an online benefits application used by about 400,000 residents a year, prioritising eligibility rules and payment calculations by risk
- Led exploratory testing sessions with charters and session notes, finding 62 defects before launch that scripted cases had missed, 9 of them high severity
- Ran weekly defect triage with developers and the product owner, cutting the average age of open high-severity defects from 11 days to 3
- Tested each release against WCAG 2.1 AA with keyboard, NVDA and VoiceOver, and coordinated fixes for 48 accessibility issues before the public audit
- Planned user acceptance testing with 25 caseworkers across 3 offices and reported release readiness, with open risks, to the service owner for 22 releases
QA Analyst
Lockview Benefits Software, Ottawa
Jun 2018 – Sep 2021
- Designed and maintained 900 test cases in TestRail for a pensions administration product, using boundary value analysis and decision tables for calculation rules
- Reduced the regression cycle from 5 days to 3 by removing duplicate cases and ranking the rest by risk and defect history
- Verified data migrations for 4 client go-lives with SQL checks comparing record counts and calculated balances between old and new systems
- Logged defects with steps, test data, expected and actual results and evidence, so that very few were returned as not reproducible
Education
Bachelor of Information Technology
Carling Heights University, Ottawa
2014 – 2018
Open this example in the resume builder Start empty with this template
Why this resume works
- The summary says what kind of tester Fatima is (risk-based strategy, exploratory and accessibility testing, triage), so nobody mistakes this for an automation resume with the code removed.
- Test design techniques are named in context: boundary value analysis and decision tables for calculation rules, charters and session notes for exploratory work.
- Defect figures come with severity and consequence (62 found before launch, 9 of them high severity; average age of high-severity defects from 11 days to 3) instead of a bare bug count.
- Release readiness reporting and user acceptance testing with caseworkers show the judgement and communication side of QA, which is hard to demonstrate and often left out.
- French is listed with a level, which matters for a public-sector role in a bilingual city and costs one line.
What employers look for in this role
- Write test strategies and plans based on product risk
- Design test cases from requirements, user stories and acceptance criteria
- Carry out functional, regression, exploratory and accessibility testing
- Log, prioritise and track defects through to closure
- Run defect triage and report on release quality
- Support user acceptance testing with business users
- Review requirements early to find gaps and ambiguities before build
Skills to consider
List only the skills you can back up with an example. These are the ones that come up most for this kind of role.
- Test design and analysis
- Risk-based test planning, Exploratory testing with charters, Boundary value analysis, Equivalence partitioning, Decision tables, State transition testing, Requirements review
- Testing types
- Functional and regression testing, Accessibility testing, API testing, Cross-browser and mobile testing, Data and migration testing, User acceptance testing, Usability checks
- Tools and reporting
- Jira or Azure DevOps, TestRail, Xray or Zephyr, Postman, SQL for data checks, Browser developer tools, Defect metrics and release reports
More bullet points to adapt
Each of these follows the same pattern as the example: an action, what it was applied to, and what changed. Swap in your own facts and figures. The bullet builder assembles the pattern for you.
- Reviewed 140 user stories before development and raised 37 questions on acceptance criteria, preventing rework on 8 stories
- Created a regression pack of 120 high-risk cases that could be run in one day, used as the release gate for 15 releases
- Tested a payments change with 46 boundary cases around tax year dates and found a rounding defect affecting 2% of claims
- Wrote the team's definitions of defect severity and priority, ending recurring disputes in triage
- Tracked escaped defects for 4 quarters and showed that 60% came from one integration, which led to a dedicated test environment for it
- Paired with 2 developers to test stories on their branches, so most defects were fixed before the story reached the test column
Words that recur in adverts
These terms appear often in adverts for this kind of role. Use the ones that are true of you, in sentences that show the skill in use, and check a specific advert with the keyword checker.
Which sections to include
Open with a summary that says what you test and how you approach it, since QA titles cover everything from manual testing to pure coding. In the experience section, give the product, the size of its user base and the risks, then your strategy, your findings and the effect on releases. The skills section should separate test design techniques from testing types and tools; the techniques are what show you as an engineer and not only someone who executes tests. Certifications such as ISTQB sit well after skills. Spoken languages earn a line where the employer serves the public in more than one.
Mistakes to avoid
- Reporting only volume, such as "executed 2,000 test cases" or "raised 500 bugs", which says nothing about whether the right things were tested; add severity, risk and what changed as a result.
- Describing testing as a phase at the end ("tested the application after development") when employers want testers who review requirements and shape acceptance criteria early.
- Listing tools (Jira, TestRail, Postman) but no test design techniques, leaving the impression of someone who follows scripts written by others.
- Apologising for manual testing or hiding it behind a thin layer of automation keywords; exploratory, accessibility and usability testing are skilled work and should be described as such.
- Omitting the domain, even though knowledge of benefits rules, payments or clinical workflows is often why one tester finds defects another misses.
Questions and answers
Do I need automation skills on a QA engineer resume?
Many adverts ask for some, so mention any you have, such as API checks in Postman or SQL scripts, in proportion to your real experience. A role focused on strategy and exploratory testing does not require you to present yourself as a programmer. If the advert is mostly about building frameworks, see the automation tester example.
How can I quantify testing work?
Use measures of outcome: defects found before release by severity, escaped defects, regression cycle time, age of open defects, releases supported. Avoid raw counts of test cases run, which reward quantity. Where you have no figure, describe the risk you covered and the decision it informed.
Is ISTQB certification necessary?
It is not required for most roles, but some employers, particularly consultancies and public-sector suppliers, list it. If you hold it, include the level and year. If you do not, naming test design techniques in your bullets covers much of the same ground.
How do I mention defect counts without making the developers look bad?
Frame defects as found before release and by severity, and include what you did to help them get fixed, such as clear reproduction steps or triage. A resume that shows you working with developers reads better than one that keeps score against them.