You've got the job description open in one tab and your resume in the other. The posting says "cross-functional stakeholder management," so you find the bullet where you wrangled three departments into shipping something and rewrite it to say "managed cross-functional stakeholders." You do this eleven more times. An hour later you have a resume that matches the posting beautifully and sounds like it was written by the posting. Somewhere in the keyword swap, the person who actually did the work disappeared.
That's the trap with tailoring. Most advice treats it as a translation exercise: take your experience, convert it into the employer's dialect, submit. The keywords get in, the voice gets stripped out, and what lands on the hiring manager's desk is a document that clears the screen and then fails the only test that matters — does this person sound like someone I want to talk to?
What tailoring actually is
Tailoring is a selection problem, not a rewriting problem. You have more experience than fits on a page. The job description tells you which parts of it this employer cares about. Your job is to choose the right evidence and put it in the right order — not to disguise your evidence as their language.
Think about what the hiring manager is doing when they read your resume. They're holding a mental model of the role's problems and scanning for proof that you've solved problems shaped like theirs. The keyword match gets you past the software. The proof gets you the call. A resume that says "drove operational excellence across distributed teams" matches the keyword and provides zero proof, because it could describe anyone. A resume that says "took a support queue that was three weeks behind and got it to same-day response in a quarter, without adding headcount" proves something — and it happens to demonstrate operational excellence better than the phrase ever could.
The distinction matters because the two failure modes of tailoring sit on opposite ends. Under-tailor and you send the same generic resume everywhere, making the hiring manager do the work of figuring out why you fit. Over-tailor and you parrot the posting back at them, which reads as exactly what it is: someone telling them what they want to hear. The version that works lives in between, and the way to find it is to change what you select, not how you sound.
Read the job description for problems, not keywords
Before you touch your resume, read the posting twice. The first read is for keywords — the nouns and skills the screening software will look for. Note them, because you do need them. The second read is the one most people skip: read for the problem behind the posting. Every job listing is a company describing a pain point in the most sanitized language their HR team would approve. "Fast-paced environment" means things are on fire. "Ability to influence without authority" means the org chart is a suggestion and you'll need to get people to act anyway. "Comfortable with ambiguity" means nobody has figured out what this role is yet.
Once you can name the actual problem, tailoring gets much easier, because now you're not matching words — you're matching evidence to pain. If the posting is screaming "we can't ship on time," your bullet about rescuing a deadline belongs at the top of your most recent role, even if it wasn't the biggest thing you did there. The biggest thing you did is not the most relevant thing you did, and the resume is not a monument. It's an argument.
Where the keywords go — and where your voice stays
Here's the practical split. Keywords belong in the nouns: skill names, tools, certifications, methodologies, the literal terms of the trade. If they call it "demand generation" and you've been writing "growth marketing," use their term. That's not losing your voice; that's speaking the local language, the same way you'd say "soda" in one city and "pop" in another. Nobody's identity lives in whether the section says "Stakeholder Management" or "Cross-Team Leadership."
Your voice lives in the verbs and the evidence — in how you describe what you actually did. "Spearheaded a transformative initiative to optimize workflows" is voiceless no matter whose resume it's on. "Rebuilt the onboarding flow after watching five new hires get lost in the same place" is a person. Keep the sentences yours: the specific situation, the honest scale, the verbs you'd actually use if you were telling a friend what happened. A hiring manager reading two hundred resumes can feel the difference between language that came from a posting and language that came from a memory, even if they couldn't tell you why.
The test for any tailored bullet: would you say this sentence out loud in the interview? Because you'll have to. Every line you borrow from the job description is a line you'll need to defend in a conversation, in your own words, with details. If the bullet only works on paper, it's a liability. If it's something you can expand into a five-minute story, it's an asset — and it was probably written in your voice to begin with.
The order of operations
The whole process, start to finish: read the posting for keywords, then read it again for the problem. Go through your full inventory of experience — not your current resume, your actual history — and pick the four or five pieces of evidence that hit the problem hardest. Reorder your bullets so the most relevant evidence leads each role. Swap your generic terms for their terms wherever a real synonym exists, and nowhere else. Then read the result out loud. Anywhere it stops sounding like you, that's where you over-corrected. Put your sentence back and keep their noun.
Notice what's not in that list: rewriting your accomplishments to inflate their relevance, claiming adjacent experience you don't have, or restructuring your entire history to mirror the posting's priorities. If you have to contort the resume that hard to fit the role, the resume isn't the problem. The fit is — and it's better to learn that before the interview than during it.
The candidates who do this well aren't the best writers. They're the ones who know their own evidence cold — every story, every number, every hard thing they navigated — so that tailoring becomes a quick matter of selection instead of a desperate act of invention. When you know exactly what you've got, you never have to borrow someone else's words to describe it.
Tell me if this matches your experience on the hiring side. I'm curious how often a keyword-stuffed resume actually makes it through to a conversation, and what happens when it does.
Prism Tree builds tailored resumes this way by design — it pulls from your full career history, ranks your evidence by quality against the specific job, and writes in your documented voice instead of the job posting's. The keywords get in. You stay in too. Try it here.