How to tailor your resume to a job description (with a worked example)
Updated 2026-10-27 · 8 min read
Why one resume for every job does not work
Most freshers make one resume in the final year and send the same file to every company on Naukri, LinkedIn and the placement portal. It feels efficient, but it is the main reason good students get no calls. A resume written for "any software job" matches no particular job well.
Two things read your resume before an interview. First, an applicant tracking system (ATS) compares it with the job post and ranks it. Second, a recruiter gives it a quick scan and decides yes or no. Both look for the same signal: does this person have what this job asks for? Tailoring means making that answer easy to see, using only things you have really done.
Tailoring does not mean writing a new resume from scratch each time. Your education, projects and internships stay the same. What changes is the order, the words you use, which bullets come first and which skills you lead with. Once you have a good base resume, tailoring one application takes 15 to 20 minutes.
Step 1: Read the job description like a recruiter
Read the whole job post once without making notes. Then read it again and split it into three parts. Recruiters and hiring managers write job posts in roughly this shape, even when the headings are different.
- Must-have requirements: the degree, skills and tools named under "Requirements", "Eligibility" or "What we are looking for". These are what the ATS filters on.
- Nice-to-have skills: lines that say "preferred", "good to have" or "a plus". They help you rank higher but will not reject you on their own.
- The actual work: lines under "Responsibilities" or "What you will do". These tell you which of your projects to put first.
- Hard filters: CGPA cut-offs, no active backlogs, year of passing, location or shift timings. If you do not meet a hard filter, tailoring will not fix it, so save your time for other jobs.
Step 2: Make a keyword list from the job post
Copy every skill, tool, method and qualification from the post into a list. Write them exactly as the post spells them. If it says "Power BI", do not write only "Microsoft BI tools". If it says "REST APIs", use that phrase. Many ATS match words fairly literally, and recruiters search their database with the same terms.
Mark each keyword with how many times it appears and whether it is a must-have. A skill mentioned three times in the post matters more than one mentioned once at the end. Soft skills such as "communication" or "team player" are worth noting, but they carry little weight on their own. Show them through a bullet, not by listing the word.
If the post is short or vague, open two or three similar job posts from other companies for the same role. Skills that appear in all of them are the core of that role, and they are worth covering even if this one post mentions them only once. This also helps you build a stronger base resume for the whole job family.
You can do this by hand, or paste the job post and your resume into a keyword scanner to see which terms are missing. Either way, the output is the same: a short list of the 8 to 15 terms this job cares about most.
Step 3: Match each keyword to real evidence
Go through your list and, next to each keyword, write where in your life you have actually used it: a project, an internship, a course with an assignment, a hackathon, a college role. This is the honest core of tailoring. A keyword with evidence goes into a bullet. A keyword you only know from a video tutorial goes into the skills list at most, and only if you could answer basic interview questions on it.
If a must-have keyword has no evidence at all, do not add it. Interviewers in technical rounds and HR rounds pick words from your resume and ask about them. A skill you cannot explain does more harm than a missing one. Instead, note it as a gap. If the gap is small, you can close it with a short project before you apply to similar jobs.
Step 4: Rewrite your summary and top bullets
Your summary is the first thing a recruiter reads, so it should name the role and two or three of the job’s main requirements that you really have. Keep it to two or three lines. Do not use a summary written for a different role.
Next, rewrite the first two bullets under your most relevant project or internship. Use the job’s own words where they truthfully describe what you did. If you "built a website" and the job asks for "responsive web interfaces using React", and your website was responsive and built in React, say so in those words. Add a number where you have one: users, time saved, accuracy, records handled. If you do not know the exact number, find it out or leave it out. Do not guess.
Step 5: Reorder sections and skills for this job
Order matters because recruiters read the top third of the page most carefully. Put the section that best proves you fit this job near the top. For a developer role with a strong project, Projects can come right after Education. For a sales role where you did a summer sales internship, Experience comes first.
Reorder your skills list so the job’s must-have skills come first, grouped sensibly (for example, Languages, Frameworks, Tools). Remove skills that are unrelated to this job if the list is long; ten relevant skills read better than twenty-five mixed ones. Finally, save the file with a clear name such as Firstname_Lastname_DataAnalyst.pdf so you can track which version went where.
A worked example: one fresher, one job description
Here is a short sample job post and how a B.Tech fresher changed two bullets for it. The candidate and company are illustrative. Notice that nothing new is invented: the project is the same, only the description is sharper and uses the job’s words.
Sample job post (Junior Data Analyst): - Strong SQL and Excel (pivot tables, VLOOKUP) - Build dashboards in Power BI - Clean and validate large datasets - Explain findings to business teams Before (generic): - Did a project on sales data analysis using Python. - Made charts and presented them in class. After (tailored, same facts): - Cleaned and validated 40,000 rows of retail sales data in SQL and Excel, removing duplicates and fixing date formats. - Built a Power BI dashboard showing sales by region and month; presented the three main findings to a faculty review panel. Summary, after: B.Tech (CSE) 2026 graduate with hands-on SQL, Excel and Power BI from two data projects. Comfortable cleaning messy datasets and explaining results to non-technical audiences.
How far can you go without lying?
A simple test: for every line on the tailored resume, could you explain it for two minutes in an interview, with details? If yes, it stays. Using the job’s vocabulary for work you really did is good tailoring. Claiming a tool you never used, inflating a team project into a solo one, or changing an internship’s dates is not tailoring, and it often surfaces in background verification, which many Indian employers run before or after joining.
It is fine to describe the same project differently for different jobs. A college attendance app can be framed around the database for a backend role and around the interface for a frontend role, as long as you did both parts.
How ApplyNivo helps
You can paste a job post and your resume into the free keyword scanner at /tools/keyword-scanner to see which terms are missing, then check the result with the free ATS checker at /ats-resume-checker (no login). In the 7-day free trial, ApplyNivo rebuilds your resume for each job from your own facts. It never invents experience, and where a number is needed but unknown it leaves a placeholder such as [add %] for you to fill in.
Frequently asked questions
How many keywords from the job description should my resume have?
There is no magic number. Aim to cover the must-have skills you genuinely have, each in at least one bullet that shows how you used it, plus the skills list. Repeating a keyword many times does not help and makes the resume read badly. Recruiters notice keyword stuffing quickly.
Should I copy sentences directly from the job description?
No. Use the job’s key terms, such as tool names and skills, but write your own sentences about your own work. Copying full lines from the job post looks lazy to a recruiter and does not prove anything. A bullet should describe what you did and, ideally, the result.
Do I need to tailor my resume for mass recruiters like service companies?
Less than for product companies or niche roles, because mass hiring filters mainly on degree, CGPA, year of passing and test scores. Still, a clean resume that names the skills in the job post, such as Java, SQL or communication, helps in the interview stage where the panel reads it.
What if I do not have most of the skills the job asks for?
If you are missing several must-haves, apply to other jobs that suit you better and use this one as a learning list. If you are missing one or two, you can still apply; recruiters rarely find candidates who match every line. Do not add skills you do not have.
How long should tailoring take for each application?
With a good base resume, 15 to 20 minutes: read the post, list the keywords, adjust the summary, reorder skills and rewrite two or three bullets. Spending this time on ten well-matched jobs usually gets better results than sending one generic resume to a hundred.