There are two bad ways to handle a resume during a search. One is to send the same file to every posting and hope. The other is to rewrite it from scratch for each application, which burns an evening per job and ends with a folder of files named “final_v7_REAL”.
A workable middle exists. It has one master document, a small number of versions, and a short tailoring routine you can finish in 20 minutes.
The master resume
Start with a file you never send. It holds everything: every role, every project, every bullet you have ever been proud of, written in full. It can run to four pages. Nobody reads it. Its job is to be the place you pull from.
This file solves a real problem. Without it, each tailored version drops bullets you later wish you had, and you rewrite from memory. With it, tailoring is selecting and trimming, not writing.
Keep it somewhere you will find it, with a plain date in the file name. Update it the day something happens, such as a launch, a promotion or a number you finally found, while you still remember the details.
When to make a separate version
A version earns its own file when the roles you are applying to differ in what they would want to see first. Examples:
- You apply to both product management and project management roles, and they weight different experience.
- You apply to both individual contributor and team lead roles.
- You apply in two industries where the same skills carry different names.
A version does not earn its own file because one posting says “Python” and another says “Go”. That is a tailoring edit, not a new document.
A useful limit is three versions at most. Past that you are likely to lose track of which has the corrected dates, and a fix to your phone number has to be made in every file.
Name versions by the kind of role, not by company: resume-product-manager, not resume-acme. Then the file tells you what it is for.
The 20 minute routine
Open the version closest to the posting and work through these steps with a timer.
Minutes 0 to 5: read the posting for three things. What the role is called, the two or three responsibilities that come first in the list, and the tools or skills named more than once. Write them on a sticky note. That note is your target.
Minutes 5 to 10: rewrite the top third. The title line, the summary if you have one, and the first role’s first three bullets are what a reader sees before deciding whether to continue. Make the title line match how the posting names the role if it is honestly the same work. Make the summary two sentences that answer: what you do, and what you have done that is closest to this job.
What happens in the last ten minutes?
Minutes 10 to 15: reorder. Within each role, put the bullet that best matches the posting’s first responsibility on top. If a role further down has a relevant achievement, pull it up or add a line to the skills section. You are changing order, not inventing.
Minutes 15 to 18: adjust three to five lines. Where the posting’s word for a thing is the standard word for something you did, use it. If the posting says “stakeholder management” and your bullet says “kept the directors updated”, say the first, as long as it describes what you did. Do not paste in terms for work you have not done.
Minutes 18 to 20: check and save. Read the top third aloud. Check dates and numbers against the master. Save as a PDF with a name that includes the role and company.
If you have no master yet
Spend your first session building one, even if it takes an hour. Every later application gets faster because of it. Without a master, you are tailoring from a document that has already lost things.
What not to change
Some things should be identical across every version, because a mismatch is the kind of inconsistency a reader will notice:
- Employer names, job titles and dates.
- Education and credentials.
- Any figure. A number that is 40 in one version and 45 in another is a problem.
If a title was unofficial or differs from your HR record, decide once how to present it, and keep it the same everywhere.
Keeping track
A short list beats a clever system. For each application, note the date, the company, the role, and which file you sent. A spreadsheet with four columns does it. When a recruiter calls three weeks later and asks about something in your resume, you need to know which version they have in front of them.
In Zorlya, you can store several uploaded resumes under your profile, give each one a label, and compare two of them line by line in a diff view. That helps with the tracking problem, because the label says which is which and the diff shows what you changed between them. You choose which stored resume to activate for Zorlya to read.
Using the tailoring tool without losing your voice
Zorlya also has a resume tailor. For a job you choose, it takes the parts of your resume closest in meaning to the posting and writes five bullets that say your work in the posting’s words. It is instructed to invent nothing and to keep any number that is already in your resume.
Treat the output as suggestions. The check you should do is the same one you do for yourself: does each bullet describe something you did, and could you talk about it for two minutes in an interview? Each plan has a monthly tailoring allowance, listed on the pricing page. The routine above needs no tool at all, so the limit is not what makes it work.
Check that it still sounds like you
Before sending, ask whether the version you made could be handed to a friend who knows your history, and whether they would say “yes, that is you”. If so, you tailored. If they would say “that sounds like someone else”, you stretched, and the interview will show it.