Tailoring every application from scratch is the advice candidates hear. It's also unsustainable past about 15 applications, which is well below the volume most job searches require. So candidates do one of two things: stop tailoring (and lose the conversion benefit), or burn out trying to tailor everything (and stop applying altogether).

There's a middle path: build one master resume, project it into a small number of variants, and tailor only at the top of the closest-fitting variant per application. This post is the workflow.

Why a single resume can't carry the load

The problem with one resume is that the roles you're applying to aren't actually one role. A senior individual contributor and a people-manager posting want different things. A platform-engineering JD and a customer-facing-product-engineering JD want different things. A standard "well-written resume" reads as a compromise to both audiences because it can't emphasize the angle each one cares about.

The problem with per-application tailoring is the math. At 30-60 minutes per application of real tailoring work, a serious job search becomes a part-time job in itself, and quality drops as fatigue accumulates.

The master-plus-variants system splits the work. Most of the thinking happens once (which archetypes you're targeting, what to emphasize for each). Per-application work shrinks to summary tuning and bullet-order tweaks.

Build the system once

The five-step setup takes a long evening. After that, every application benefits.

Step one is the master resume. Write every role, every project, every accomplishment in full. Don't constrain to one page — this document never gets sent. Length is helpful here because you want the complete inventory to draw from. Quality of writing matters more than length: every bullet should be strong because variants will inherit them.

Step two is identifying your archetypes. Look at the postings you'd actually apply to. Most candidates discover they have two to four real archetypes — "senior backend IC" and "tech lead manager", for instance, or "B2B growth PM" and "consumer growth PM". More than four is usually a sign you're applying too broadly; fewer than two is rare.

Step three is the variants. Each one is a 1-2 page resume optimized for one archetype. Same underlying content, different selections, different emphasis, different summary. The technical-skills order changes; the bullets foregrounded per role change; the framing of your most recent role changes. About 60% of the content overlaps; 40% diverges.

Step four is the per-application work — and it's small. Pick the closest variant, tailor the summary and the first bullet or two of each recent role to the posting, verify your skills section reflects the posting's vocabulary where you have the work, and submit. See tailor-resume-to-job-description for the in-the-moment tailoring playbook.

Step five is keeping the master current. A new project lands, a new accomplishment surfaces — add to the master first, propagate to variants as relevant. The master is the source of truth.

What the system saves you

The time per application drops sharply when the variant is well-matched. A from-scratch tailoring effort runs 60-90 minutes for thoughtful work. Starting from a generic resume runs around an hour. With master plus variants, a well-matched variant cuts that to ~8 minutes — mostly summary tuning and a glance at the top bullets.

The savings compound. At 30 applications over a 6-week search, the difference is more than 30 hours of work. That's time available for company research, network outreach, interview prep, or just sleep.

The trap to avoid: don't try to skip tailoring entirely. The master-plus-variant system makes light tailoring fast, not unnecessary. Per keyword-stuffing-vs-keyword-fit, the summary and the skills section are the highest-leverage places to reflect a specific posting's vocabulary, and both are 2-minute edits per application.

What actually changes between variants

A useful way to see what a variant is: take two of yours and run them side by side. The matched column — content that appears on both — is your stable identity, the keywords and credentials that don't change with the role. The missing column — content unique to one variant — is the angle.

A senior-IC variant and a people-manager variant might share Python, AWS, system design, incident response, and total years of experience. They diverge on management language: "managed 6 engineers", "hired 3 senior engineers", "ran quarterly performance reviews", "owned the roadmap". That divergence is the whole point. Sending the IC variant to a manager role costs you the angle; sending the manager variant to a deep-IC role costs you the depth.

What this isn't

A few clarifications:

• It's not a substitute for per-application keyword work. The variant gets you 80% of the alignment; the remaining 20% is the per-posting summary and skills-section tuning. Both matter.
• It's not a reason to have 12 variants. Two to four covers almost every real job search. More than five is a sign you're not actually targeting; you're scattering.
• It's not write-once. Update the master quarterly — sooner if your role changes significantly. Variants drift out of date fast.

The short version: build the system once and the per-application work becomes a tractable 5-10 minute task, not a 60-minute one. That's the difference between sustaining a serious search and giving up on tailoring halfway through.