For every campus placement job at a top Indian company, recruiters see 200–500 resumes. Most are eliminated in the first 30 seconds — not because the candidates weren't qualified, but because the resume failed to communicate it. Here's what actually gets you shortlisted in 2026.
The Single-Page Rule (and When to Break It)
For freshers with under 2 years of experience: one page, always. No exceptions.
Why: Recruiters at high-volume campuses spend an average of 6 seconds per resume. Anything beyond page 1 rarely gets read. Two-page resumes from freshers signal inability to prioritise — itself a negative signal.
The only exception: if you have exceptional projects, publications, or research, an Appendix-style second page is acceptable at IIT/NIT-level campus drives for FAANG. Service company recruiters won't read it.
ATS Optimisation — What Indian Companies Actually Use
ATS (Applicant Tracking System) filters resumes before a human sees them. In India:
Service companies (TCS, Infosys, Wipro): Most use internal ATS that filters by exact keyword match, degree type, and CGPA threshold. Use the same technology terms as the job description.
Product companies (Flipkart, Swiggy, CRED): Mix of Greenhouse, Lever, and proprietary tools. Keyword matching on tech stack + experience level.
FAAN/FAANG recruiters: Often manually sourced from LinkedIn or referrals — ATS matters less, content quality matters more.
ATS rules that work everywhere:
• Use standard section headers: Work Experience, Education, Projects, Skills
• No tables, columns, or text boxes — ATS often can't parse them
• Save as PDF, named: FirstName-LastName-Resume.pdf
• Use the exact skill names from the job description (Java, not 'programming languages')
The Projects Section — The Most Important Part for Freshers
The projects section IS your work experience as a fresher. It needs to be treated accordingly.
Bad project description:
'Built a food delivery app using React and Node.js.'
Good project description:
'Built a full-stack food delivery app (React, Node.js, MongoDB) handling 50+ concurrent users. Implemented JWT auth, order state machine, and real-time delivery tracking with Socket.io. GitHub: [link] | Live: [link]'
Formula for every project:
[What it does] + [Key tech used] + [Scale/measurable outcome] + [Links]
If your project doesn't have a GitHub link, create one. Recruiters at product companies check.
The Skills Section — Don't Lie, Don't Be Vague
Common mistakes:
× 'Proficient in: Java, Python, C++, JavaScript, React, Angular, Vue, Machine Learning, NLP, Blockchain' — lists everything, signals nothing
× 'Familiar with Java' — too vague; just list it or don't
× Listing tools you can't discuss in an interview
The right approach:
Group by category:
Languages: Java (primary), Python
Frameworks: Spring Boot, React
Databases: MySQL, MongoDB
Tools: Git, Docker, Postman
Cloud: AWS basics (EC2, S3)
Only list skills you can discuss for 3+ minutes if asked. Listing them and blanking in the interview is worse than not listing them.
CGPA and Academics — The Real Cutoff Situation
What recruiters actually need:
TCS: 60% throughout (equivalent to ~6.0 CGPA). Wipro/Infosys: similar. Product companies vary — some have no filter, some have 7.0 CGPA.
If your CGPA is below the threshold:
• Apply off-campus where filters aren't enforced
• Lead with your projects/skills section — put it above Education
• Target companies that explicitly don't have CGPA requirements (Zoho, many startups)
• Get referrals — referral resumes often bypass ATS filters
If your CGPA is above 8.5: put it prominently. It's a positive signal at high-volume drives where 70% of candidates are 6.5–7.5.
Frequently asked questions
Ready to practice?
After building your resume, practice explaining your projects and experience in mock interviews on HireStepX — the gap between resume and interview is where most candidates lose.
Start free practice
