Resume versions let you keep a single career profile and produce multiple tailored resumes from it. This is the heart of the "build once, tailor many" workflow.
What a version is
A version is a variant of a base resume. Every resume has a base (created in the wizard) plus any number of versions. Versions store only what differs — the template, section order, hidden sections, layout (summary-part visibility and section columns), a tailored summary, and notes — never a full copy of the resume.
The Versions panel
Open the Versions panel from the builder header (or the mobile menu). The panel shows:
- A list of versions — switch between them with one click; rename, duplicate, or delete from the inline actions.
- Template — each version can use its own template.
- Sections — reorder sections and show/hide them for this version.
- Tailoring — a friendly Professional Summary + job title per version, with Use base content to reset back to the base version.
- Notes — reminders for why you created this version (e.g. "apply by Friday").
All changes apply instantly to the live preview. Layout (which summary parts show, and section columns) is edited from the Layout card in Review & Export, but is saved and applied per version like the other settings.
How tailoring works
Instead of raw JSON patches, tailoring gives you plain-language fields:
- Pick a version.
- Edit the Professional Summary (and optional job title) to match the target role.
- Reorder or hide sections that aren't relevant to that application.
- Export that version when you're ready.
Sections that differ from the base show a Tailored for this version indicator in the wizard. Use Use base content to revert a single section.
Creating versions
From the Versions panel, click Create. The new version starts as a copy of the current layout — then you adjust it. Versions you've used for a specific job application are counted in the panel so you can see which resume each application used.
Tips
- Keep the base resume as your "master" profile and do all role-specific tweaking in versions.
- Name versions by role or company (e.g. "Product Manager — Acme") to stay organized.
- Apply a version's overrides when exporting — see Export guide.