Fresher Resume Tips for Indian Job Seekers: Stand Out in 2026

Indian recruiters processing hundreds of applications per day spend 6–10 seconds on an initial resume scan. One page is non-negotiable for freshers with under 2 years of experience.

One page forces you to prioritise: everything on the resume is there because it matters. Two pages with padding (irrelevant courses, generic hobbies, every subject studied) reads as poor judgment. Exception: PhD students and research-focused roles: up to 2 pages is acceptable for academic output. Format: clean single-column or two-column layout. Do not use templates with heavy graphics, sidebars with skill bars, or photo headers: Indian ATS systems often fail to parse these. Standard fonts: Calibri, Georgia, or Helvetica 10–11pt body, 12–14pt headings.

The order of sections in a fresher resume should reflect what Indian recruiters care about most.

Recommended order: (1) Contact Details (name, phone, email, LinkedIn URL, GitHub: no photo, no date of birth). (2) Education (CGPA prominently: it is the primary filter in most IT fresher hiring). (3) Projects (most important section for tech freshers: 2–3 strong projects beat a dozen generic ones). (4) Technical Skills (languages, frameworks, tools: one line per category). (5) Experience (internships if any: most freshers do not have this). (6) Certifications (relevant certifications only). (7) Achievements (competitive programming rankings, hackathon wins, academic awards). (8) Extracurriculars (optional: only if leadership or significant achievement).

The projects section is the single most important differentiator in a fresher resume in India.

Each project entry should follow this structure: Project name + tech stack (bold the tech). One-line description of what the project does. Two to three bullet points: what specific problem it solves, what you specifically built (not what the project does as a whole), and one measurable outcome if possible ('reduced API response time by 40%', 'achieved 94% model accuracy'). Link to GitHub or live demo if available. Common mistakes: listing the project name and tech stack with no description of what you built or why. Describing the project's full feature set instead of your specific contribution. Projects to prioritise: full-stack web apps with a backend, ML projects trained on real data, mobile apps with published store presence, or contributions to active open-source projects.

Most large Indian companies (TCS, Infosys, Wipro, Flipkart, Amazon India) use ATS systems that parse resume text before a human sees it.

ATS-friendly basics: use standard section headings ('Education', 'Projects', 'Skills': not creative alternatives like 'My Journey'). Save in PDF format (generated from Word or Google Docs, not scanned). Avoid tables, text boxes, and graphics: ATS parses these badly or not at all. Keywords: copy the job description and make sure the key technical terms it mentions appear on your resume. If the JD says 'Java Spring Boot' and your resume says 'Spring framework': the ATS may not make the connection. Company-specific tip: TCS NQT uses a resume screener before the test: ensure your CGPA is prominent in the top half of the resume.

Many strong freshers have sub-7.0 CGPA due to circumstances beyond academic performance. Here is how to handle it.

Do not hide it: ATS systems and HR forms always ask for it; lying creates a compliance problem later. Compensate visibly: 2–3 strong projects that demonstrate practical competence can offset an average CGPA in off-campus and startup hiring. Competitive programming rank (Codeforces, LeetCode: 1800+ rating, LeetCode top 10%) is taken seriously by Google, Amazon, and product companies. Internal company channels: apply to companies that do not have a CGPA cutoff (most startups, product companies hiring on merit, off-campus drives with holistic screening). Some companies explicitly have 55% or 6.0 CGPA as their bar: filter for these in job searches.