Tailor Resume to the Posting: A Step by Step Method

To tailor a resume, you read the posting for what it asks for, keep the bullets from your history that prove those things, rewrite them in the posting's own words, put the most relevant skills first, and then check that the file still reads cleanly when a parser pulls the text out. Your history does not change. What changes is selection, order and vocabulary, and that is enough to move a resume from "probably relevant" to obviously relevant for the person, or the search box, reading it.

The reason vocabulary matters is mechanical. Greenhouse, a widely used applicant tracking system, explains to candidates that its AI analyzes the job description and suggests relevant keywords to recruiters, and that "when recruiters search for these terms, they'll find exact matches in candidates' applications." Exact matches. If the posting says Tableau and your resume says "BI dashboards", you are relying on a recruiter, or a suggested synonym, to make the leap for you. That is a search problem, not an automatic rejection: the popular claim that 75% of resumes are rejected by ATS software is a myth we traced. Employers know this costs them people: in the Harvard Business School and Accenture "Hidden Workers" survey, 88% of employers believed qualified high-skills candidates were screened out because they did not match the exact criteria in the job description.

The method below runs on one invented posting and one invented resume, so you can see each step change the page.

What tailoring a resume means

Tailoring is editing, not writing. You start from a master resume that holds every role, bullet, project and skill you could honestly claim, often two or three pages of it. For each posting you make a one page cut of that master, using three levers. If you are building the master from scratch, our guide to what to put on a resume lists every section in order. The three levers:

• Selection. Which bullets appear at all.
• Order. Which bullets lead each role, and which skills lead the skills line.
• Vocabulary. Which words describe the work, so they match the words the employer used.

What tailoring does not touch is the factual skeleton: employer names, job titles, dates, schools, degrees, certifications and every number. Those are the same on every version you send. A recruiter who sees two of your applications should see two different emphases, never two different histories.

Is it worth the effort? Huntr's 2025 annual job search report found that applications sent with a tailored resume converted to an interview, offer or hire at 5.8%, against 3.73% for untailored resumes, across 65,088 tailored and more than a million untailored applications in its tracker. That is observational data from one product's users, and people who tailor may also be the people who apply more carefully, so the honest reading is "associated with", not "causes". It is still the largest public comparison there is, and it points the same way as the employer survey. The full evidence is weighed in should I tailor my resume for each job.

Step 1: pull the requirements from the posting

Read the posting once to understand the job, then a second time with a pen. Strip out the parts that describe the company rather than the work: the mission paragraph, benefits, pay range, the equal opportunity statement. What is left sorts into five buckets:

1. Named skills and tools. Tableau, SQL, Python, Salesforce, Kubernetes. These are the terms most likely to be searched, and our post on hard skills for a resume covers which ones recruiters look for.
2. Years and level. "3+ years", "senior", "lead".
3. Education. A degree, a field, a license.
4. Responsibilities. The verbs and objects: "build dashboards", "partner with carrier management", "present to leadership".
5. Domain words. The industry vocabulary: on-time delivery, carrier performance, claims, churn.

Write each requirement down in the posting's exact wording. Our guide to resume keywords shows how to find them in any posting. Mark the ones that appear more than once, and the ones listed as required rather than preferred.

Here is the invented posting this post works through. The company and every detail are made up.

Operations Analyst, Harbor Lane Logistics

What you'll do: Build and maintain Tableau dashboards that track on-time delivery and carrier performance. Write SQL to pull shipment data from our data warehouse. Partner with the carrier management team to find cost savings. Present findings to operations leadership every week.

What you bring: 3+ years in an analytics role, ideally in logistics or supply chain. Advanced SQL. Tableau or a similar BI tool. Python for data cleaning is a plus. Bachelor's degree in a quantitative field.

The requirements list from that posting:

Step 2: keep the bullets that prove them

Now open your master resume and go through it bullet by bullet. For each one, ask which requirement on the list it proves. A bullet that proves a required item stays. A bullet that proves a preferred item probably stays. A bullet that proves nothing on the list goes, however proud you are of it, unless you need it to explain a role.

The invented candidate's master resume has one current role, Data Analyst at Brightwater Distribution, 2021 to present, with seven bullets:

1. Built reporting in Power BI and Tableau for the fulfillment team covering late shipments by region.
2. Wrote queries against the shipment database to answer ad hoc questions from managers.
3. Analyzed freight invoices and flagged billing errors, recovering $48,000 in 2024.
4. Organized the team's quarterly volunteer day.
5. Cleaned vendor data files with Python scripts, cutting a weekly manual task from 4 hours to 30 minutes.
6. Presented a monthly metrics summary to the director of operations.
7. Trained two new hires on the reporting tools.

Mapped against the requirements: bullet 1 proves Tableau and delivery tracking, bullet 2 proves SQL, bullet 3 proves cost savings with carriers, bullet 5 proves Python for data cleaning, bullet 6 proves presenting to leadership. Bullet 7 is mild evidence of nothing the posting asked for, and bullet 4 is evidence of being a good colleague, which the interview can show. Both go. Five bullets remain, each tied to something the employer wrote down.

Step 3: rewrite in the posting's words

This is the step that makes the difference to a keyword search, and the one where people either do too little or too much. The rule is narrow: where your bullet describes the same thing the posting describes, use the posting's term for it.

• "Late shipments by region" and "on-time delivery" are the same metric seen from opposite ends. Use "on-time delivery".
• "Queries against the shipment database" is SQL against shipment data. Say "SQL", because that is the word a recruiter types.
• "Freight invoices" in a posting that talks about carriers can honestly become "carrier invoices", if the invoices were from carriers.
• "The director of operations" is operations leadership. The posting's phrase covers it.

Three things do not change in a rewrite: numbers, names and scope. The $48,000 stays $48,000. Brightwater stays Brightwater. A monthly summary does not become a weekly one because the posting says weekly. And "advanced SQL" goes on the page only if you would be comfortable with an advanced SQL question in the interview, because the word "advanced" is a claim about your level, not a description of your work.

Lead each bullet with the part the posting cares about. If the posting's first responsibility is dashboards, the dashboard bullet goes first under your current role. When a bullet needs a stronger opening verb, our list of action verbs for a resume groups them by what you did.

Step 4: order skills by relevance

The skills line is the densest keyword surface on the page, and it is usually written once and never touched. For each posting, reorder it so the posting's named tools come first, in the posting's spelling, and drop the ones irrelevant to the role so the relevant ones are not buried. The resume skills section guide covers what to list and in what order.

If you have a summary line at the top, it is the other place worth two minutes. Point it at the role without renaming your past: "Data analyst in freight and fulfillment reporting, working in SQL, Tableau and Python" tells an operations analyst hiring manager what they need to know without pretending the candidate's title was ever Operations Analyst. More are in our resume summary examples.

Step 5: check it the way a parser reads it

A tailored resume that does not parse has thrown away the work. Before sending, export the file and run the paste test from our post on ATS friendly resume format: open the file, select all, copy, and paste into a plain text editor. You should see your name first, then your roles in order, each with an employer, title and date range on its own line, and every keyword you just added appearing as real text. Do not wait for a score from the employer's system, because, as resume ATS score explains, no ATS actually gives you one.

Then run two checks of your own against the master resume:

1. The facts check. Employers, titles, dates, schools, degrees and every number match the master exactly. Editing is where these drift, usually by accident.
2. The interview check. Read every skill and every bullet on the tailored page and ask whether you could talk about it for two minutes with someone who knows the subject. Anything that fails comes off.

A before and after example

Here is the invented candidate's current role, before and after the five steps.

Skills line before: Excel, Power BI, Tableau, SQL, Python, Salesforce, Google Analytics.

Skills line after: SQL, Tableau, Python (data cleaning), Power BI, Excel.

The employer, the title Data Analyst, the dates, the degree and the three numbers are identical in both versions. The tailored version is shorter, and every line in it answers a question the hiring manager wrote down. For more full pages, each set beside a sample posting, see these resume examples with line by line notes.

One more check on the first bullet: "maintained" is only there because, in this invented history, the dashboards ran for years and the candidate kept them working. If yours were built once and handed off, the posting's word does not fit and you should leave it out.

Where mirroring ends and invention begins

The example stayed on the safe side of a line that most tailoring advice blurs. It helps to split edits into three kinds.

The middle row is where the real decisions are. Plenty of people have used a tool in a side project, a course or a previous job and simply never put it on the resume. Adding it is accurate. Adding a tool you have only read about is a bet that nobody asks, and the interview is exactly where somebody asks.

AI tailoring tools draw this line in different places, and you should know where yours draws it. If you use ChatGPT, our ChatGPT resume prompts are written to tailor without inventing. ApplyEze, for example, goes further than our table: it brings the posting's named skills and tools onto your skills line, which is a deliberate choice for getting past keyword screening. What it does not move are the facts in the bottom row. Whatever tool you use, the practical rule is the same: read the tailored resume, and be ready to discuss anything on the page. With ApplyEze there is no step to remove a skill before a live run, so do that reading in a dry run.

Doing this for every application

The method is not hard. The problem is repetition. Enhancv's tailoring page puts manual tailoring at "Three hours" per job, a figure it states without a source, and even if your number is a fraction of that, it multiplies by every posting you apply to. Our post on how many applications it takes to get a job covers why that number is usually higher than people plan for.

Three habits make it faster by hand:

• Keep the master resume long. Every bullet you have ever written, each tagged with the skills it proves. Tailoring becomes selecting, not drafting.
• Keep a vocabulary list per role type. The same ten or fifteen terms recur across most postings for one kind of job. Once you have the posting's version of each, step 3 takes minutes. We have pulled starter lists from real postings for project managers, customer service, sales and marketing.
• Save each tailored version with the posting. If a recruiter calls, you want to see exactly what they saw. The same goes for a cover letter, if you send one; is a cover letter necessary covers when it counts, and our guide to how to write a cover letter builds one from the same list of requirements.

This is the work ApplyEze automates. For every posting, it writes a resume for that posting, as PDF and DOCX, and a cover letter when the form asks, and reads each file back with a parser check before anything is uploaded. It mirrors the posting's own vocabulary, so a recruiter's keyword search finds you, and it brings the posting's named skills and tools onto your skills line, even when your own record does not list them. There is no step to remove one before a live run, so use a dry run to see what it writes, and be ready to discuss anything on the page. A certification the posting asks for is not added unless you hold it. Your employers, job titles, dates, schools, degrees and certifications come from your own record, and code rejects a rewrite that adds a figure, employer, school or credential your record does not hold. It is still your name on the application, so read what it wrote. If you are comparing tools, our guide to the best AI for resume tailoring sets out what to test.