Career change resume: pivot without inventing experience

Summary opens with the role you want and two proofs from what you already did — even if the industry differed. Example: moving support to UX: cite research calls, workflow fixes, and tools used, not a fake design job.

Do not rename old titles to match the new field. Recruiters verify employment. Instead explain transfer in bullets: “Documented user pain points from 200+ tickets weekly” supports UX more than retitling yourself “Product Designer.”

Verum keeps your employer names and dates intact; AI rewrites bullets to emphasize honest overlap with the posting.

Split skills into groups if helpful: “Customer operations” and “Technical” rather than one undifferentiated list. Put tools you used in any role that the new job needs.

Courses and certificates belong in their own section when completed — not mixed into employment.

Remove skills from the old industry that confuse the pivot unless the posting asks for them.

Side projects count when labeled clearly: personal repo, freelance client with permission, bootcamp capstone. Include stack, outcome, and link if public.

Volunteer roles follow the same company / role / date pattern as paid jobs when substantial.

Never list a project as a full-time employer.

Name the pivot in sentence one: “I am moving from X to Y because…” Give one paragraph of evidence, one paragraph of learning you have already done (course, portfolio piece), close with availability.

Address the obvious question — why leave the old field — in one factual sentence, not a memoir.

You will miss some domain keywords. Apply when you meet most hard requirements or have strong adjacent proof. Use the keyword tool to see gaps before you spend an hour customizing.

Network referrals matter more in pivots; the resume still must survive HR screening software.

Pivots benefit from visible learning: certificate lines, portfolio links, and volunteer projects that use the target stack. These belong in dedicated sections with dates — not embedded as fake employment.

Informational interviews do not belong on the resume, but outcomes do: “Pro bono site rebuild for nonprofit X using React” after consent from the org.

Referrals often bypass strict keyword filters; your resume still must be coherent when forwarded to hiring managers.

HR forms ask years of experience in the new field — answer truthfully and use the cover letter for context. Misrepresenting years fails background checks.

Salary expectations for pivots may be lower than your previous peak; that is a negotiation topic, not a resume fabrication.

If you took a pay cut to retrain, employment dates and titles still reflect what happened; gaps filled by study can say “Full-time certificate program, Provider, dates.”

Teacher to instructional design: cite curriculum built, LMS tools, and measurable learner outcomes from classroom data — not a renamed “Designer” title.

Retail manager to operations: inventory systems, scheduling, shrink metrics, and vendor coordination translate directly when named.

Journalist to content marketing: publication volume, SEO experiments you ran with real traffic numbers, and CMS tools used in newsroom workflows.

Overlapping full-time work and full-time study happens — show both with accurate dates rather than hiding one. Recruiters prefer overlap explained to gaps unexplained.

If you left the prior field for health or family reasons, one neutral sentence in the cover letter suffices; the resume stays factual on dates.

Use version diff before sending pivot applications so you do not accidentally restore old-industry bullets from a previous master file.

Target hybrid titles on job boards (e.g., customer success engineer) when your proof spans two domains — still apply only when requirements match honestly.

A pivot portfolio needs two or three pieces that use the target stack or domain vocabulary. Label each with date, role (personal project is fine), and outcome.

Bootcamp certificates alone rarely replace experience bullets — pair them with shipped work or client outcomes, even pro bono.

In interviews, walk from old field to new using one narrative thread; the resume should preview that thread in the summary.