Is Ada Fennimore a real person

No. She is invented for this page, and so is Northwind Pay. Every number in her résumé was written to demonstrate a shape, and none of it describes anyone's career. We do not publish real people's documents.

What does “Use this example” do

It opens the résumé builder, reads this example through the same import an uploaded file goes through, and saves it as a NEW entry called “Example · Software engineer”. Anything already saved on your device is untouched and stays in your Workspace.

Can I copy this example

Copy the structure, not the sentences. Three dated roles, five achievement lines under each, every line opening with a verb and carrying a figure where a figure exists, is a shape that survives any parser. The claims have to be yours or the document is worthless.

What did the checker score it

98 out of 100, re-measured on 25 September 2026, with readable volume 4 points short and achievement quality 2 points short. The arithmetic is 100 × 30% for parseability + 100 × 30% for completeness + 94 × 40% for content. The writing check scored it 95, which is 91 of the 96 points that applied to it.

What did the import review read

3 roles, 1 degree, 3 languages and 10 skills, each shown beside the line it came from before anything reached the editor. The review lets you correct any field before you accept it.

Does the example work for a junior engineer

The shape does. Replace the roles with projects and coursework, keep the verb-first lines and the figures, and the same structure reads correctly. The builder keeps a projects section for exactly that.

Which design is the example rendered in

Classic, an ATS-safe layout. The picture at the top of this page is that document drawn by the builder’s own renderer, and the door below opens the builder on the same design. Any of the 37 designs renders the same content, and 24 of them are marked ATS-safe.

Example · Engineering

A free software engineer résumé example, and what a parser makes of it

One complete backend engineer résumé, written out in full. The person is invented. The reading, the score and the screenshots are real.

ConxfolioPublished 2026-09-12 · updated 2026-09-25

— structure first. the wording is the easy half.

The example résumé drawn as a complete page in the Classic design: name, summary, two roles with bullet lines, one degree 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.

Most résumé examples are a picture of a finished page and a paragraph of encouragement. This one is written out in full, so you can read the lines, and then put through the two tools on this site so you can see what software makes of it. The candidate is invented.

The example, in full

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

Ada Fennimore
Backend Engineer
Berlin, Germany · [email protected] · +49 30 1234 5678

Summary
Backend engineer with nine years on payment systems and data pipelines, working on reliability, cost and settlement correctness. Leads a platform group of six engineers and writes the runbooks the on-call rota depends on.

Experience

Senior Backend Engineer · Northwind Pay, Berlin · 2021 to present

Rebuilt the settlement pipeline for 3 payment schemes and held end-of-day reconciliation inside 6 minutes on 400 000 daily transactions.
Reduced database cost by 31% a year by moving cold ledger rows into partitioned storage and rewriting the two reports that read them.
Led a platform team of 6 engineers through a scheme migration that touched 22 services and shipped without a customer-visible outage.
Wrote the on-call runbook the team still works from, and saw paging incidents fall from 9 a quarter to 2 over 18 months.
Mentored 4 engineers through their first production releases, their first on-call weeks and their first incident reviews.

Backend Engineer · Leitmotiv GmbH, Leipzig · 2018 to 2021

Built the invoicing service that carried 2.3 million transactions a day at 99.97% availability across 5 markets.
Cut checkout errors by 46% by tracing a race condition in the payment retry queue that 3 teams had looked at.
Migrated 14 services off a shared monolith onto independent deployments across 11 months with no rollback.
Designed the integration suite that covered 320 test cases, ran on every merge and caught 96 defects before release.
Removed 1 200 manual finance tickets a year by rebuilding the refund flow and giving support a self-serve view.

Junior Backend Engineer · Leitmotiv GmbH, Leipzig · 2016 to 2018

Shipped 40 releases of the internal ledger API in the first year without a single rollback or production incident.
Automated the nightly reconciliation report and returned 6 hours a week to a finance team of 4 people.
Documented 28 endpoints that had no written description, so the support team could answer without an engineer.
Halved the build from 22 minutes to 11 by splitting the test stages across 4 runners and caching dependencies.
Rewrote the payment callback handler after a retry storm and kept every one of 90 000 daily callbacks safe to repeat.

Education
BSc Computer Science · Universität Leipzig, Leipzig · 2012 to 2016

Skills
Go, Python, PostgreSQL, Kafka, Terraform, Kubernetes, gRPC, Docker, observability, incident response

Languages
German · native · English · C1 · Dutch · B1

Certifications
Certified Kubernetes Application Developer · Cloud Native Computing Foundation · 2022

Why the lines are built this way

Fifteen achievement lines, five under each of three dated roles, every one opening with a verb and every one carrying a figure. The figures are the part candidates skip and the part that does the work: "improved reconciliation" and "held end-of-day reconciliation inside 6 minutes on 400 000 daily transactions" describe the same afternoon, and only one of them can be argued about at an interview.

Every line is in the past tense, including the ones under the current job. That is a deliberate choice and it costs a point: our own writing check wants the present tense in a role that has not ended, while the action-verb check it sits beside is a list of 436 past-tense verbs. Both cannot pass, the past-tense half is the cheaper and the commoner one, and the page would rather say so than pretend the document scored something it did not. The summary is two sentences and names a domain, which is what a summary is for. There is no objective, no skills bar chart and no photograph, because none of those survive extraction as information.

Take the shape, leave the sentences

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.

The door below opens the builder with this example already in it, saved under its own name so nothing of yours is touched — useful for reading the structure from the inside, in the editor, in the design the picture above was drawn in. Then open the import, paste your own résumé over it, and correct what it read. Then compare your page against the shape above: three dated roles, five verb-first lines under each, a figure in every line, and a summary that names a domain rather than a temperament. The design gallery holds 37 layouts and the words do not change when the paper does, so the structure is the only part of this example worth borrowing.

Skills for a software engineer résumé, grouped

Ada's ten skills fall into three groups a hiring engineer recognises at a glance. Languages and data: Go, Python, PostgreSQL, Kafka. Platform: Terraform, Kubernetes, Docker, gRPC. Operations: observability and incident response. Printed as one run of ten, the reader has to sort them; printed as three short groups, the sorting is done and the stack reads as a stack.

In the free résumé builder the Skills section has a One list or In groups switch. Name the groups in your own words, move each skill with its arrow, and the paper prints a bold label before each group. Keep the list to what you would be happy to be interviewed on; the skills section guide covers trimming.

From junior to senior engineer, what changes on the page

A junior backend résumé proves that you ship: features merged, tests written, a service you kept alive. The Leitmotiv junior role here does exactly that in five lines. The senior role at Northwind Pay changes the unit of the line from the task to the system: latency, cost, incidents, the engineers who adopted your library.

The move to senior also changes what earns space at the top. Early on, a projects block or a degree can sit high. Once you have three dated roles, experience leads and the summary shrinks to two lines naming your domain. If you are moving into staff or lead work, add one line per role about a decision you owned and what it cost to reverse, because that is the question a panel will ask.

How it reads and scores

The ATS checker scored it 98 out of 100, re-measured on 25 September 2026, with readable volume 4 points short and achievement quality 2 points short: 100 × 30% for parseability, 100 × 30% for completeness and 94 × 40% for content. It scored 95 — 91 of the 96 points that applied here — and the five it did not award are the tense rule described above. The method behind these numbers is written up once, in how our examples are made and checked.

The Conxfolio import review showing the example résumé read into fields, headed Here's what we read, with the rendered page beside it — Ada Fennimore's software engineer résumé read into fields, each field beside the line it came from.

Write yours beside it

Opens the builder with Ada’s example loaded, saved as its own entry in the design above. Replace every line with your own. Free, no account.

Use this example Check a résumé instead

Questions

Is Ada Fennimore a real person: No. She is invented for this page, and so is Northwind Pay. Every number in her résumé was written to demonstrate a shape, and none of it describes anyone's career. We do not publish real people's documents.
What does “Use this example” do: It opens the résumé builder, reads this example through the same import an uploaded file goes through, and saves it as a NEW entry called “Example · Software engineer”. Anything already saved on your device is untouched and stays in your Workspace.
Can I copy this example: Copy the structure, not the sentences. Three dated roles, five achievement lines under each, every line opening with a verb and carrying a figure where a figure exists, is a shape that survives any parser. The claims have to be yours or the document is worthless.
What did the checker score it: 98 out of 100, re-measured on 25 September 2026, with readable volume 4 points short and achievement quality 2 points short. The arithmetic is 100 × 30% for parseability + 100 × 30% for completeness + 94 × 40% for content. The writing check scored it 95, which is 91 of the 96 points that applied to it.
What did the import review read: 3 roles, 1 degree, 3 languages and 10 skills, each shown beside the line it came from before anything reached the editor. The review lets you correct any field before you accept it.
Does the example work for a junior engineer: The shape does. Replace the roles with projects and coursework, keep the verb-first lines and the figures, and the same structure reads correctly. The builder keeps a projects section for exactly that.
Which design is the example rendered in: Classic, an ATS-safe layout. The picture at the top of this page is that document drawn by the builder’s own renderer, and the door below opens the builder on the same design. Any of the 37 designs renders the same content, and 24 of them are marked ATS-safe.

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.