Blogs
Blogs
Article
Your resume is probably being read by software before a human ever sees it — here is how to build one that survives the filter and reaches a recruiter.
You spend an entire evening making your resume look beautiful. Two columns, a soft blue sidebar, a small photo in the corner, little skill bars that fill up to show you are "80% good at Excel". You export it as a PDF, upload it to a listing on Naukri, and wait. Days pass. Nothing. You assume the market is bad or you are not qualified. Often, neither is true. A piece of software read your resume, could not make sense of the layout, and quietly filed you away before a single recruiter opened it.
That software is called an Applicant Tracking System, and in India it now sits between you and almost every mid-to-large employer. IT services firms, product companies, banks, staffing consultancies that recruit for dozens of clients at once — they all use it to handle the flood of applications a single opening attracts. When a job on LinkedIn or foundit shows "500+ applicants", no team is reading them by hand. They are searching and ranking by machine first.
The good news is that beating an ATS is not a trick or a hack. It is mostly about respecting how the machine reads, then writing content strong enough to convince the human on the other side. This guide covers both — what an ATS does, why fancy templates sabotage you, the exact structure to use, how to work keywords in honestly, and how to write bullets that carry weight even if you have never held a full-time job. There are India-specific examples throughout, plus the norms that are genuinely different here.
An Applicant Tracking System is database software that collects, stores, and organises job applications for an employer. When you upload your resume, the ATS tries to parse it — to pull your name, contact details, work history, skills, and education out of your document and drop each piece into the right field in its database. A recruiter then searches that database the way you search Flipkart: by keywords, filters, and location.
Here is the part most people get wrong. The ATS is usually not "auto-rejecting" you with a secret score out of 100. That myth causes real damage, because people start writing for a robot instead of a person. What actually happens is simpler: if the software parses your resume badly, your details land in the wrong fields or go missing. So when a recruiter searches for "React developer Pune", your resume does not surface — not because you were rejected, but because the system does not know you match. You were never in the running.
So there are two battles. The first is parsing: making sure the machine reads your resume cleanly. The second is searchability: making sure the right words are present so a recruiter's search finds you. A good resume wins both without ever looking like it was written for a machine.
Large IT and services companies run ATS platforms because they receive lakhs of applications a year. Product startups past a certain size use them too. But the heaviest users you will meet as a fresher are recruitment consultancies and staffing agencies. A single consultant may be filling roles for fifteen client companies at once, living inside the ATS search bar all day, typing skill keywords and shortlisting whoever comes up. If your resume is not machine-readable and keyword-honest, you are invisible to exactly the people whose full-time job is to find candidates.
Walk through any resume template site and you will see gorgeous designs. Most of them are quietly hostile to ATS parsing. Here is what breaks, and why.
Two-column layouts. This is the single biggest killer. Your eye reads a two-column resume in a sensible order, but many parsers read straight across the page, left to right, line by line. So a skill from the sidebar gets stitched onto a sentence from your job description, and the result is scrambled nonsense the machine cannot categorise. Keep everything in one single column, top to bottom.
Tables. People use tables to line up dates neatly, or to make a tidy skills grid. Parsers frequently read table cells out of order or drop them. Never put real content inside a table.
Text boxes, graphics, and skill bars. A text box is a floating object, not part of the normal text flow, so its contents often vanish during parsing. Those "80% Python" progress bars communicate nothing anyway — 80% of what? — and the machine cannot read them.
Photos and logos in the header. A photo is an image; the ATS extracts no text from it. Worse, if you put your name or contact details inside a header or footer region, some parsers ignore that region entirely and your resume ends up with no name attached. The same goes for decorative fonts and icons used in place of words — a little envelope instead of "Email" turns into a blank.
The uncomfortable truth: the more a template tries to impress you visually, the more likely it is to fail the one reader that matters first. A plain, clean, single-column resume is not boring — it is professional, and it works.
Use this order. It matches what parsers expect and what Indian recruiters scan for.
Not every section is mandatory. An experienced candidate may drop the projects section and lead with work. A fresher should absolutely keep projects. What matters is that each section carries a standard, obvious title. Which brings us to the next point.
These are not suggestions. Follow them and your parsing problems mostly disappear.
Both are usually fine with modern parsers, but there is a safe default. If the form or job post specifies a format, obey it exactly. Otherwise, if you built your resume in Microsoft Word, a .docx file is the most reliably parsed choice across older systems. If you want a PDF — often better for preserving layout when a human opens it — make sure it is a real text PDF, not a scanned image or a design export where the text is actually a picture. Test it: open the PDF and try to select and copy a line. If you can highlight it as text, a parser can read it. If nothing selects, it is an image and the ATS sees a blank page.
Recruiters download dozens of files into one folder, where "Resume final FINAL v3.pdf" is invisible. Name yours: Firstname_Lastname_Role.pdf — for example "Ananya_Rao_DataAnalyst.pdf". It helps the human, and it signals you pay attention to detail.
Recruiters search the ATS using words from the job description. So your job is to make sure the genuine skills you have appear on your resume using the same words the employer used — because "MS Excel", "Advanced Excel", and "spreadsheets" are three different search terms, and you want to match the one they actually type.
Here is a clean method:
The line you must not cross is keyword stuffing — pasting a wall of skills you do not have, hiding white keywords, or repeating a term twenty times. Recruiters spot it instantly and it reads as dishonest. A resume listing "Machine Learning, Deep Learning, NLP, TensorFlow, PyTorch, Keras" from someone who watched one Coursera video fools no one. Tailor honestly: change the emphasis and wording per application, keep the substance true.
Most resumes are full of duties, not achievements. "Responsible for handling social media" tells a recruiter nothing. The fix is a simple pattern: strong action verb + what you did + the result, with a number wherever possible.
You do not need corporate experience to quantify. Freshers have numbers everywhere — they just do not think to use them. How many people used your project? How many days did a task take before and after you improved it? What rank, what percentage, how many members in the team you led?
Look at the difference.
Weak: "Made a website for our college event."
Strong: "Built the registration website for our college tech fest using React and Firebase, handling 1,200+ sign-ups over three days with zero downtime."
Weak: "Did a marketing internship and helped with Instagram."
Strong: "Grew the startup's Instagram following from 800 to 3,400 in eight weeks by planning a daily reel calendar and running two collaboration campaigns."
Weak: "Good at Excel and data."
Strong: "Cleaned and analysed a 10,000-row sales dataset in Excel, building a pivot-based dashboard that cut the weekly reporting time from four hours to thirty minutes."
See the shape. Verb, action, tool, number, outcome. Even when you estimate, be honest: "1,200+ sign-ups" is fine if the real figure was around that. Inventing "increased revenue by 300%" for a college project is not.
Picture Priya, a 2026 B.Com graduate from Pune targeting a financial analyst role. Her resume is one page, single column, Calibri 11, black text on white.
At the top: her name in slightly larger bold text, then one line — "Pune, Maharashtra | +91 [number] | priya.[surname]@gmail.com | linkedin.com/in/priya[surname]".
Then a four-line summary naming her strengths in Advanced Excel and financial modelling, her CA-firm internship, and the analyst role she wants. Then Key Skills: Advanced Excel, Financial Modelling, Tally ERP 9, Power BI, Financial Statement Analysis, SQL (basics).
Then Experience: her three-month CA-firm internship, with two bullets — one on reconciling 200+ vendor invoices monthly and cutting errors, one on an Excel tracker the team still uses. Then Projects: an equity-research report on two listed FMCG companies, and a Power BI budgeting dashboard, each with a bullet naming the tools and output. Then Education: B.Com, college and university, 2026, with her percentage, and Class 12 below it. Then Certifications: a genuine financial-modelling course and her NISM certification.
No photo. No date of birth. No "Declaration" line. No marital status. It parses cleanly, every keyword a recruiter would search is present and true, and a human reading it in ten seconds understands exactly what she offers. That is the whole game.
If you have two or more years of real work, the balance shifts. Your experience section leads, right after the summary, and it should be the longest part of the resume. Projects and college activities shrink or disappear. Your bullets move from "what I learned" to "what I delivered and owned" — scope, scale, money, people, and outcomes. It is acceptable, sometimes expected, to run to two pages once you have several years of substance, though never pad to fill space.
Your summary becomes a positioning statement: "Digital marketing specialist with 4 years across two SaaS firms, owning paid-search budgets up to 8 lakh per month and improving lead cost by 22%." Move education below experience — nobody hiring a four-year professional cares about your Class 12 marks. And your skills list should reflect depth, not everything you have ever touched.
This is where generic international advice gets you into trouble, because India genuinely has two different sets of expectations.
Modern private-sector and MNC roles. Follow global best practice. Do not include a photo, date of birth, marital status, father's name, religion, caste, or a "Declaration" signature line. These are outdated on a private-sector resume, they add nothing a recruiter can use, and a photo can even invite bias. Keep the resume about your skills and results. This applies to almost all IT, startup, corporate, and consultancy applications you will make.
Government, PSU, and some traditional roles. Here the rules invert. Many public-sector applications go through official forms that require your photograph, date of birth, category, father's or mother's name, and other personal fields, often with a signed declaration. If you are applying through such a portal, provide exactly what the form asks for, in the format specified. Treat it as a separate document from your private-sector resume.
The mistake to avoid is mixing them: sending a photo-and-DOB government-style resume to a product startup, or a minimalist skills resume where an official form demands specific personal fields. Match the resume to the destination.
A few more local notes: expected salary rarely belongs on the resume; discuss it when asked. References are offered on request, not listed. And keep your email professional — "coolboy_pune@" undercuts everything above it.
Do these in order this week and your resume will be in the top slice that both the machine and the recruiter actually see.
Get the format right so the machine can read you, then write content honest and specific enough to make the human want to call. Do both, and the silence you have been getting starts turning into interviews.