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

97 out of 100, with one improvement remaining worth 8 points. The document has 170 readable words, and the volume rule's top band opens at 250. This is the shortest engineering page in this family.

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

Rubric, one of the 21 ATS-safe layouts out of 37. It marks sections clearly without a sidebar, which keeps a short page from looking sparse.

Example · Quality

A 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

— a suite that nobody trusts is worse than none.

The qa engineer example résumé drawn as a complete page in the Rubric design: name, summary, the roles with their bullet lines, education and a skills row — The example below, drawn by the builder's own renderer in the Rubric 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. Gwendolyn Achebe-Marsh does not exist, neither employer exists, and every figure was chosen to demonstrate a shape.

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. Works on the tests that catch real regressions and on the ones worth deleting.

Experience

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

Built an end-to-end suite of 340 tests covering 8 critical journeys, running in 11 minutes.
Cut escaped defects reaching production from 21 to 6 a quarter.
Deleted 190 flaky tests and raised pipeline pass rate from 74% to 97%.
Trained 12 developers to write and own their own tests.

QA Analyst · Fernthwaite Mobile, Sheffield · 2019 to 2022

Tested 30 releases a year across 2 mobile platforms and 14 device models.
Wrote 600 test cases and automated 240 of them.
Reduced regression testing from 4 days to 6 hours before each release.

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

Certifications
ISTQB Foundation · 2019

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.

What the reading found

The door on this page hands the document to the résumé builder as plain text, through the same import an uploaded file goes through, and the review shows every field beside the line it came from. Here the completeness pass found four readable sections, 100 words of experience evidence and ten distinct skills, with the certification kept with its year.

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 — The real import review, opened by this page's own door. It names Gwendolyn Achebe-Marsh as invented before anything is saved, and it shows every field beside the line it came from.

No language model is involved. Every string a reader emits is checked in code to be a span of the source document, and where the rules are unsure they ask rather than deciding quietly.

What the checker scored it

The same import review on a 390 pixel phone screen, with the example notice above the accept button — The same door on a phone. Nothing is withheld on the small screen: the notice, the reading and the accept button are all there.

Ninety-seven out of 100, with one improvement remaining worth 8 points. The arithmetic is 100 × 30% + 100 × 30% + 92 × 40% = 97, explained in the article on the score. Seven action-led lines, three of them measurable, seven lines of depth and 170 readable words against a band opening at 250.

This is the shortest page in this batch and it still scores 97, because the content rules reward evidence density rather than length up to the point where volume is counted. Your own page will be scored the same way by the ATS checker, with the count printed rather than implied.

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 certification if you have one, 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 Rubric 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: 97 out of 100, with one improvement remaining worth 8 points. The document has 170 readable words, and the volume rule's top band opens at 250. This is the shortest engineering page in this family.
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: Rubric, one of the 21 ATS-safe layouts out of 37. It marks sections clearly without a sidebar, which keeps a short page from looking sparse.

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 20 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.