How to tailor your resume to a job description, honestly

Tailoring your resume means changing the order, wording and emphasis of what's already true about you so it answers one specific job post. It does not mean adding skills you don't have. Done well, it takes about 15 minutes per application, and it is the single biggest improvement most engineering resumes can make.

This guide is for software engineers, students preparing for campus placements, and anyone sending the same resume to fifty companies and hearing back from two. You'll get a repeatable method, real before-and-after bullets, and a clear line between tailoring and lying.

Why one resume for every job doesn't work

Two things happen to your resume after you apply.

First, it's often filtered or ranked by software. In Harvard Business School and Accenture's Hidden Workers research, 63% of the employers surveyed in the US, UK and Germany used a recruitment management system. More than 90% of those used it to make the first cut or rank applicants.

Second, recruiters search it. Applicant tracking systems let recruiters search resume text by keyword. Greenhouse, for instance, documents a full-text resume search and keyword filters marked "required" or "preferred".

A generic resume describes you in your own words. A tailored resume describes the same experience in the employer's words, with the most relevant proof first. Both are honest. Only one shows up when a recruiter searches for "Kafka" or "React Native".

You may have read that "75% of resumes are rejected by ATS". That figure has no published study behind it; we unpack it in Is a LaTeX resume ATS-friendly?. The real reason to tailor is simpler: relevance is easier to see.

Step 1: Read the job post like a checklist

Copy the job description into a notes file and split its requirements into two lists:

• Must-haves: usually under "Requirements", "What you'll need" or "Minimum qualifications". Look for years of experience, core languages and frameworks, degree requirements, and words like "must" or "strong".
• Nice-to-haves: "Bonus", "Preferred", "Good to have".

Then underline the exact terms they use. Write down "PostgreSQL", not "SQL databases". Write down "CI/CD with GitHub Actions", not just "DevOps". Note the job title too: "Backend Engineer", "SDE-1" and "Software Engineer, Platform" may be the same job, but the title in the post is the one recruiters search.

For example, a backend post might boil down to:

Step 2: Match each requirement to proof you already have

Now go down the must-have list and, for each item, find where your resume proves it. Proof is a bullet, project or role that shows you did the thing, not a word in your skills list.

This table drives everything that follows:

• Proven items need the employer's wording and a good spot.
• True but missing items need a bullet. This is where most people leave easy matches on the table.
• Gaps stay off the resume. More on that in Step 6.

Step 3: Use their words where they're true

Swap your wording for theirs only when it describes the same thing:

• "Postgres" becomes "PostgreSQL", if the post says PostgreSQL.
• "Made APIs" becomes "Designed REST APIs".
• "Unit tests" becomes "Unit and integration tests with JUnit", if that's what you actually wrote.

Put each important term where it carries weight: in a bullet that proves it, and once in your skills section. Repeating a keyword five times doesn't help a human reader, and stuffing skills you can't defend in an interview hurts you.

Step 4: Reorder so the best match comes first

Recruiters skim, so order is a tailoring tool:

• Bullets within a role: move the bullet that best matches the must-haves to the top of each job.
• Projects: for a student or fresher, projects often carry the resume. Lead with the project that uses the job's stack.
• Skills section: list the job's core technologies first. If the post is Go-first, "Go, PostgreSQL, Docker" should come before "C++, MATLAB".
• Sections: with less than a year of experience, Projects can come before Experience.

Step 5: Rewrite the top bullets around impact

The bullets you moved up deserve a rewrite. A reliable pattern is action + what you built + the tool + the result:

Before: Worked on backend APIs for the payments team.

After: Built 6 REST APIs in Java (Spring Boot) for refunds and settlements, backed by PostgreSQL; cut refund processing time from 2 days to 4 hours.

Before: Did a project on a chat app.

After: Built a real-time chat app with Node.js, WebSockets and Redis pub/sub; load-tested to 2,000 concurrent connections on a single instance.

Only use numbers you can explain in an interview. If you don't know the exact figure, describe the scope honestly: "used by the 40-person support team" is a fine result.

Step 6: Handle the gaps honestly

You'll rarely match every line. When you can't back up a requirement:

• Leave it off. Listing Kubernetes because the job wants it gets found out in the first technical round, and it's the fastest way to lose a recruiter's trust.
• Show adjacent proof instead. No Kubernetes, but you deployed with Docker Compose and GitHub Actions? Say exactly that. A reader can see you're close.
• Close small gaps for real. If a missing skill shows up in every post you want, a weekend project that uses it gives you something true to write.
• Remember most posts are wish lists. The Hidden Workers research found employers often recycle old job descriptions and filter out people who don't match exactly, and it recommends they stop. Apply when you meet the core must-haves.

Step 7: Check the match and the file, then save a copy

Before you hit Apply:

1. Re-read the must-have list and confirm each proven item is visible on the page, not just in your skills line.
2. Run a match check. Paste the job post and your resume into the free resume and job description checker to see which required skills, keywords, years and title your resume shows.
3. Test that the PDF parses. Copy all the text out of the PDF and paste it into a plain-text editor; everything should come through intact. Our ATS guide explains why.
4. Keep it to one page if you have under about five years of experience.
5. Save a copy per company, for example resume-razorpay-backend.pdf, so you know exactly what you sent when the recruiter calls.

What tailoring is not

It's worth being explicit, because "optimise your resume for ATS" advice often drifts into fiction:

• Not adding tools, titles, employers or years you don't have.
• Not pasting the job description into your resume in white text. Recruiters see the extracted text, and it reads as a trick.
• Not inflating numbers. "Improved performance by 300%" invites the question "measured how?"

Tailoring changes how your real experience is presented, never what it is.

Doing this for 20 applications a week

The method above is about 15 minutes per job once you've done it a few times. To keep it manageable:

• Keep a master resume with every bullet you've ever written, and tailor down from it rather than writing from scratch.
• Group similar roles. Three backend posts at similar companies can share one tailored version with small tweaks.
• Spend your effort where it counts. Tailor carefully for the roles you want most, and lightly for the rest.

If you'd like help with the rewriting, fastcv's AI tailoring does Steps 2 to 5 for one job post: it rewords only what your resume already shows, lists what you can't claim, and lets you accept or skip each change. The method is the same either way, and it works just as well by hand.

Frequently asked questions

How long should tailoring a resume take?

About 15 minutes once you have a master resume to work from. The first time takes longer because you're writing bullets you'll reuse.

Should I tailor my resume for every job?

Tailor for every job you really want. For similar roles, one tailored version per role type, such as backend, data or frontend, with small tweaks per company is a practical middle ground.

Is it okay to copy keywords from the job description?

Yes, when the keyword describes something you've actually done. Using the employer's exact term for your real experience is the point of tailoring. Adding keywords for skills you don't have is not.

Do I need to tailor the summary or objective too?

If you have one, make the first line name the role you're applying for and your strongest matching skill. Many engineering resumes, including Jake's Resume, skip the summary entirely, and that's fine.

What if I meet only half of the requirements?

Apply if you meet the core must-haves, such as the main language and the type of work, and show adjacent proof for the rest. Job posts often list more than the role truly needs.