How to tailor your resume: choose your stories first, then edit the lines

Do you tailor your resume by highlighting the keywords in the job description and working them into your bullets until the match feels good? That version might get past the software, but it hands the interviewer a pile of claims with nothing they want to ask you about.

This article covers a different order of operations: pick the three or four stories you want the interview to be about, then read the job description to predict their questions. Edit the resume line by line afterward, so every bullet points at one of those stories. Do the story picking before you touch the file, because every editing decision gets easier once you know where you want the conversation to go.

The advice comes from Ethan Evans, a retired Amazon VP who spent 15 years there and reviewed real resumes across dozens of episodes of his Level Up show; Nikhyl Singhal, former CPO of Credit Karma and VP of Product at Meta, who runs The Skip; and Lauren Ipsen, who recruits senior executives at Daversa Partners. Every quote plays the exact moment it was said.

Start from what a resume is for

Evans opened one of his earliest resume reviews, for a Harvard graduate applying to director of mergers and acquisitions roles, with the rule that drives everything else in this article.

There's a second effect worth planning for. Once the resume gets you the interview, it sits in front of the interviewer, and they build most of their questions from whatever you chose to put on it. Every line you keep is a question you're inviting. Tailoring, done properly, means deciding which questions you want and rebuilding the document so those are the ones you get.

Choose your three or four stories first

Before you edit a single bullet, write down the three or four stories you'd most want to spend the interview talking about. A story here means a specific piece of work you can talk about for two minutes: the situation, what you did, and what changed because of you. Singhal calls these your greatest hits, and he tells people to prepare them before worrying about any introduction or summary.

He's describing how to talk about your career, and the same math applies to the document. You already know which conversations you want. The resume's job is to make an interviewer want to start them.

These stories do double duty. The same three or four should power your behavioral answers and your introduction, so build them once as a story bank. The behavioral interview questions playbook covers how to structure each story for "tell me about a time" questions, and the tell me about yourself playbook covers the 90-second version you'll open with.

Read the job description for the questions they'll ask

Most people read a job description once, hunting for keywords. Read it twice, for two different things.

First, read it as a preview of the interview. Take the top five or six requirements and turn each one into the question an interviewer would ask about it. "Owns pricing strategy across three product lines" becomes "tell me about a time you set pricing." "Partners with engineering leadership" becomes "give me an example of a hard tradeoff you negotiated with engineering." Write the questions down. Then check them against your story list. If your three or four stories give you a strong answer to most of those questions, you've chosen well. If they don't, either swap in different stories or take it as useful information about fit.

Second, read it for vocabulary. Recruiters search and skim using the words in their own posting, so if they say "growth marketing" and your resume says "demand generation" for the same work, use their term. This is the honest version of keyword matching: the same facts, described in their words. It helps with screening software too, but the bigger audience is the humans skimming.

One more thing raises the odds anyone reads the tailored version at all: a person inside the company sending it along. If you don't have that person yet, the foot in the door playbook covers how to build that path before or while you apply.

Tailor line by line

The summary. One or two lines at the top: what you do, and the thread that connects your work to this role. Write it last, after the bullets below it have been chosen, so it summarizes evidence that actually appears on the page. If it runs longer than two lines, Evans's advice is to break it into bullets, because people skim past paragraphs.

The order. Within each role, move the bullets that support your chosen stories to the top. The first bullet under your current title gets more attention than anything else on the page, so it should carry your strongest story. You're allowed to reorder for every application; the facts stay the same, you're just changing what a skimmer hits first.

The numbers. Give each story at least one bullet with a concrete result. In a review of a resume that claimed "70 plus subsystems, managing 4,180 control system signals," Evans said "numbers equals facts": specific figures make a claim believable, even when the reader can't check them. If you don't have exact figures, honest approximations of scale, frequency, or before-and-after still work.

The tease. Here's where most tailoring goes wrong. People try to cram the entire story into the bullet, and a bullet that tells the whole story leaves the interviewer nothing to ask. Singhal uses a Hollywood comparison for career storytelling that applies directly.

A good bullet names the result and hints at the approach: "Cut enterprise onboarding time from six weeks to nine days by rebuilding the implementation handoff." The interviewer who cares about onboarding has to ask how. That's the question you prepared a two-minute story for. Save the full version for the interview instead of squeezing it into the page.

Cut anything that invites the wrong question

Since every line invites a question, some lines invite questions you don't want, and plenty invite nothing at all. Reviewing one resume, Evans hit a header full of Instagram and YouTube links and reacted as the hiring manager he used to be: "what the hell does that have to do with anything?" Cut with the same standard. If a line doesn't support one of your stories and doesn't answer a stated requirement, it's taking space from something that does.

The usual suspects:

• Generic responsibility lines. "Managed stakeholders and cross-functional partners" describes almost every job. Replace it with what changed because of your work.
• The skills soup. A long list of tools invites a pop quiz on the one you know least. Keep the skills this posting names, plus the ones you'd happily be tested on.
• Old roles at full length. Compress anything past ten years into one line each, or one short section. Those jobs rarely hold your best stories.
• Decoration. Social links, hobby lists, and objective statements that repeat the job title. None of them earn an interview.

Length follows from the cutting: one page early in your career, two at most later on. In the same review, Evans liked that the applicant had boiled a two-page resume down to one.

Run the 30-second read test

Before you send anything, test the resume against the way it will actually be read. Evans is blunt about how little time that is.

So run the test literally. Hand the resume to a friend for 30 seconds, take it back, and ask three questions: What does this person do? Which two results stood out? What would you ask them about in an interview? If their answers match your chosen stories, the tailoring worked. If they noticed the wrong things, fix the mismatch mechanically: move the right bullets up, bold the numbers you want caught, and cut whatever stole their attention.

No friend handy? Set a 30-second timer and skim your own resume the way you skim anyone else's: top of the page, first bullet of each role, anything bold. Whatever you didn't get to in 30 seconds, the recruiter probably won't get to either.

Point your interview answers at the same stories

The payoff of stories-first tailoring shows up in the interview. Your resume made them want to ask about three or four specific things. Your "tell me about yourself" answer previews the same three or four things in 90 seconds. Your behavioral answers are the full two-minute versions. Everything the interviewer touches points at evidence you picked on purpose, and nothing you say contradicts the page in front of them.

That alignment only holds if you've practiced the spoken versions before they count. Ipsen has watched senior candidates burn interviews at companies they wanted while they figured this out live.

Tell each story out loud twice before you apply anywhere that matters. Record one attempt, listen back once, and fix the spot where the result got buried. You've already done the hard part by choosing the stories; this step just makes sure the first time you tell them out loud isn't in the interview.

Frequently asked questions

How different should each tailored version be?

Usually about 20 percent of the file: the summary, the bullet order, the lead bullets under your current role, and the vocabulary. The underlying facts and most of the bullets stay the same. If a role needs more change than that, check whether your story choices fit it at all.

Do keywords still matter for the ATS?

Use the posting's vocabulary wherever it honestly describes your work, and you've covered most of what matters. Screening software mostly stores and ranks rather than auto-rejecting, and the recruiter searching that system uses the words from their own posting. Writing for the human skimmer covers the software too.

What if I don't have exact numbers?

Use honest approximations of scale, team size, frequency, or before-and-after: "about 200 customers," "roughly 40 releases a year." A rounded number you can defend works better than a precise one you can't back up, and either works better than an adjective.

Should I tailor for every single application?

Do the full version for jobs you actually want. For similar roles at similar companies, one tailored version per role type covers the group, since the predicted questions barely change. Don't skip it entirely, though; the generic version you send everywhere is the weakest one you have.

Is it dishonest to leave things out?

No. Choosing what to feature is selection, and every resume does it. What crosses the line is fabrication: every fact on the page has to be true and able to survive follow-up questions, because inviting questions is the whole strategy.

The method on one page