A rewrite should make your real experience easier to understand. It should not manufacture a parallel career.
That sounds obvious until you are staring at a job description full of tools you touched once, metrics you never measured, and verbs that feel more impressive than your day-to-day. The temptation is to “optimise”. The cost is an interview you cannot survive.
What “truthful rewrite” means
Allowed:
- Rephrasing for clarity and British English.
- Reordering bullets so the strongest evidence for this role comes first.
- Choosing which real projects to emphasise.
- Framing impact with numbers you actually have (or ranges you can defend).
- Cutting fluff, jargon, and unsupported adjectives.
Not allowed:
- Employers, titles, dates, or qualifications you did not hold.
- Tools and methodologies you cannot discuss in depth.
- Metrics invented because the JD likes percentages.
- Softening failure into fake leadership.
If a line cannot survive “Tell me more about that,” it does not belong on the CV.
Start from evidence, not from the JD
Work backwards from artefacts you trust: appraisals, emails, dashboards, shift plans, P&L extracts, before/after photos of processes you owned. Write rough bullets in your own voice first. Then look at the JD.
That order matters. Starting from the JD trains you to fill gaps with fiction. Starting from evidence trains you to map truth onto the role.
Matching language without lying
Job descriptions reuse stock phrases. Mirroring a few — when they accurately describe work you did — helps humans and parsers. Mirroring phrases for work you did not do is fabrication with better grammar.
A practical filter:
- Does this phrase describe something I did weekly or owned end-to-end?
- Could I give a concrete example in under two minutes?
- Would a former manager nod if they read it?
If any answer is no, drop or rewrite until all three are yes.
Voice over evasion
Some tools sell “humanise so detectors won’t catch you.” That is the wrong problem. Hiring managers care whether you sound like someone who did the job — not whether a classifier scored you as organic prose.
Keep your cadence. Keep the words you actually use. Shorten sentences if you ramble; do not replace your voice with generic corporate mush. If you write samples into a voice profile, use them as a style guide, never as a licence to invent facts.
Guardrails are a feature
When software rewrites a CV, it should refuse unverifiable claims — or strip them and tell you. Silent invention is worse than a blunt “we can’t support that line.”
Use that discomfort. If the tool removes a metric, ask yourself where the real number lives. Add it only when you can source it. Otherwise leave the achievement qualitative and true.
A simple rewrite workflow
- Extract the current CV to plain text so you see the same stream a parser sees.
- List 8–12 real achievements with evidence notes (private — not for the CV yet).
- Map each JD must-have to at most one evidence item. Gaps stay gaps; do not invent fillers.
- Rewrite bullets for clarity; keep names and dates intact.
- Diff against the original. Every new claim needs a source.
- Export ATS-safe for portals; keep designed versions optional and labelled.