ATS

How to write a resume for India (2026 guide)

By AI Resume Maker · 27 July 2026 · 12 min read

Writing a resume in India in 2026 means writing for two readers, and most advice only covers one of them. Your resume first has to get past an applicant tracking system that reads single-column plain text and ranks you on how closely your words match the job description. If it clears that, it has to survive a person who spends under thirty seconds on it, looking for the same three things the software was looking for, in a different order. This guide covers the whole resume in the order you should actually work through it: section order, bullets, the India-specific lines that hurt you, the keywords that help, and the hand-off to the HR round.

The two readers, in the order they read you

Every Indian resume gets read twice before anyone senior sees it. First by an applicant tracking system. TCS, Infosys, Wipro, the big product companies and most career portals all run one. It parses your file into structured fields, scores it against the posting, and either forwards you or drops you. If you clear that, a recruiter or panel lead reads it for ten to thirty seconds and decides whether to send it further up.

Both of them are looking for the same evidence: your skills stated in the posting's own words, your work history with numbers attached, and your education and credentials in the usual places. The software looks for it in your vocabulary and your structure. The recruiter looks for it in your numbers and in how specific you are. You have to clear both.

Section order that works in India

One section order works for both readers, and it is worth following even if your current resume looks fine to you.

Contact details at the top: name, phone, email, city and LinkedIn. Leave out the photo, the postal address, your father's name and your date of birth. A photo and a date of birth are both parsing hazards and bias risks, and the recruiter has your LinkedIn for anything else.
A professional summary in two or three lines: what you specialise in, how many years you have, and the strongest number you can claim. Don't write an objective statement here. For many readers the summary is the only part they read in full.
Work experience in reverse chronological order. Two or three bullets for recent roles and one or two for older ones, but never zero. Write each bullet as an outcome you produced.
Skills grouped by category: languages, frameworks, databases and tools. Don't dump fifty keywords into one comma-separated line.
Education after experience once you have any. Degree, institute, year, and CGPA only if it is 7.0 or above or the employer asks for it.
Projects, certifications and achievements last. These are optional, though a working GitHub link or a project outcome with a number in it is worth more than white space.

The India-specific lines to cut

These habits are almost universal on Indian resumes, and almost absent on the ones that get shortlisted at companies worth applying to. Each one costs you either a line or a clean parse.

The photo. It is a parsing hazard and it invites age and gender bias. Your LinkedIn already shows the recruiter whatever a photo would.
The declaration. 'I hereby declare that the above information is true…' followed by a signature and a place. It serves no purpose on a screened resume and eats four lines.
The objective. 'Seeking a challenging role in a reputed organisation where I can utilise my skills.' It burns the most valuable line on the page and says nothing. Put a two-line summary there instead.
Class 10 and 12 percentages, once you have a degree. Some campus placement rubrics still ask for them, and in that case include them. Otherwise drop them and use the space for a project.
Date of birth, marital status, nationality, father's name, and the languages you learnt at school. These are left over from a different hiring era. Neither the software nor the recruiter needs any of them.

What a good bullet looks like

Your bullets are where most resumes are won or lost, and two rules carry almost all the weight.

First, write every bullet as an outcome. 'Responsible for the payments module' is a line lifted straight out of a job description. 'Cut payment failure rate 38% by reworking the retry path, and shipped it with zero rollback across three releases' is something only you could have written. Ask 'so what?' of every bullet you have. If there is no answer, rewrite it.

Second, put a number in every bullet. It does not have to be revenue. Requests handled per day, records processed, deploy time before and after, defects cut, test coverage added, incidents resolved, team size, services owned all work. If you genuinely have no number, describe the scale in concrete terms instead. 'A system used by 2 lakh users' or 'a service handling 40k requests per minute' both do the job. The free bullet rewriter will handle the rewriting if you give it one weak line to start from.

Keywords the screen matches on

Once the parser has pulled out your text, the match against the job description is mostly vocabulary overlap. It looks for the actual terms, and synonyms usually don't count. 'React.js' and 'ReactJS' match in some systems and not in others. The posting says 'stakeholder management'. Your resume says 'worked with internal and external teams', and scores zero for it.

So state every genuine skill you have in the words the posting uses, once, in context. Repeating a keyword twenty times trips a separate filter and reads as spam to the person who eventually opens your file. Go through the posting requirement by requirement, and for each one ask whether your resume states that thing in the posting's own words. If a requirement is missing from your resume, you are missing it in the screen as well. The free ATS score checker finds these gaps in seconds by parsing your resume against the same posting.

Tailoring to one posting without rewriting the whole thing

Most candidates try to rewrite the whole resume from scratch for every application. That produces a flat document that sounds like nobody and reads as quickly as it was written. Keep one base resume instead, and rewrite two bullets per application: the summary line and the first bullet of your lead project.

Rewrite the summary to match the role's level and specialisation. Rewrite the lead project's first bullet so it describes the same outcome in the posting's vocabulary. Leave everything else as it is.

A resume tuned to no posting in particular does badly against all of them. A resume tuned to each of the three postings you actually care about will convert on those three. Spend ten minutes per application on those two bullets, and skip the applications you can't honestly tailor for.

What the parser drops that you did not realise

A parser reads text and ignores pictures. These formatting choices quietly lose you information.

Two-column layouts. The parser reads left to right across the full page width, so your sidebar skills get interleaved with your job history and both turn into nonsense.
Tables and text boxes. A skills matrix inside a table often comes out as one run-on line, or gets dropped altogether. Write your skills as a grouped list instead.
Text inside images or icons. Contact details sitting in a header graphic are invisible to the parser. Put them in plain text.
Headers and footers. Many parsers skip them entirely, so never put your phone number or email there.
Non-standard section names, like 'My Journey' instead of 'Work Experience' or 'Toolbox' instead of 'Skills'. The parser looks for the standard headings, so give it the standard headings.

The HR round hand-off

Your resume gets you the interview and the interview gets you the offer. In India that interview is usually two rounds: a technical round on the work you described, and an HR round covering your notice period, expected CTC, why you are leaving your current role, and any gap you took between jobs. Both need practice, and both go better if your resume is honest about the work it describes.

The technical round follows your bullets. If you claimed a 38% reduction in payment failures, you will be asked how you did it. If you can't explain that rewrite in the room, the bullet turns into a liability. Put down only what you can defend.

The HR round is where most candidates lose. The expected CTC question, the notice period question, the move from a service-based company to a product company, a career gap, a gap after a layoff: each of these has a good answer, and the good answer is one you have rehearsed. The mock interview covers the HR round specifically, and that is the place to practise before the real call.

Putting it together, in order

Start with one real job posting you actually want. Strip your resume down to a single column with standard headings. Drop the photo, the declaration, the objective, and the Class 10 and 12 marks if you already have a degree. Group your skills by category. Rewrite every bullet so it survives the 'so what?' test and carries a number. Then score the result against the posting with the free ATS score checker. The parse and the keyword match will tell you what is missing in seconds.

After that, spend forty minutes rewriting the summary line and the lead project's first bullet in the posting's vocabulary. Save that as a tailored version and move on to the next posting.

That is the whole resume in 2026: standard structure, bullets with numbers in them, tailoring to the posting's vocabulary, ATS-safe formatting, and an honest hand-off to the interview round that follows.

What to use, by step

These free tools cover the mechanical work end to end. Run them in this order, because each one feeds the next.

ATS score checker: paste your resume and the posting, and get the keyword match, the missing sections and the formatting the parser will trip on. Use this first, to find the gaps before you rewrite anything.
Bullet point rewriter: feed it one weak line and get back a rewrite with a number in it, in the posting's vocabulary. Use it on every bullet that fails the 'so what?' test.
Free resume review: once the whole draft is ready, get line-by-line feedback on what works and what is quietly costing you interview calls.
Cover letter generator: for the postings that ask for one, write it from the same resume and posting so your language stays consistent across both.
Mock interview: for the HR round that follows a shortlist. Practise the expected CTC question, the notice period answer, the service-based to product company move, and your career gap explanation before the call.

Put it into practice

Score your resume against a real posting with the free ATS score checker, or rehearse the HR round against an AI interviewer that asks the follow-ups.

Get Started Free