How to Write an ATS-Friendly Résumé as a Fresher in India (With a Checklist)
What applicant tracking systems do with your résumé, the formatting that parses cleanly, how to match job-description keywords honestly, and a checklist with before/after examples for B.Tech and B.Com/BBA freshers in India.

You found a job that fits, hit "Apply"… and heard nothing. Before you blame your CGPA or your college, check something simpler: can the software that received your résumé actually read it?
Most large companies, and many startups, collect applications through an applicant tracking system (ATS) such as Workday, Greenhouse or Lever. This guide covers what an ATS does with your file, how to format a fresher résumé so it reads cleanly, how to match keywords honestly, and the mistakes Indian freshers make most often, with a checklist and before/after examples at the end.
What an ATS actually does with your résumé
An ATS is the hiring team's database. When you upload your résumé, it parses it: it pulls out your name, contact details, education, job titles and skills into a candidate profile. Recruiters then search and filter that database, like filtering products on a shopping site.
How common is it? Jobscan's 2026 ATS Usage Report detected an ATS on the careers sites of 97.4% of Fortune 500 companies (487 of 500). Many of those companies hire in India through the same portals.
And recruiters really do search. In Jobscan's State of the Job Search 2025 survey of 384 recruiters, 99.7% said they use filters in their ATS or a similar system to find candidates to interview. The most common filters were skills (76.4%), education (59.7%) and job title (55.3%). If your skills are hidden in an image or a sidebar the parser can't read, you simply won't show up in those searches.
About that "75% of résumés are rejected by ATS" stat
You've probably seen the claim that 75% of résumés are auto-rejected before a human sees them. We couldn't verify it, and neither could people who traced it. OfferMic's investigation found the oldest versions date to 2012 articles crediting Preptel, a company that sold résumé-optimisation software and closed in 2013, with no published method or data behind the number.
The honest picture: automatic rejection usually comes from knockout questions the employer sets (graduation year, location, work authorisation). A badly formatted résumé is more often misread than deleted, leaving a half-empty or jumbled profile that a busy recruiter is unlikely to fix by hand. So the goal isn't to "beat the bot". It's to make sure it copies your details correctly so a human can find you.
Formatting: what parsers read well (and what breaks them)
Greenhouse, one of the most widely used ATS platforms, publishes a support page on why a résumé fails to parse. It reads like a description of popular Canva templates: graphics, photos or word art; résumés uploaded as images; tables, headers and footers; contact details in a header, footer or text box; columned layouts; unclear sections; and files over 2.5 MB.
Indeed's guidance on ATS-friendly résumés lines up with this. Here's the short version:
Do
- Use a single column, top to bottom. It is the one change that fixes the most parsing problems.
- Use standard section headings: Summary, Education, Skills, Projects, Internships (or Experience), Certifications, Achievements. Creative headings like "My Journey" or "What I Bring" confuse parsers.
- Use common fonts such as Arial, Calibri or Times New Roman, at 10–12 pt for body text.
- Use simple round bullets or hyphens. Skip icons, emojis and decorative symbols.
- Put your contact details in the main body, on the first two lines, as plain text: name, phone with +91, a professional email, city, and your LinkedIn and GitHub/portfolio links.
- Put dates on the same line as the role, for example "Data Analyst Intern, XYZ Pvt Ltd | Jun 2026 – Aug 2026".
Don't
- Two-column templates with a sidebar. The sidebar (often your skills) can get mixed into the middle of your projects, or read in the wrong order.
- Tables for layout. Dates in one cell and roles in another can get separated from each other.
- Skill bars, star ratings and pie charts. "Python ●●●●○" means nothing to a parser, and a recruiter can't tell what four dots means either. Just list the skill.
- Scanned or photographed résumés. An image has no text for the parser to read.
- Spaced-out letters like "R E S U M E" or "S K I L L S". Greenhouse specifically calls this out: the parser can't join the letters back into a word.
PDF or DOCX?
Follow the job posting first. If the portal asks for a specific format, use it. Otherwise, a text-based PDF exported from Word or Google Docs is usually the safest choice: Indeed India describes PDF as a widely accepted format that keeps your layout intact, while noting that some systems ask for .doc or .docx.
The file extension matters less than what's inside it. In a small controlled test by Jobsistant (10 files, two open-source text extractors, not a real employer ATS), simple single-column résumés gave back every tracked detail in both PDF and DOCX, two-column layouts came back in the wrong order in both formats, and image-only scans returned no text at all. Two quick checks:
- Open your PDF, press Ctrl+A and copy everything into Notepad. If the text comes out in the right order, a parser will probably read it in that order too.
- Keep the file small and name it Firstname_Lastname_Resume.pdf, not "final_final_v3.pdf".
Keywords: match the job description honestly
Since recruiters filter by skills and job title, the words on your résumé should mirror the words in the job description. Indeed India recommends picking out role-specific terms that repeat in the posting and including them naturally, without overusing them. A simple 10-minute routine:
- Copy the job description into a doc and highlight every tool, skill and qualification (for example SQL, Excel, React, Tally, GST, customer support, stakeholder communication).
- Mark the ones you genuinely have. Never add a skill you can't be questioned on.
- Use the exact wording. If the posting says "Microsoft Excel" and "data visualisation", don't only write "spreadsheets" and "charts". Include both the full form and the short form where it helps, for example "Machine Learning (ML)".
- Put keywords where they carry proof: in project and internship bullets, not just in the skills list. "Built a sales dashboard in Power BI using SQL queries on 2 years of store data" counts for more than "Power BI, SQL" alone.
- Match the job title in your summary line, for example "Final-year B.Tech CSE student seeking a Software Engineer role".
Don't keyword-stuff. Hiding the job description in white text might get past a filter, but it fails the human read. Ladders' 2018 eye-tracking study found recruiters spent an average of 7.4 seconds on the initial screen, and listed keyword stuffing, clutter and multiple columns among the traits of the worst-performing résumés.
The best section order for a fresher
With little or no work experience, lead with what proves you can do the job. For most Indian freshers that order is:
- Contact details: name, +91 phone, email, city, LinkedIn, GitHub or portfolio.
- Summary (2 lines): target role + your strongest 2–3 skills + one proof point. This replaces the old "career objective".
- Education: degree, college, graduation year, CGPA or percentage. Add Class 12 and Class 10 only if the employer asks, or if they're strong and you have little else.
- Skills: grouped, for example Languages / Tools / Concepts for tech, or Accounting / Tools / Communication for commerce roles.
- Projects: 2–3 real projects with what you built, the tools used and one outcome. Add a link.
- Internships / Experience: move this above Projects if it's directly relevant to the role.
- Certifications and Achievements: hackathons, competitions, scholarships, club leadership.
Keep it to one page.
Common fresher mistakes (especially in India)
- A photo, date of birth, marital status, religion or father's name. Unless the employer specifically asks (some government or PSU forms do, and they'll ask in the form itself), leave them out. Naukri Campus advises freshers to skip the photo unless it's explicitly required and to avoid personal details like marital status. Photos also add file size and are one of the elements Greenhouse lists as a cause of parsing issues.
- A generic objective. "Seeking a challenging position in a reputed organisation to utilise my skills" says nothing. Write a two-line summary aimed at the role instead.
- Messy CGPA formatting. Write it the same way everywhere, with the scale: "CGPA: 8.4/10". If a posting asks for a percentage, use the conversion your university officially specifies rather than guessing. Don't round up; it can be checked against your marksheet.
- A "Declaration" at the bottom. "I hereby declare…" takes space and adds nothing for a private-sector application.
- Duties instead of results. "Responsible for social media" vs "Ran the college fest's Instagram; grew followers from [X] to [Y]".
- One résumé for every job. Keep a master version and tweak the summary, skills and top bullets for each role.
Before and after: two fresher examples
These are illustrations. Replace the details with your own, and only use numbers you can back up.
B.Tech (CSE/IT) fresher applying for a backend developer role
Before
- Career Objective: To work in a reputed company where I can enhance my skills.
- Made a website for college project.
- Skills: C, C++, Java, Python, HTML, MS Office, Teamwork, Hardworking.
After
- Summary: Final-year B.Tech CSE student (CGPA 8.1/10) seeking a Backend Developer role; builds REST APIs with Node.js, Express and PostgreSQL.
- Built a hostel complaint-tracking web app (Node.js, Express, PostgreSQL, JWT auth) used by [number] students in my hostel; deployed on [platform]. GitHub: [link]
- Skills: Languages: JavaScript, Java, SQL | Backend: Node.js, Express, REST APIs | Databases: PostgreSQL, MongoDB | Tools: Git, Postman, Docker (basics)
B.Com / BBA fresher applying for an accounts or operations role
Before
- Objective: Hardworking and dedicated person looking for a job in a good company.
- Did internship at CA firm.
- Skills: MS Excel, Communication, Leadership.
After
- Summary: B.Com (2026) graduate seeking an Accounts Executive role; skilled in Tally Prime, GST return preparation and Microsoft Excel (VLOOKUP, pivot tables).
- Accounts Intern, [CA firm name] | May 2026 – Jul 2026: Recorded purchase and sales entries in Tally Prime for [number] small-business clients; helped prepare GSTR-1 and GSTR-3B filings; reconciled bank statements monthly.
- Skills: Accounting: Bookkeeping, GST, TDS basics, Bank Reconciliation | Tools: Tally Prime, Microsoft Excel, Google Sheets | Communication: client follow-ups in English and Hindi
The "after" versions name the target role, use the job's own keywords, and attach each skill to something real.
Your ATS-friendly résumé checklist
Run through this before every application:
- ☐ Single-column layout, no tables, text boxes, sidebars or skill bars
- ☐ Name, +91 phone, professional email, city, LinkedIn and GitHub/portfolio in the body (not the header)
- ☐ Standard headings: Summary, Education, Skills, Projects, Internships, Certifications
- ☐ Two-line summary that names the target job title
- ☐ Keywords from this job description used naturally in skills and bullets, and only ones you really have
- ☐ 2–3 projects or internships, each with tools used and one real outcome
- ☐ CGPA written consistently with its scale (e.g. 8.4/10)
- ☐ No photo, DOB, marital status or declaration unless the employer asks
- ☐ Dates on the same line as each role, in one consistent format (e.g. Jun 2026 – Aug 2026)
- ☐ Standard font, 10–12 pt, simple bullets
- ☐ One page, text-based PDF (or DOCX if the portal asks), named Firstname_Lastname_Resume
- ☐ Ctrl+A copy test passes: text pastes out in the right order
- ☐ Proofread once on screen and once out loud
Short on projects? Build one this week
The hardest part of a fresher résumé is often having something real to put under Projects. HireDoor's Productothon 01 is a free product-building event for students: problems drop on 30 October and the build week runs from 1 to 5 November. You come out with a real project, a team story and a link to put on your résumé.
Build it, then apply
Rather not fight with Word templates? The HireDoor résumé builder gives you a clean, single-column layout. Then pick a real role from HireDoor's freshers jobs or internships, tailor your résumé to it with the checklist above, and apply. When the call comes, the interview guide and our post on answering "Tell me about yourself" will help with what comes next.
Frequently asked questions
What is an ATS-friendly résumé?
It is a résumé that applicant tracking software can read correctly: a single-column layout, standard headings like Education, Skills and Projects, contact details in the main body, and plain text instead of images, tables or skill bars.
Is it true that 75% of résumés are rejected by ATS?
We could not find any study behind that figure. It traces back to 2012 marketing by a résumé-software company. Automatic rejections usually come from employer-set screening questions; poor formatting is more likely to leave your profile incomplete or jumbled.
Should I send my résumé as a PDF or DOCX?
Use whatever the job portal asks for. If it doesn't specify, a text-based PDF exported from Word or Google Docs is usually safe. Avoid scanned or image-only files, which contain no readable text.
Should freshers in India add a photo or date of birth to their résumé?
Not for most private-sector jobs. Leave out the photo, date of birth, marital status and declaration unless the employer or application form specifically asks for them.
How do I add keywords if I have no work experience?
Put the job description's skills and tools into your summary, skills section, project bullets and internship bullets, using the same wording as the posting. Only include skills you can genuinely discuss in an interview.
Browse by category
Published on hiredoor.in