Keep one master resume containing everything you've ever done, one base version for each distinct role type you're pursuing — usually one to three — and produce a lightly tailored copy per application from the matching base. What you shouldn't have is twenty divergent files with no source of truth, or a single generic resume sent everywhere unchanged.
The master resume is a private document no employer ever sees, and it has no length limit: every job, every project, every quantified win, every certification, in full detail. Its job is to make sure you never rewrite the same bullet from memory twice, and never forget the strong-but-niche achievement that suddenly becomes relevant.
Maintain it the way engineers maintain a changelog — add accomplishments as they happen, with the numbers, while you still remember them. Six months later, "improved the deployment process" is all you'll recall; today you know it cut release time from two days to three hours. The master resume is where that number survives.
If you're applying to genuinely different kinds of roles — say, data analyst and analytics engineer, or product manager and program manager — each needs its own base version, because the emphasis, keywords, and even which jobs get the most space differ structurally. Build each base once, carefully, from the master.
Most people need one to three bases. If you think you need five, you're usually either casting too wide a net for an effective search, or treating minor variations as separate role types when a tailoring pass would cover them. Every base you add is a document you must keep updated, so add them reluctantly.
Each application gets a copy of the relevant base with a 15–30 minute pass: mirror the job description's exact keyword phrasing, rewrite the summary line for this role, reorder or swap bullets so the most relevant evidence leads. You're adjusting emphasis, not rewriting history — the heavy lifting happened when you built the base.
Name files so you can find them later — company, role, date — and keep them. When the recruiter calls three weeks after you applied, you want to be reading from the exact version they're holding, not guessing which variant they saw.
A base version is built once per role type and maintained; it carries the right emphasis and keywords for that career direction. A tailored copy is disposable — a base plus fifteen to thirty minutes of per-application adjustment to mirror one specific job description.
Yes, because 'updated' resumes are trimmed for length, and trimming destroys detail permanently. The master is the untrimmed archive — every role, project, and number — so future tailoring pulls from a complete record instead of from memory.
Keep them, clearly named with company and date. Interviews often happen weeks after applying, and the interviewer is reading the version you sent — not your current draft. You want to prepare from exactly the document in their hands.
Score each base version free against a representative job description — a weak base multiplies its weaknesses into every application built from it.
