8 min read
Same person, three job titles on the board this week. That's normal after a layoff, a pivot, or a hybrid skill set that fits more than one lane.
The mistake isn't ambition. It's shipping one generic PDF and hoping each recruiter reads between the lines. Check your resume for free on the version you're about to upload so the headline field and first experience block still parse as separate lines.
You're not rewriting your past. You're choosing which true bullets lead for each req. Below are the decisions I see candidates skip, plus a tracker line you can paste tonight.
Quick wins
- Save a master DOCX, then duplicate per role family before you touch wording.
- Mirror the posting title in the headline when your duties already match.
- Log which PDF went to which req so you don't cross-wire versions later.
What to do when you apply to different roles with one background
Think in two layers. The master resume holds every employer, date, and bullet you've ever used in an application. Role versions are duplicates where only the headline, summary line, skills order, and top bullets change.
The headline is the routing label. In Workday and Greenhouse, parsers often map that field to current job title or target role. If you lead with "Marketing Generalist" but apply to a product marketing req, the sort treats you as a weak title match even when your bullets mention launches.
The first bullet is the proof line. Recruiters skim the top of your current job before they scroll. Put the outcome that matches this posting in the first eight words: channel mix for growth roles, ticket volume for support leadership, forecast accuracy for ops.
Before: One PDF titled Resume_Final.pdf goes to every portal.
After: Resume_Ops_Manager_Acme.pdf and Resume_Program_Lead_Acme.pdf share dates but swap headline and bullet one.
Pair this with resume tips for switching industries when you want a longer tailoring checklist. Tonight, version naming and headline swaps beat another hour on fonts.
Decisions to make for each posting
Which role family is this req?
Tag the posting as ops, product, people, revenue, or technical support before you open Word. If it doesn't fit your saved families, duplicate the closest version and rename the file. Don't edit the master in place.
Does your headline match their title string?
Copy the title from the posting into your headline when you're within one level of seniority. Use a pipe for a second token only when space allows: Senior Operations Manager | SaaS renewals and vendor SLAs.
Which three bullets move to the top?
Under your current employer, drag the bullets that mention their must-have tools or outcomes. Leave older roles alone unless the posting cares about a past title.
Illustration only, not a claim about hiring odds: Built weekly churn dashboards in Looker, cutting reactive tickets 11% in Q3 sits above vendor RFP work when the req mentions customer retention.
Are you staying inside one ATS employer?
Applying to two titles at the same company in the same week can overwrite parser data if both reqs sit on one profile. Space applies by a few days when you can, and upload the version that matches each req title.
Copy-paste into your tracker:
Req: [Title] @ [Company]
Role family: ops / product / revenue / other
Headline used: [paste]
File uploaded: Firstname-Lastname-[RoleToken]-[Company].pdf
First bullet theme: [one phrase]
Follow-up date:
I've screened Greenhouse queues where the candidate's background fit two lanes, but the headline still said coordinator while the posting asked for manager. The bullets were strong; the sort never surfaced them.
Before: You rewrite the entire experience section for every apply.
After: You change headline, summary, skills order, and three bullets, then export a new PDF name.
When you're choosing between adjacent titles, read resume framing for career switchers for summary lines that bridge without apologizing for your path.
Where one background breaks
- Sending the same headline to ops and product reqs because both feel "close enough."
- Stuffing every keyword from three postings into one skills block.
- Renaming the file but leaving the old headline inside the PDF.
- Deleting older jobs to make room instead of reordering bullets.
- Applying to senior and junior versions of the same stack without adjusting scope language.
Before: "They'll see I'm flexible."
After: "I'll give them the version that matches this title string tonight."
Score fit before you swap bullets
Paste the posting and your draft into a match tool before you export. Gaps you see there are the bullets you promote, not new jobs you invent.
Score your job match on the version you're about to upload, then fix headline and first bullet gaps first.
Build your resume from a single-column template if your master file still uses tables or icons that break parsers.
Generate a cover letter that repeats the same headline title when the posting still asks for a letter.
One story, several front doors
Your background is fixed; your packaging isn't. Master file plus named versions keeps you honest about dates while giving each req a headline and lead bullet that match how parsers sort.
Tonight, pick two open reqs in different lanes. Duplicate your file twice, swap headlines, promote three bullets each, and log the PDF names. That's what to do when you apply to different roles with one background without burning out on full rewrites.
Read more
Frequently asked questions
Keep one master file with every bullet you might use, then three to five saved versions keyed to role families such as operations, program management, and customer success. Each version shares the same jobs and dates but uses a different headline and reordered first bullets under your current role.
The headline is a target title, not a payroll record. Use the posting title when your work matches the duties. Your experience section still lists real employers and dates. Do not invent employers or dates to fit a title you never performed.
No. Spend ten to fifteen minutes on headline, first bullet under current job, and skills order. Rewrite the full file only when the posting asks for a different seniority band or industry vocabulary you have not surfaced yet.
Use Firstname-Lastname-Role-Company.pdf with the role token matching the posting, not your internal nickname. That name is what recruiters see in the attachment list after the parser imports your packet.