A resume for a career change, without pretending

The two questions a reader has

Someone reading a career changer's resume has two questions, and a resume that answers only one of them fails: why is this person applying for this job, and can they do it? The first is answered in one line at the top. The second is answered by everything else, and most of the work is there.

Say the move in the first line

Without a summary, a reader sees eight years of teaching on an application for instructional design and has to guess why. Guessing is where applications stop. One line settles it: what you have been, what you are moving into, and the strongest evidence that the move is real.

• •“Secondary-school mathematics teacher of eight years moving into instructional design, with four e-learning courses built in Articulate Storyline for the district's online programme.”
• •“Retail store manager of six years moving into HR, SHRM-CP certified in 2026, with the hiring and onboarding for a 26-person store behind it.”
• •“Mechanical engineer moving into data analysis; built the plant's downtime dashboard in Python and Power BI, now used in the weekly operations review.”

Find the overlap in what you already did

Most careers share more with the next one than their titles suggest. The work is to find the parts of the old job that are the new job's work, and to write those bullets in terms the new field would recognise — wherever the term is honest.

• •A teacher designed a 12-week curriculum, assessed 150 students against it and revised it from the results. That is instructional design, and it should read like it.
• •A store manager hired, trained and scheduled 26 people and cut first-year turnover. That is recruitment and retention, measured.
• •An engineer who automated a reporting spreadsheet wrote a data pipeline, whatever it was called at the time.

Keep your real job titles. Retitling “Teacher” as “Learning Experience Designer” is the line a reference or a background check contradicts, and the bullets underneath can make the argument without it.

Build the evidence that is missing

If nothing in your history shows the core skill of the new job, no wording will create it. It has to be built, and it can be: a project, a course with an output, volunteer work, a freelance engagement. Put that section above Experience while it is the strongest evidence you have for this job — the builder lets you reorder sections freely — and move it back down once the new job exists.

• •Projects that did something real outweigh certificates on their own. A dashboard the plant uses is evidence; a completion badge is a claim.
• •Name the new field's tools in the bullet where you used them.
• •Link the portfolio, repository or published work. For a career changer it is often the most persuasive thing on the page.

Chronological, not functional

The usual advice to career changers is a skills-first, or functional, resume that groups abilities and pushes the job history to the bottom. It reads as hiding something, and parsers need dated roles to build a work history at all. A chronological resume with a clear summary and a projects section above it does the same job honestly.

Cut what does not travel: the old field's jargon, its internal awards, the tools nobody in the new field uses. Older roles can shrink to a line each. The page should read as the history of someone heading somewhere.

Paste a posting from the new field into the builder's Match tab. What it lists as missing is not a set of words to add — it is the evidence to build next.

Keep reading