Resume Tips for Freshers India 2026: What Gets Shortlisted

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 (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 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 fails in two opposite directions. The first is the "kitchen sink" list: Java, Python, C++, JavaScript, React, Angular, Vue, Machine Learning, NLP, Blockchain: which signals either that you've listed every word from every tutorial you've touched, or that you genuinely don't know what your strengths are. Either way, recruiters stop reading it. The second failure is the hedge: "Familiar with Java." Just list it or don't. Hedging wastes space and reads as insecure.

The right approach is to group by category and be honest about depth. Something like: Languages: Java (primary), Python. Frameworks: Spring Boot, React. Databases: MySQL, MongoDB. Tools: Git, Docker, Postman. Cloud: AWS basics (EC2, S3). This takes 5 lines and tells the interviewer exactly where to start a technical question.

The rule that actually matters: only list a skill if you can talk about it for 3 minutes without stalling. If you listed Docker because you ran one tutorial command and never touched it again, take it off. An interviewer who asks "walk me through your Docker setup" and gets a blank stare loses confidence in everything else on the page: not just Docker.

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.

Indian fresher resumes are notorious for using weak filler verbs that drain impact from otherwise solid experiences. The most overused words in Indian fresher resumes are participated, involved in, assisted, supported, helped, and worked on, all of which signal passive contribution rather than ownership. Replace these with verbs that show initiative and result: built, designed, reduced, increased, automated, deployed, led, optimized, migrated, and implemented. For project descriptions specifically, start with the outcome verb rather than the task verb: instead of 'worked on building a student portal that improved login speed' write 'reduced student portal login time by 60 percent by rebuilding the authentication module using JWT'. The specific metric in the opening clause forces the reader to engage before they can dismiss the entry.

For product company applications in India in 2026, a well-maintained GitHub profile can be as important as the resume itself, especially for candidates from tier-2 and tier-3 colleges where brand recognition alone does not open doors. A GitHub profile that supports a resume should show consistent contribution history rather than a single burst of activity before placement season, have a descriptive README on each significant project explaining the problem it solves and the technical decisions made, and contain at least one project with more than 50 commits demonstrating sustained development over time rather than a weekend build. Recruiters and technical screeners at companies like Razorpay, Zerodha, and Groww explicitly ask candidates to share GitHub links, and a sparse or dormant profile when one is mentioned on the resume is a negative signal.