How to tailor your resume to a job description

Most students send the same resume to every opening. It feels efficient, but each job is looking for something slightly different, and a recruiter reading 200 applications decides in seconds whether yours fits. Applicant tracking systems (ATS) make this stricter: recruiters search them for the skills in the job post, and a resume that never uses those words does not come up.

Tailoring means making the parts of your experience that match this job easy to find. It never means adding things you have not done.

Copy the job description and split it into three lists before you touch your resume:

• Must-haves: skills and qualifications the post says are required.
• Nice-to-haves: anything marked preferred, a plus or good to have.
• The work itself: what you would actually do every day.

For example, a backend developer opening in Bengaluru might list Java, Spring Boot, MySQL and REST APIs as must-haves, Docker and AWS as nice-to-haves, and "build and maintain APIs for our payments team" as the work. Those three lists tell you what to lead with.

If the post says REST APIs and your resume says "backend services", a recruiter searching for REST APIs will miss you. For every must-have you genuinely have, use the job's exact wording at least once:

• In your skills section, so it is found in a search.
• In a bullet, so it is backed by something you did. A skill that appears only in a list is easy to doubt.

Do not paste keywords in white text or repeat them ten times. Recruiters read the resume after the search, and keyword stuffing is obvious to a person.

Recruiters read top to bottom and stop early. Put what matches the job where they will see it first:

• Reorder your projects so the one closest to the job comes first.
• Reorder skills so the must-haves lead each group.
• Inside each entry, put the most relevant bullet first.
• If you use a headline, make it match the role: "Backend Developer (Java, Spring Boot)" rather than "Software Engineer".

The same work can be described in a way that fits the job better. For the backend role above:

• Before: "Made a college event website with a login system."
• After: "Built REST APIs in Spring Boot and MySQL for a college event site with login and registrations, used by 1,200 students during the fest."

Nothing new was invented. The rewrite names the tools the job asks for, says what you built and adds a result.

Space on one page is limited, so every line should earn its place for this job. Hide the project that has nothing to do with the role, drop skills the job will never use, and shorten old or unrelated bullets. Keep the resume to one page; for a fresher, a second page almost always means weaker points diluting strong ones.

Tailoring only works with things you can talk about. If a skill from the job description is missing, do not add it; interviewers ask about every line. Instead, mention related work you have done, or learn the basics and build a small project with it before you apply.

• Every must-have you have appears in skills and in a bullet.
• The most relevant project or internship is at the top.
• Your headline, if you use one, names this role.
• No line on the page is there only for other jobs.
• It still fits on one page and reads well as a PDF.
• Every claim is something you can explain in an interview.

Doing this by hand for every application takes time, which is why most people skip it. In Shortlist you keep one main resume and tailor a copy for each job:

1. Open your resume, choose Improve with AI and add the job by pasting the description or a link to the post.
2. Choose Tailor resume. It reorders, trims and rewrites bullets for that job, using only what is already in your resume and profile.
3. Review every change side by side and apply the ones you agree with. Nothing changes until you apply, and you can undo from History.

Then run the free ATS resume checker with the same job to see which of its keywords your resume covers. The free plan includes one tailored resume a month to try it.