Resume Tips for Freshers — India 2026

For any candidate with less than 5 years of experience, a resume MUST be one page. Indian recruiters at services companies review 50-200 resumes per hour during campus season — two-page fresher resumes get skimmed less carefully than one-page ones. If you can't fit everything on one page, cut. Padding is worse than brevity.

1. Name + phone + email + LinkedIn (github/portfolio if relevant) — 3 lines max at the top. 2. Summary — 2 lines. What you study, what you're targeting. 3. Education — B.Tech/MBA/etc., college name, CGPA/percentage, graduation year. Add 12th and 10th percentages below. 4. Internships — chronological, most recent first. 2-3 bullets each with quantified outcomes. 5. Projects — 3 projects with tech stack, GitHub links, one outcome each. 6. Skills — grouped (Languages / Frameworks / Tools / Soft skills). 7. Certifications, achievements, extra-curriculars — one short section at the bottom.

1. Every bullet starts with a verb (Built, Deployed, Analyzed, Led). No 'Responsible for'. 2. Every bullet has a number. Users served, transactions processed, teams led, awards won. 3. Don't say 'good communication skills' — everyone says it. Show it with a specific example. 4. Projects need GitHub links. A project without a link looks fake. 5. Include only relevant coursework — if you're applying for full-stack roles, listing 'Digital Signal Processing' is noise. 6. Skip 'Hobbies' unless they're relevant (open-source, competitive programming, blog) — 'Reading books' hurts you. 7. Save the file as FirstName_LastName_Resume.pdf. Recruiters download hundreds; a clean filename gets found faster. 8. Get 2 people to read it before sending. Typos are the #1 reason freshers get rejected at the ATS stage.

Every fresher feels their internship was 'not real work'. Recruiters know this. The trick is to reframe: instead of 'attended standup meetings and did documentation', write 'shipped documentation for 4 REST APIs, used by 6 downstream teams'. Even small tasks have measurable outcomes if you look for them. And if your internship truly involved no real work — leave it off. A missing internship is better than a fake one.

Everyone knows most fresher projects are tutorial-based. But you can still stand out by: (1) adding one original feature the tutorial didn't cover, (2) deploying it live (Netlify / Vercel / Render / Railway — all free), (3) writing a 3-line README explaining what problem it solves. A deployed, working project always beats an impressive-sounding one that's just in a GitHub folder.

1. Include percentages, not just CGPA — services firms filter on percentages. 2. Mention your native city if you're willing to relocate — Bangalore/Hyderabad candidates get more interviews because those are the hubs. 3. If you have any AICTE-recognised certification or NPTEL Elite, list it — Indian recruiters weight these highly. 4. Language skills matter. If you're fluent in Hindi + 1-2 regional languages, list them — several service company client accounts explicitly ask for it. 5. Photo is optional but not disqualifying. If you include one, use a plain background and business-casual attire. Never a selfie.