Resumes for managers, career switchers and returners

Three paths do not follow the ladder in the previous lesson. An engineering manager is judged on a different job. A career switcher has a history that points somewhere else. A returner has a hole in the timeline. In each case the reader, left alone, will draw the wrong conclusion.

So all three resumes share one move: they answer the reader's question before it is asked. That is why a summary, which most engineers should skip, is often justified on all three of these paths.

Engineering manager

Your resume must carry two arguments at once, and the balance between them is the whole problem.

The two arguments

1. You deliver through a team. Shipping, planning, execution.
2. You develop people. Hiring, growth, retention.

And a third thing, held in reserve: you have retained enough technical credibility to lead engineers. Enough that they respect you. Not so much that you read as an IC.

The two failure modes

Reads as a senior IC. Every bullet is about systems you built. A hiring manager for an EM role concludes you have not really moved into management.

Reads as a non-technical manager. Every bullet is about process, ceremonies, and headcount. Engineers conclude you cannot evaluate their work.

The fix for both is the same: attach the team outcome to the technical outcome.

Managed a team of eight engineers.

Rebuilt the payments platform.

Led an 8-engineer payments team through a platform rebuild that cut transaction failures from 2.1% to 0.3%; grew the team from 5 to 8 and promoted two engineers to senior during the same period.

One sentence, both arguments, and it is clearly a manager writing it.

What to include

The structure

ContactSummary            ← often justified: state span of control and domainExperience         ← management roles first; earlier IC roles compressedSkills             ← short; leadership scope, plus enough technical to stay credibleEducation

A summary is more often justified for managers than for ICs, because span of control is not inferable from a title. "Engineering Manager" could mean four people or forty.

Retention is your strongest number

Most managers do not think to include it, and it is the most differentiating figure you have:

• Team attrition of 4% over two years against a company average of 18%.

If you have that number, use it. Very few competing resumes will.

Career switcher

A career switcher is asking a reader to make an inference they would not make on their own, so the resume must make it for them.

The core task

Your history does not point at the job you want. Left alone, a reader will read it chronologically, conclude you are a marketer or a teacher or a physicist, and stop.

Your resume has to reframe before they read.

The structure

This is the one profile where a summary is close to mandatory (see Summary or objective: when to include one).

ContactSummary            ← 3 lines: what you do now, the evidence, the prior career as an assetRelevant projects  ← or relevant experience, if you have anyExperience         ← prior career, compressed, keeping what transfersEducation / TrainingSkills

Writing the summary

Three moves, in order: what you do now, the proof, and the prior career reframed as an advantage.

Data engineer building pipelines in Python and dbt. Built and operate the ingestion pipeline for Meridian Labs' clinical trial data (~2M rows/day) since 2025. Previously eight years as a clinical research coordinator — I know what this data means and why it is dirty.

That last clause is the whole argument. The prior career is not a gap in the story; it is the reason to hire this person over a generic data engineer.

Translating prior experience

Do not delete your old career. Translate it.

The rule: keep what a hiring manager for this role would care about. Cut the rest to titles and dates.

Target roles where the switch is an advantage

The single most effective tactic available to a career switcher: apply where your prior domain is the product. A former nurse applying to a healthcare technology company is not a risky hire — they are a rare one.

Returning after a break

A career break of one to five years is common and manageable. Most of the difficulty is in presentation and confidence rather than in the facts.

Put the break in the timeline

Do not leave a hole. Make it an entry:

Career break — Mar 2023 to Aug 2025Full-time caregiving. Completed AWS Solutions Architect Associate (2024) andcontributed 6 merged PRs to the Polars project (2025).

This does three things at once: it removes the unexplained gap, it states the reason without apology, and it shows you did not stop being an engineer.

Show current relevance

The reader's genuine question is whether your skills are current. Answer it with evidence:

• Anything recent and verifiable — a contribution, a project, a certification, a course with a real output.
• Date your evidence. "Contributed to X in 2026" answers the question; "familiar with X" does not.
• A small, recent, deployed project is the strongest single answer available. It proves currency more convincingly than any certificate.

Structure

ContactSummary            ← 2–3 lines: what you did before, the break, what you have done recentlyExperience         ← including the break as an entry, in sequenceRecent projects    ← if the break was longSkills             ← weighted to what you have used recentlyEducation

Do not over-explain

You owe a fact, not a narrative. Two words of reason are enough, and you are never obliged to disclose a medical reason.

After a difficult period dealing with family illness, I have been out of the industry and am now hoping to find my way back into a role where I can rebuild my confidence.

Career break, 2023–2025 (family care). Returning to backend engineering; shipped two Rust services for a local nonprofit in 2026.

The second is the same situation, stated as a professional fact.

On length of break

The longer the break, the more weight moves to recent evidence. Under a year, the break is barely worth remarking on. Over three years, your recent project section may matter more than your last job.