How your resume is actually screened
Before a person reads your resume, software turns it into plain text. If that text is scrambled, you are rejected by a search you never see.
The path your resume takes
| Step | What happens | What kills you here |
|---|---|---|
| 1. You apply | Naukri, LinkedIn, Instahyre, or the company’s careers page stores your file. | Nothing yet. |
| 2. The ATS parses it | An applicant tracking system converts your PDF into plain text and tries to split it into sections: contact, skills, projects, education. | Two columns, Canva templates, text inside images, icons instead of words. The parser gets scrambled text or nothing. |
| 3. A recruiter searches | They filter by keywords (“React”, “TypeScript”, “Next.js”), location, and year of passing. | The keyword isn’t in your text, or it’s spelled differently (“React js”, “Nextjs”). |
| 4. A 30-second skim | The recruiter opens the few resumes that matched and scans the title, links, and project names. | A generic summary, no live links, projects described as feature lists. |
| 5. The hiring manager | An engineer clicks your GitHub and live demo and reads one project in detail. | Dead links, default READMEs, claims you can’t explain in the interview. |
Most freshers only think about step 5. Most freshers are rejected at steps 2 and 3, where a clean, boring, single-column resume beats a beautiful one every time.
What a parser really sees
A PDF doesn’t store “sections”. It stores text fragments with positions. A parser reads those fragments in the order they were written into the file, which is not always the order you see on screen. Designer templates often write the left column first, then the right, or place headings and text in separate layers.
This is what a parser read from a real Canva resume (project names changed):
SUMMARYTaskflow – Project Management System Grocery Marketplace App Developed a full-stack multi-vendor grocery marketplace using Next.js ... Implemented role-based authentication for customers, sellers ... MCA graduate and Full Stack Developer passionate about building ...
The heading “SUMMARY” is glued to a project title, and the project bullets land under Summary. The actual summary appears much later. A recruiter searching the Projects section finds nothing, and the bullets drawn as shapes never reach the parser at all.
Upload your current PDF to the ATS check. It shows you the exact text a parser extracts, in the order it reads it. If it looks scrambled there, it looks scrambled to recruiters.
What the human skim looks for
- Target title under your name. “Full-Stack Developer (Next.js, TypeScript, PostgreSQL)” tells them where you fit before they read anything else.
- Live links. A deployed app is the strongest proof a fresher can show. Recruiters click live apps, not source code.
- Project names and the first bullet. They read one bullet, maybe two. Make the first one the hardest thing you built.
- Year of passing and location. Services companies filter on this. Startups glance at it.
The takeaway
Your resume has two readers: a parser that needs plain, ordered text, and a tired human who needs proof in 30 seconds. Everything else in this guide serves one of those two.