An ATS-friendly resume for an IT job is a plain, single-column document with standard section headings, your contact details in the body, and the exact skills from the job description written out where you actually used them. Fancy templates with columns, icons and skill bars look good to people but often scramble when software reads them, and a scrambled resume is hard for a recruiter to find.

Most large employers in India, from IT services firms to product companies and global capability centres, use an applicant tracking system (ATS) to store, search and filter applications. Here is how to make sure yours is read correctly and shows up in searches.

What an ATS actually does with your resume

When you apply, the ATS extracts the text from your file and tries to sort it into fields: name, phone, email, employers, job titles, dates, skills and education. Recruiters then search that database with keywords such as “Spring Boot”, “Terraform” or “Azure”, and filter by experience, location or notice period.

Two things decide whether you appear in those searches:

  1. Parsing: the system must be able to read your text in the right order and put it in the right fields.
  2. Matching: the words a recruiter searches for must be in your resume.

Most systems do not automatically reject people; a recruiter usually runs the search. But a resume that parses badly or lacks the right terms simply does not come up, which has the same effect.

Layout rules that keep your resume readable

DoAvoid
One column, top to bottomTwo- or three-column templates that can be read across instead of down
Standard headings: Summary, Skills, Experience, Projects, Education, CertificationsCreative headings like “My Journey” or “What I Bring”
Contact details as normal text near the topContact details only in the page header or footer
Common fonts such as Arial or Calibri at 10-12 ptDecorative fonts, icons for phone and email, skill-level bars or star ratings
Normal round bulletsText boxes, tables and images carrying important information
A text-based .docx or PDF, in the format the portal asks forA scanned resume or a photo of a printed page

ATS vendors say much the same. Greenhouse’s support pages list multi-column layouts, graphics and photos, contact details in a header, footer or text box, abbreviated job titles such as “Sr. Account Exec”, and files over 2.5 MB as common reasons a resume fails to parse. Workday’s documentation notes that image-based resumes give weaker results and that text-based files work best.

A quick test: open your PDF, select all the text and paste it into a plain text editor. If the order is jumbled, words are missing or your phone number has vanished, an ATS will probably have the same problem.

A structure that works for most IT roles

  1. Header: name, phone, email, city, LinkedIn URL, and GitHub or portfolio if it has real work in it.
  2. Summary: two or three lines with your role, years of experience and core stack. For example: “Backend engineer with 5 years in Java and Spring Boot, building payment APIs on AWS for a fintech product.”
  3. Skills: grouped by type, for example Languages, Frameworks, Cloud, Databases, DevOps and Tools.
  4. Experience: most recent first, with company, title, location and dates (month and year) on one line, then three to six achievement bullets.
  5. Projects: essential for freshers and career switchers; list the stack, what you built and a link.
  6. Certifications and education: name, issuer and year. Leave out school marks unless the employer asks for them.

Getting keywords right without stuffing

Read the job description and list the tools, languages and practices it repeats. For each one you genuinely have, make sure it appears in your Skills section and in at least one experience bullet that shows how you used it.

  • Use the employer’s spelling: if they write “Kubernetes”, do not rely on “K8s” alone.
  • Write both the full term and the abbreviation once: “Amazon Web Services (AWS)”, “Continuous Integration/Continuous Deployment (CI/CD)”.
  • Match the job title where it is honest. If your title was “Member of Technical Staff” but the work was backend development, write “Member of Technical Staff (Backend Developer)”.
  • Tailor the Summary and top bullets for each application; you do not need to rewrite the whole resume.

Never list skills you do not have. Technical interviewers ask about everything on the page, and background verification teams compare your resume with employer records. For what gets checked, see our guide to background verification in Indian IT companies.

Write achievements, not duties

Compare two versions of the same bullet:

  • Weak: Responsible for deployments on AWS.
  • Strong: Automated deployments for 12 microservices on AWS using GitHub Actions and Terraform, cutting release time from two days to two hours.

The second contains the keywords (AWS, GitHub Actions, Terraform, microservices), the scale and the result. A simple formula: action verb + what you did + tools used + measurable result. If you do not have an exact figure, use an honest approximation you can explain in an interview, such as “about 30%”.

A fresher can apply the same idea to projects: “Built a library management app in React and Node.js with JWT login and a PostgreSQL database; deployed on Render; 40 users from my college tested it.”

Length and personal details

One page is usually enough for freshers and people with up to about five years of experience. Two pages are fine for experienced professionals. Cut old or irrelevant roles rather than shrinking the font.

Many Indian resumes still include date of birth, marital status, religion, father’s name, a photo and a full home address. None of this is needed for most IT roles; it takes space and shares personal data with everyone who downloads your file. City and phone are enough. Give the rest only if an employer asks for it during onboarding. Under India’s privacy law you can also ask job portals to delete your data once you stop using them; see our DPDP Act explainer.

Mistakes that get resumes skipped

  • Skills hidden in a sidebar or graphic that the ATS cannot read.
  • Dates in mixed formats (“Jan 22”, “2023-05”, “Present”) that confuse experience calculations; pick one style such as “Jan 2022 – Mar 2024”.
  • A long list of every technology you have touched, with no evidence in the experience section.
  • Different job titles or dates on your resume and LinkedIn profile.
  • A file named resume_final_v3.pdf. Use FirstName_LastName_Role.pdf.

Checklist before you apply

  • Single column, standard headings, no key information in images, tables or headers
  • Plain-text paste test passed
  • Top five skills from the job description present and backed by bullets
  • Achievements with numbers in your most recent role
  • Consistent dates, and gaps of more than a few months explained in one line
  • LinkedIn profile matches your resume; our LinkedIn profile tips for IT professionals cover this
  • Proofread, then ask someone else to proofread

FAQ

PDF or Word?

Use whatever the portal asks for. If it accepts both, a text-based PDF made from Word or Google Docs is usually fine for modern systems; some older systems handle .docx more reliably. Run the paste test either way.

Do ATS resume score tools help?

They can point out missing keywords, but each tool uses its own scoring, not the employer’s. Treat the score as a hint, not a target.

Sources


Last reviewed: 9 October 2026.

Leave a Reply

Trending