Your Resume Is Getting Rejected Before Anyone Reads It — Here's Why

A friend of mine — sharp engineer, three solid years at a mid-size startup — applied to 60 companies over two months. Got four callbacks. He was convinced something was wrong with him.

Nothing was wrong with him. His resume was wrong.

He had a beautiful two-column template he'd downloaded off Canva. Colours, icons, a photo. It looked great as a PDF. The problem? Every company he applied to was running his resume through an ATS — Applicant Tracking Software — before any human touched it. And that software was reading his fancy resume as a garbled mess and quietly throwing it out.

What ATS actually does

Companies like Swiggy, Razorpay, Infosys, Zomato — basically any company that receives more than 200 applications for a role — use ATS to handle the flood. The software parses your resume into plain text, extracts your name, email, experience, skills, and then scores you against the job description. If your score is below a threshold, you're out. A recruiter never sees you.

This isn't new. But what has changed is how aggressive the filtering has gotten. In 2024-25, applications per role in India jumped significantly — partly because LinkedIn and Naukri made applying easier, partly because more people started applying remotely to cities they don't live in. More applications means stricter filters.

The mistakes that get you filtered out

The most common one is the template problem. Two-column resumes, tables, text boxes — ATS parsers read left-to-right, top-to-bottom. A table with your experience in one column and your skills in another gets read as a jumbled string of words. The parser can't figure out what's a job title and what's a skill. Your ten years of experience essentially disappears.

The second mistake is what I call skill translation failure. If the job description says "React.js" and your resume says "ReactJS", some parsers won't match them. Sounds absurd, but it happens. Same with "Node.js" vs "NodeJS", or "PostgreSQL" vs "Postgres". Use the exact spelling the JD uses.

Third — and this surprises people — is generic job titles. If your actual title was "Module Lead" at your company but the industry standard is "Senior Software Engineer", consider using the standard one (or both: "Senior Software Engineer / Module Lead"). ATS searches by title keywords.

What actually works

Single column, clean format. Arial or Calibri, 10-11pt, standard margins. No photos (most MNCs and product companies don't want them anyway). No tables. No text boxes. Section headings in plain text — not styled boxes.

For each job you apply to, spend 5 minutes reading the JD and make sure your skills section includes the exact terms they used. You don't need to rewrite your whole resume. Just make sure the language matches.

And add numbers wherever you can. Not because ATS specifically scores on this (it doesn't always), but because when your resume does get to a human, "increased user retention by 28%" lands very differently than "worked on improving user retention". The ATS gets you through the door. The numbers get you the interview.

One more thing

I know it's tempting to use a template that looks impressive. Design matters, eventually — when someone's actually reading your resume. But they only read it if the machine lets it through first. Get through the machine first. The best-looking resume that gets filtered out is worth exactly nothing.

Upload your resume to Uplio's free ATS scorer and you'll see exactly what's holding your score down — missing keywords, formatting issues, weak sections. Takes 30 seconds.