Before-and-after rewrites: manager and career switcher, and what all five share

The last two cases are the paths where the reader's first conclusion is most likely to be wrong: a manager who reads as an individual contributor, and a career switcher who reads as someone from another field. As before, form your own view of each "before" before you read the diagnosis.

The lesson then steps back from the individual cases. Five people at five stages turn out to need nearly the same handful of edits, and that list becomes the checklist you run on your own draft.

Case study: engineering manager

A capable manager whose resume reads like a senior individual contributor's.

Before

SARA LINDQVISTStockholm · sara.lindqvist@email.comEXPERIENCESenior Engineering Manager, Northwind Retail, February 2023 – Present• Managed the payments team• Oversaw the payments platform rebuild• Conducted 1:1s and performance reviews• Involved in hiring and interviewing candidates• Ran sprint planning and retrospectives• Contributed to the technical design of the settlement serviceEngineering Manager, Northwind Retail, March 2020 – January 2023• Managed the checkout team• Delivered the checkout redesign project• Improved the on-call process• Worked with product on the roadmap

What is wrong

This describes the activities of a management job — one-to-ones, sprint planning, retrospectives, hiring. All real, all expected, none evidence of doing it well.

There are also no numbers of any kind: not team size, not headcount growth, not delivery outcomes, not retention.

After

The rewritten version is the manager template. The changes:

A summary added, because span of control cannot be inferred from "Senior Engineering Manager" — that title covers anything from six people to sixty.

Team size in every context line. "3 teams, 21 engineers, 2 tech leads reporting in."

Delivery and people outcomes fused in single bullets. "Led the payments platform rebuild across 3 teams, cutting transaction failure rate from 2.1% to 0.3% and unblocking expansion into 4 new markets." Both arguments, one sentence.

Hiring quantified. "Grew the org from 12 to 21 over 18 months; hired 11, promoted 4 to senior and 1 to tech lead."

Retention included. "Team attrition of 5% over two years against a company average of 19%." Sara had this number and had not thought to use it.

Process work given an outcome. "Introduced a written design-review process; production incidents attributable to design gaps fell from 14 to 3 per year." The ceremony became a result.

Technical credibility retained. "Still active in design review" in the summary, plus the backend stack under skills.

Case study: career switcher

Real engineering experience, but a resume that lets the reader draw the wrong conclusion in the first three seconds.

Before

MAYA FERREIRALisbon · maya.ferreira@email.comEXPERIENCESenior Clinical Research Coordinator, Lisbon University Hospital,2019 – 2024• Coordinated multiple oncology clinical trials• Managed data quality and regulatory submissions• Trained and supervised junior coordinators• Built Python scripts for monthly reportingClinical Research Coordinator, Lisbon University Hospital, 2016 – 2019• Supported trial operations and patient scheduling• Maintained trial documentationData Engineer, Meridian Labs, January 2025 – Present• Work on data pipelines• Built validation for incoming data• Improved pipeline performanceEDUCATIONBSc Biomedical Sciences, University of Lisbon, 2016Data Engineering Zoomcamp, 2024

What is wrong

The first thing on this page is Senior Clinical Research Coordinator. A recruiter hiring a data engineer reads that, forms a conclusion, and may never reach the engineering role — which is listed third, out of chronological order, and described in nine words.

After

The rewritten version is the career-switcher template. The changes:

A summary added, doing three jobs in three lines. What Maya does now, the evidence, and the prior career reframed: "Previously eight years as a clinical research coordinator — I know what this data means and why it arrives dirty." That last clause is the hiring argument.

Order fixed. The data engineering role first, with a full context line and three outcome-first bullets.

The engineering role described properly. "Work on data pipelines" became three bullets with numbers — validation cutting data-quality tickets from ~25 to 4 a month, runtime from 5h 40m to 55m, and a schema template used for twelve new sites.

Prior career moved under "Earlier career" and compressed, signalling a deliberate transition rather than a gap.

The bridge bullet kept and labelled. The Python reporting scripts that cut monthly reporting from three days to two hours, with a note that this is what led to the move. It makes the transition a coherent story rather than an abrupt change.

Domain expertise listed under skills, given equal billing with the tools.

Open-source project added, providing independent evidence of engineering ability.

What changed across all five

The five rewrites are different people at different stages. The edits are largely the same five moves.

The recurring edits, by frequency

Two more appeared twice each: adding a summary where one was genuinely warranted, and fixing section order.

The observation worth taking away

Your personal edit checklist

Build your own from what you found in these five. The generic version:

Run this against your own draft now, before Section 14 (Advice for Hiring Managers on Screening). It will take twenty minutes and it is the last structural pass this course asks of you.