Fresher Resume Tips India 2026: What Indian Recruiters Actually Look For

Five evaluation criteria in order of weight:

(1) ATS keyword match: most large Indian IT companies (TCS, Infosys, Wipro, Cognizant, Accenture, HCL) use ATS to filter by keywords from the job description. If your resume does not contain 'Core Java', 'Spring Boot', or 'REST API' when those appear in the JD, it may be filtered out before a human sees it. Fix: read the JD, identify the key technical terms, and include them verbatim in your skills section if you genuinely know them.

(2) CGPA cutoff: most Indian IT services companies enforce a 60% / 6.0 CGPA cutoff at the screening stage. Product companies and startups are less rigid but look harder at project quality to compensate. If your CGPA is below the cutoff, focus applications on companies known to care less (startups, companies with referral pathways).

(3) Project quality and specificity: this is the most differentiating factor for freshers. A strong project entry describes: what you built (product, not tech stack), what specific technical challenge you solved, what the outcome was (number of users, performance metric, accuracy %). A weak project entry says 'Built a web app using React and Node.js.' A strong entry says 'Built a real-time collaborative task manager using React, Node.js, and Socket.io supporting up to 50 simultaneous users; handled concurrent edits via operational transformation.'

(4) Scannability: Indian campus recruiters screen hundreds of resumes during placement season. The resume must be scannable in 20 seconds: clear section headers (bold), bullet points (not paragraphs), one page, logical section order (Education first for freshers).

(5) Tech stack alignment: does your skills section match what the company recruits for? A candidate applying to a Java-first company should list Java, Spring Boot, Hibernate at the top, not bury them after six other languages.

Recommended structure (in order):

(1) Header: full name (large), phone number (with +91 for international applications), professional email (firstname.lastname@gmail.com; not gaming handles or nicknames), LinkedIn URL (customise it: linkedin.com/in/firstname-lastname), GitHub URL if you have public projects, city name. No photo required (most Indian companies do not require it and some international companies discourage it to avoid bias).

(2) Education: college name, degree and branch, CGPA and year. Include 10th and 12th percentages only if above 85%; otherwise omit both or include only one. Do not include primary school.

(3) Skills: grouped by type. Languages: Python, Java, C++. Frameworks: React, Spring Boot, Django. Databases: MySQL, PostgreSQL, MongoDB. Tools: Git, Docker, VS Code, Linux. Only list technologies you can discuss in an interview at a basic level.

(4) Projects (most important section): 2-3 projects. For each: project name (bold) + GitHub link, 2-3 bullet points. Each bullet: what you built or did (action verb), what technology was involved (specifics), and the outcome or technical detail that differentiates it.

(5) Internship (if any): company name, role, dates, 2-3 bullets on what you worked on and what you delivered.

(6) Achievements and certifications: competitive programming ratings (LeetCode, Codeforces), AWS or GCP certifications, hackathon wins with context ('1st place out of 200 teams at HackBITS 2025 for a real-time traffic prediction system'), academic awards.

(7) Extracurriculars: only if genuinely impressive or leadership-relevant (technical club president, core team of a major college fest, open-source contributor with merged PRs). Not: 'member of coding club'.

Six ATS rules that change shortlist rates:

(1) Single-column plain layout: ATS parsers are not as sophisticated as humans. Two-column layouts, text boxes, tables, and stylised section headers often confuse parsers. A clean single-column layout with standard HTML-like headings is reliably parsed.

(2) Exact keyword matching: if the JD says 'Core Java', your resume should say 'Core Java' (not just 'Java'). If it says 'Agile methodologies', include that phrase. ATS searches for exact strings.

(3) Standard section headings: 'Education', 'Work Experience', 'Projects', 'Skills', 'Certifications'. Creative headings ('My Technical Toolkit', 'What I Build') are not matched by ATS parsers.

(4) No headers and footers: content in Word document headers/footers is often skipped by ATS parsers entirely. Put your name and contact information in the main body.

(5) Spell out acronyms at least once: 'Object-Oriented Programming (OOP)', not just 'OOP'. Some ATS search for the full phrase.

(6) Save as PDF (usually): PDF preserves formatting across systems. Some companies specifically request .docx; follow instructions. In the absence of instructions, PDF is safer for formatting preservation.

What ATS does NOT do: care about font aesthetics, visual design (unless it breaks parsing), or the number of pages (though human screeners care about length).

Six mistakes that consistently result in no-call:

(1) 'Objective statement' at the top: 'Seeking a challenging position where I can leverage my skills to contribute to your organisation's growth.' This statement is the same for every candidate and adds no information. Replace with a 2-line profile summary ONLY if you have something specific to say; otherwise skip it entirely.

(2) 15-technology skills section: listing C, C++, Java, Python, HTML, CSS, JavaScript, Bootstrap, jQuery, SQL, MongoDB, Firebase, PHP, Ruby, MATLAB sends the signal that you know none of these at a real interview level. List 5-7 technologies you can discuss confidently in an interview.

(3) Vague project descriptions: 'Developed an e-commerce website using React.' What did you specifically build? What was the hardest part? What is the user-facing outcome? Rewrite every project bullet with an action verb + specific technology + specific outcome or technical challenge.

(4) One resume for all companies: 15 minutes of keyword-matching the resume to a specific JD before applying meaningfully improves ATS pass rate. Have a base resume and customise the skills section and project bullet emphasis for each target.

(5) Irrelevant personal information: date of birth, father name, passport number, religious affiliation, hobbies ('cricket, music, cooking') with no professional relevance. These waste space and are not evaluated.

(6) Two-page fresher resume: a fresher resume must be one page. Every section that does not directly support 'hire this person for a software engineering role' should be removed. Two pages signal an inability to prioritise.