Is Gwendolyn Achebe-Marsh a real person

No. She is invented for this page, and so are Brackenhall Software and Fernthwaite Mobile. Every figure was written to show a shape.

Is a test count a good metric

On its own it is a vanity number. The example pairs 340 tests with eight critical journeys and an eleven-minute runtime, which turns a count into a description of a suite somebody has to live with.

Why mention deleted tests

Because deleting 190 flaky tests and taking the pipeline pass rate from 74% to 97% is the most valuable thing a QA engineer does, and almost nobody writes it down. A suite nobody trusts is a suite nobody reads.

What did the checker score it

99 out of 100, re-measured on 25 September 2026, with readable volume 2 points short and achievement quality 1 point short. The arithmetic is 100 × 30% for parseability + 100 × 30% for completeness + 97 × 40% for content. The writing check beside it scored 95, which is 91 of the 96 points that applied, and the five it withheld are the bullet tense rule.

Does manual testing still belong on a résumé

Exploratory testing does, and it should be named as that. Thirty releases a year across fourteen device models is manual work described precisely enough that nobody mistakes it for clicking around.

Which design is this rendered in

Classic, one of the eight layouts in the ATS family. The eight were chosen from a measurement taken on 2026-09-14: each exports a PDF whose text layer scores exactly what the pasted text scores, on both test documents, in one column, with the reading order kept and no graphics. It marks sections clearly without a sidebar, which keeps fifteen short lines from running together.

Example · Quality

A free QA engineer résumé example, including the tests it deleted

One complete QA engineer résumé, written out in full. The person is invented. The reading and the score come from the product itself.

ConxfolioPublished 2026-09-13 · updated 2026-09-25

— a suite that nobody trusts is worse than none.

The QA engineer example résumé drawn as a complete page in the Classic design: name, summary, three dated roles with five achievement lines under each, education and a skills row — The example below, drawn by the builder's own renderer in the Classic design. The picture was taken by pressing this page's own Use this example door and photographing what the editor rendered.

Quality work is easy to count badly. Test totals, bug totals and coverage percentages all go up without anything getting better. This example is written out in full so you can read what the useful version looks like, then put through the tools here to see what a parser takes from it. The candidate is invented.

The example, in full

An invented person. Not a real document, and not yours.

Gwendolyn Achebe-Marsh
QA Engineer
Leeds, United Kingdom · [email protected] · +44 113 496 0355

Summary
QA engineer with six years on web and mobile products, working on automated suites, release risk and the flaky tests worth deleting. Owns a pipeline of 340 tests across 8 journeys for 3 product teams.

Experience

Senior QA Engineer · Brackenhall Software, Leeds · 2022 to present

Built an end-to-end suite of 340 tests covering 8 critical user journeys, and held the whole run inside 11 minutes on every merge.
Cut escaped defects reaching production from 21 to 6 a quarter across 3 product teams, and kept that level for 7 straight releases.
Deleted 190 flaky tests from the pipeline and raised the pass rate from 74% to 97% over 2 quarters of steady triage work.
Trained 12 developers to write and own their own tests, and watched unit coverage on new code climb from 48% to 79%.
Wrote the release checklist that 4 teams now follow, and cleared 9 of every 10 sign-off questions without a call to an engineer.

QA Analyst · Fernthwaite Mobile, Sheffield · 2020 to 2022

Tested 30 releases a year across 2 mobile platforms and 14 device models, and signed off each one against a written risk list.
Automated 240 of 600 written test cases over 18 months and cut the manual regression pass from 4 days to 6 hours.
Reduced crash-free session loss on 2 platforms by 38% after tracing a memory leak that 3 previous releases had carried unnoticed.
Ran the device laboratory of 14 test units and kept every model on a supported operating system for 2 years without a gap.
Documented 120 known defects with reproduction steps so the support team answered 7 in every 10 customer reports without escalation.

Junior QA Tester · Fernthwaite Mobile, Sheffield · 2019 to 2020

Executed 400 manual test cases a month against 2 mobile applications and logged every failure with a reproduction path and a screenshot.
Prepared the test data sets for 30 releases and removed a setup step that had cost the team 5 hours every week.
Verified 90 defect fixes a month and returned 12% of them to the developers with evidence that the original fault survived.
Checked 60 pages of the mobile application against accessibility guidance and raised 84 issues that the design team fixed before release.
Supported 24 overnight deployments in a year and reported every blocking defect inside 20 minutes of the first failing build.

Education
BSc Computing · Aireborough University, Leeds · 2015 to 2019

Skills
test automation, Playwright, Cypress, API testing, exploratory testing, accessibility testing, CI pipelines, defect triage, test strategy, mobile testing

Languages
English · native · French · B1

Certifications
ISTQB Foundation · 2019
ISTQB Advanced Test Analyst · 2023

The one number that matters is what got out

Escaped defects reaching production from 21 to six a quarter. That single line is what a head of engineering is buying, and everything else on the page is an explanation of how it happened.

The suite line supports it: 340 tests across eight critical journeys, running in eleven minutes. Runtime belongs there because a suite that takes an hour is a suite developers learn to skip, and a QA engineer who thinks about that is a different hire from one who only counts cases.

Deleting is the senior move

One hundred and ninety flaky tests deleted, pipeline pass rate from 74% to 97%. Removing work is harder to justify internally than adding it, and it is the line most likely to start a real conversation at interview.

Training twelve developers to own their own tests is the second half of the same idea. A quality engineer whose value depends on being the only person who can run the suite has built a bottleneck rather than a practice.

Skills for a QA engineer résumé, grouped

Gwendolyn's skills group into automation, testing and delivery. Automation: test automation, Playwright, Cypress, API testing. Testing practice: exploratory testing, accessibility testing, mobile testing. Delivery: CI pipelines, defect triage, test strategy. An engineering manager reads the strategy item as a sign you decide what to test, not only how.

Manual testers moving into automation can keep a smaller automation group and grow it. The free résumé builder lets you name groups and move skills between them as your toolkit changes.

From junior tester to senior QA

A junior tester's résumé counts defects found and test cases run, as the Fernthwaite junior role does. An analyst adds coverage and the escape rate: what reached users and how that fell. The senior role adds decisions: suites retired, flaky tests removed, the release gate you designed.

Deleting tests is a senior move, and the example says so in a line. At every level, put what reached production next to what you caught, because that is the result a team lives with. The certifications guide covers where ISTQB belongs.

How it reads and scores

The import review read three dated roles with five lines under each, one degree, ten skills, two languages and two certifications, each kept with its year. The ATS checker scored it 99 out of 100, re-measured on 25 September 2026, with readable volume 2 points short and achievement quality 1 point short: 100 × 30% for parseability, 100 × 30% for completeness and 97 × 40% for content. The writing check scored it 95, which is 91 of the 96 points that applied here. The same check runs on every example; the method is described here.

The Conxfolio import review after the door opened, showing Gwendolyn Achebe-Marsh's example read into fields beside the rendered page, with the line saying it is an example — Gwendolyn Achebe-Marsh's qa engineer résumé read into fields, each field beside the line it came from.

The same import review on a 390 pixel phone screen, with the example notice above the accept button — Gwendolyn Achebe-Marsh's qa engineer résumé in the same review on a 390 px phone.

What this example leaves off

No coverage percentage. Line coverage rises without quality rising, every engineer knows it, and quoting it invites a sceptical reading of everything else on the page. Escaped defects is the honest version of the same claim.

Bug counts raised are left off too. A tester who raises 900 bugs may be finding real problems or may be filing noise, and the number alone cannot tell a reader which. What got out, and what the pipeline pass rate became, are the figures that separate the two.

What to change for your own

Change the surface and the risk. Embedded, games, regulated finance and mobile all use this shape and care about different failures. Then put in your own escaped defect counts, suite runtimes and pass rates, and name the framework you actually work in.

Keep one line about something you removed. Keep the certifications you hold, each with its year. The guide on experience bullets covers the construction used here, the design gallery holds 37 layouts, and the DevOps example, the product manager example and the UX designer example sit beside this one.

Write yours beside it

Opens the builder with Gwendolyn's example loaded, saved as its own entry in the Classic design. Replace every line with your own. Free, no account.

Use this example Check a résumé instead

Questions

Is Gwendolyn Achebe-Marsh a real person: No. She is invented for this page, and so are Brackenhall Software and Fernthwaite Mobile. Every figure was written to show a shape.
Is a test count a good metric: On its own it is a vanity number. The example pairs 340 tests with eight critical journeys and an eleven-minute runtime, which turns a count into a description of a suite somebody has to live with.
Why mention deleted tests: Because deleting 190 flaky tests and taking the pipeline pass rate from 74% to 97% is the most valuable thing a QA engineer does, and almost nobody writes it down. A suite nobody trusts is a suite nobody reads.
What did the checker score it: 99 out of 100, re-measured on 25 September 2026, with readable volume 2 points short and achievement quality 1 point short. The arithmetic is 100 × 30% for parseability + 100 × 30% for completeness + 97 × 40% for content. The writing check beside it scored 95, which is 91 of the 96 points that applied, and the five it withheld are the bullet tense rule.
Does manual testing still belong on a résumé: Exploratory testing does, and it should be named as that. Thirty releases a year across fourteen device models is manual work described precisely enough that nobody mistakes it for clicking around.
Which design is this rendered in: Classic, one of the eight layouts in the ATS family. The eight were chosen from a measurement taken on 2026-09-14: each exports a PDF whose text layer scores exactly what the pasted text scores, on both test documents, in one column, with the reading order kept and no graphics. It marks sections clearly without a sidebar, which keeps fifteen short lines from running together.

Conxfolio is a free set of four career tools: a résumé builder with 37 rendered layouts, an ATS résumé checker that prints its own arithmetic, a cover letter builder that traces every proof paragraph back to the line it came from, and a portfolio builder with 22 authored designs. There is no account to create, nothing is held back for a paid plan, and no language model is used anywhere in the product, so the readers, the score and the letter are deterministic code you can check.