distil.work

How Rewrite Works

Rewrite does not start from scratch — it finds the weak lines and fills in the missing evidence.

What does Distil do?

Distil does not rewrite your CV from scratch.

It picks only the lines Audit flagged as weak. It asks for the missing evidence, then rewrites them.

Your experience does not change. Only the expression gets sharper.

Strong lines stay untouched

Distil's first rule is "do not touch."

Lines that already have metrics, results, and a clean structure stay as they are. Over-rewriting a good line makes it worse.

Distil works only on the lines that need work. Not your whole CV — just the few that move the needle.

Nothing gets fabricated

Distil never invents numbers or results.

It uses only what you provided — either in the original CV, or in your answers to follow-up questions.

When evidence is missing, Distil does not fill it in. It asks you.

Three steps

  • Select weak lines Picks bullets that lack evidence from the Audit result. Strong bullets stay untouched.
  • Follow-up questions Asks only for what is missing. Never asks you to rewrite everything.
  • Rewrite Builds your answer into the line. Picks the right structure for the role.

Missing evidence comes in many forms

"Missing evidence" is not one thing. Different lines need different kinds.

The common ones:

  • Metrics: How much? What percentage? How many?
  • Before/after: What changed from before to after?
  • Scale: Team size? User count? Budget?
  • Ownership: What did you personally lead?
  • Reasoning: Why this direction and not another?
  • Method: What tools, experiments, or approach did you use?

Each line needs something different. Distil asks for what that specific line is missing first.

What Distil asks

To fill the gaps in weak lines, Distil asks things like:

  • How much time did the automation save, specifically?
  • What did you directly own — planning only, or execution too?
  • What was the team size and project duration?

You do not have to know every answer. Lines still get rewritten without them. Answers just make the result sharper.

Role-aware rewriting

A strong PM bullet and a strong designer bullet do not look the same.

Distil picks the structure that fits each bullet. It might lead with a result, or open with a problem, or show a challenge → action → result chain. Different structures for different stories.

The vocabulary changes by role too:

  • PM: Thinking verbs — diagnosed, concluded, prioritized, validated
  • Designer: Insight, hypothesis, validation — the design reasoning chain
  • Engineer: Technical decisions linked to user or business impact

Summary and Skills get the same treatment

Distil does not stop at bullets. It also rewrites your Summary and Skills sections.

The summary gets rebuilt around a concrete problem you solved — not "experienced professional seeking..."

Skills get grouped as "Competency: Evidence" instead of a flat list. Not "SQL, Python" but "Data-driven decision making: SQL/Hadoop analysis of 5M users → quantified competitive churn."

Before → After

After the answers came in, Distil rewrote each line.

Before

Responsible for product planning and operations

After

Diagnosed a 20% M+1 retention ceiling through 23-month cohort analysis and designed a preemptive conversion strategy that lifted conversion by 148%

Before

Handled customer enquiries and CS operations

After

Handled an average of 45 customer enquiries per week, identified 3 recurring issue patterns, and introduced FAQ automation — reducing enquiry volume by 28%

Before

Team leadership experience

After

Led a 5-person squad through a 6-month product launch, improving NPS from 32 to 58 and reducing time-to-market by 3 weeks

Final output

The completed experience section after Distil. Missing evidence is filled in and the language matches the role.

Company A — Product Manager (Mar 2023 – Feb 2025)

Diagnosed a 20% M+1 retention ceiling through 23-month cohort analysis and designed a preemptive conversion strategy that lifted conversion by 148%.

Led a 5-person squad through a 6-month product launch, improving NPS from 32 to 58 and reducing time-to-market by 3 weeks.

Handled an average of 45 customer enquiries per week, identified 3 recurring issue patterns, and introduced FAQ automation — reducing enquiry volume by 28%.

Why we built it this way

Most AI CV tools offer to rewrite everything for you.

The problem: those rewrites look polished but feel hollow. No real numbers. Language that drifts from what you actually did.

Distil avoids that trap. It keeps the lines that have evidence. It asks you about the ones that do not. It only writes with what you gave it.

Slower. But real.