Skip to main content

Resume AI rewrite + version history

Click AI Rewrite on any section, get a side-by-side diff, accept / edit / reject. Every accept creates a new version you can restore.

Resume AI4 min read

Resume AI rewrite + version history

Open a resume in Resume AI and you'll see an AI Rewrite button on each section (Summary, Experience, Education, Skills, Projects). Click it on any section → the AI suggests a tightened version of that section grounded in your actual content. Accept it, edit further, or reject it. Original is always preserved.

What the AI rewrite does per section

SectionWhat the AI does
SummaryTightens to 2-3 sentences, leads with role + biggest signal, drops filler
ExperienceRewrites bullets to action-verb-first + quantified-result structure (STAR-ish but for bullets). Detects vague phrasing and pushes for specifics.
EducationAdds relevant coursework / honors if missing; trims dates if redundant
SkillsReorganizes into logical groups (Languages / Frameworks / Tools / Cloud); deduplicates synonyms
ProjectsRewrites titles + bullets to interview-pitchable shape (problem + your solution + outcome)

The rewrite is grounded in your actual content — the AI doesn't invent skills you don't have, employers you didn't work for, or numbers you didn't provide. If it lacks data for a bullet, it leaves placeholders like [QUANTIFY: # users / $ savings / % improvement] for you to fill.

Accept / edit / reject flow

  1. Click AI Rewrite on a section → loading spinner ~2-5 sec
  2. The rewritten version appears next to the original in a side-by-side diff
  3. Three buttons:
    • Accept → original is archived to version history, rewrite becomes current
    • Edit → opens the rewrite in the editor; you tweak before accepting
    • Reject → rewrite is discarded; original stays untouched

Version history

Every accept creates a new version. View past versions on /resumes/[id]?tab=history:

  • Timeline of every accepted change with timestamp + which sections changed
  • Restore button on any past version → bring it back as the current
  • Compare two versions side-by-side to see what changed

History is per-resume, not per-account. If you have 3 resumes, each has its own version history. Free tier: 5 versions retained per resume. Pro: 20. Pro+/Lifetime: unlimited.

How to use it well

  • First pass — Click AI Rewrite on EVERY section. Get a baseline rewrite, see what changes the AI proposes. Don't accept blindly — review.
  • Second pass — Manually edit the rewrites with your specific numbers. AI placeholders → real metrics.
  • Re-score after each accept. Watch the score change on Score Panel.
  • Iterate on weak sections. If Content Quality stays at -10, that's the section to keep rewriting until the score moves.

What the AI can't do

  • Invent achievements — won't say "managed team of 50" if your bullets never mention team size
  • Lie about employers — won't add Google/Meta to your experience if you didn't work there
  • Optimize for a specific company — the rewrite is generic-best-resume, not "tailored for Stripe." For company-specific tailoring, edit manually OR use the Custom Prompt feature inside a live session and let the AI pivot answers per company at interview time, not resume-edit time.
  • Translate languages — write your resume in English; the AI rewrites English content only

Gotchas

  • AI uses Claude Haiku 4.5 (free tier) or Sonnet 4.6 (Pro+) for rewrites. Different models produce different rewrites. Pro+ rewrites tend to be more precise; Free tier rewrites are faster but more generic.
  • No undo button on the editor itself. Once you click Accept + then edit further + then accept again, the in-between state is the new version. To go back, use Version History → Restore.
  • Rewrites use ~500-1500 tokens per section. Counts against your daily AI quota: Resume Builder AI per day = 10 (Free), unlimited (Pro+).

Where it lives in code

apps/web/app/resumes/[id]/_components/ — the editor + AI Rewrite button. Backend: apps/api/domains/resume_builder/ — handles section rewrites + version persistence. Version history table: resume_versions in Postgres.

Still stuck?

Help & Feedback → Contact us with category "Something is broken" + which section + what the rewrite did vs what you expected.

Video walkthrough

Coming soon.

Still stuck?

Sign in and message the founder directly from the Help & Feedback tab. Every reply comes from a real person, usually within a few hours.

Contact us