Aman Gupta
Getting shortlisted for IT jobs in India is a chain — a parseable resume, exact keywords, eligibility, timing, and referrals. Here's what actually moves the needle, stage by stage.
Jun 25, 2026 · 11 min read
Read
Start from an ATS-tested template, or check how your current resume scores — both are free.
You finished your degree, you have a few good projects, and you've sent your resume to 40 companies. Nothing comes back. The problem usually isn't your skills — it's a resume format built like a biodata: a photo in the corner, your father's name and date of birth up top, a two-column template from a design site, and a "Declaration" with a signature at the bottom. To an Indian recruiter scanning for six seconds, and to the ATS most companies now use, that format actively works against you.
The best resume format for an Indian fresher is one page, single-column, and reverse-chronological — with education and projects near the top, no photo or personal details, and the file saved as a text-selectable PDF. This guide covers the exact layout, how to write every section, a full annotated sample resume, the format by stream, the campus-vs-off-campus difference, the common mistakes, and how to get past ATS — everything you need to build a fresher resume that gets shortlisted in 2026.
➡ Check your fresher resume against any job, free on ResumeLens.
Freshers should use the reverse-chronological format. It is the only one ATS systems parse reliably, and it puts your most recent education, projects, and internships first.
| Format | Best for | ATS-safe? |
|---|---|---|
| Reverse-chronological | Almost every fresher — lists education, projects, and internships most-recent-first | Yes — recommended |
| Functional (skills-based) | People hiding gaps or a lack of experience | Risky — parsers struggle and recruiters distrust it |
| Combination / hybrid | Career changers with transferable experience | Workable, but rarely needed by a fresher |
The functional format is tempting when you feel you have "nothing to show," but it buries the timeline both recruiters and ATS expect, and it signals you are hiding something. Use reverse-chronological and make your projects do the work.
Lead with contact details, then a short summary, then education — because as a fresher, your degree, CGPA, and projects are your strongest evidence. A recommended order:
| Order | Section | Notes |
|---|---|---|
| 1 | Contact information | Name, phone, email, city, LinkedIn, GitHub (for tech) |
| 2 | Summary / objective | 2–3 lines; optional but useful if focused |
| 3 | Education | Degree, institution, CGPA, year |
| 4 | Projects | The most important section for a fresher |
| 5 | Internships / experience | If any |
| 6 | Skills | Technical and tools, plain text |
| 7 | Certifications & achievements | Courses, hackathons, competitions |
For software and data roles specifically, move the Skills section above Education or just under your summary — recruiters scan for your tech stack first. (See the SDE and data science formats for the role-specific order.)
The skeleton above is the easy part. What goes inside each section is what gets you shortlisted.
Keep it to one clean line or two: full name, phone, a professional email, your city, and a customised LinkedIn URL — plus a GitHub URL for tech roles. Use "linkedin.com/in/yourname," not the default string of characters. Skip your full postal address (city is enough), and never use a college email you will lose access to. Keep contact details in the body of the document, not a header or footer the ATS may skip.
A 2–3 line summary is optional, but a focused one helps — it puts your strongest keywords at the very top where the ATS reads first. Drop the old "objective" cliché ("Seeking a challenging role in a reputed organisation where I can utilise my skills"). Instead, state who you are, your top skills, one proof point, and the role you want.
List your degree, institution, graduation year, and CGPA (on its native 10-point scale) if it is reasonably strong — roughly 7.5 and above. Add relevant coursework as a single line for tech roles (Data Structures, DBMS, Operating Systems, Computer Networks) — these double as ATS keywords for entry-level jobs. Include 10th and 12th marks only if they are strong or a campus drive asks for them.
For a fresher, Projects is your work experience. It is the section that proves you can build real things, so give it the most space and write each project the way you would write a job:
Weak: "Made a shopping website using web technologies."
Strong: "E-commerce REST API — built in Spring Boot and PostgreSQL with JWT auth, serving 500+ test users at 99.8% uptime; deployed on AWS EC2. github.com/yourname/shop-api"
Two to three well-described projects beat five one-line entries. (Full method: how to write resume bullet points that pass ATS.)
If you have internships, write them like projects — what you did, the tools you used, and the outcome, in reverse-chronological order. Even a short internship with one quantified result ("automated a daily report, saving the team ~4 hours a week") is strong. If you have none, skip the section entirely rather than padding it.
A plain, flat list grouped by category — Languages, Frameworks, Tools, Databases — using the exact terms from the job description. No rating bars, star meters, or skill graphs; the ATS cannot read them, and they make you look junior. Only list what you can defend in an interview.
Include certifications that signal relevant skill (AWS, Google, a strong Coursera/NPTEL specialisation) with the year. Add achievements that show ability — hackathon wins, coding-contest ranks (LeetCode, CodeChef), paper presentations, or scholarships — and quantify them ("1st of 200 teams," not "won hackathon").
Here is what a clean, ATS-friendly one-page resume looks like for a CSE fresher, with a note on why each part works. Adapt the structure to your own stream.
Aarav Sharma — Bengaluru · +91-98XXXXXXXX · aarav.sharma@gmail.com · linkedin.com/in/aaravsharma · github.com/aaravsharma
Why it works: city only, professional email, clean custom URLs — no photo, date of birth, or address.
Summary — Final-year B.Tech (CSE) student skilled in Java, Spring Boot, and React. Built and deployed 3 full-stack projects; Smart India Hackathon 2024 finalist. Seeking a Software Engineer role.
Why it works: role, stack, proof, and goal in two lines, with keywords up top.
Education — B.Tech, Computer Science & Engineering, [College], 2026 · CGPA 8.4/10 · Coursework: Data Structures, DBMS, Operating Systems, Computer Networks.
Why it works: strong CGPA shown on its native scale; coursework doubles as entry-level keywords.
Projects
• E-commerce REST API — Spring Boot, PostgreSQL, JWT auth; served 500+ test users at 99.8% uptime, deployed on AWS EC2. github.com/aaravsharma/shop-api
• Realtime Chat App — React, Node.js, Socket.IO; handled 1,000+ concurrent messages in load tests. github.com/aaravsharma/chat
Why it works: each project names the stack, gives a number, and links GitHub as plain text.
Internship — Backend Intern, [Startup], Summer 2025 · Built 4 REST endpoints in Node.js and wrote tests that cut a recurring bug class by 30%.
Why it works: framed as impact, not "assisted the team."
Skills — Languages: Java | Python | JavaScript | SQL · Frameworks: Spring Boot | React | Node.js · Tools: Git | Docker | Postman · Databases: PostgreSQL | MongoDB
Why it works: grouped, plain text, exact-match terms — no rating bars.
Achievements — Smart India Hackathon 2024 finalist (top 6 of 200+ teams) · LeetCode rating 1750.
Why it works: quantified, role-relevant.
A fresher resume should be one page. In India, two pages are acceptable once you have real experience, but as a fresher you almost never need a second page — and padding to fill one weakens you. A tight, one-page resume where every line earns its place reads as more confident than two pages of filler. Page count is a recruiter-attention issue, not an ATS one — the system parses however many pages you submit, but recruiters spend their first 6–8 seconds on page one.
Include the things that prove capability; cut the biodata leftovers that Indian resumes carry out of habit.
| Include | Skip |
|---|---|
| CGPA (if 7.5+ on a 10-point scale) | Photograph |
| Projects (with tech stack and outcomes) | Date of birth |
| Internships | Father's / parents' name |
| Technical skills | Marital status, gender, religion, nationality |
| Certifications & relevant coursework | Full postal address (city is enough) |
| Achievements (hackathons, competitions, ranks) | "Declaration" line and signature |
The photo, date of birth, parents' names, and the "I hereby declare…" line are holdovers from the old biodata format. They are not expected on a modern Indian tech resume, they push useful content off page one, and a photo in a header can break ATS parsing.
When to include 10th and 12th marks: include them only if they are strong, or if a campus placement or company explicitly asks (many Indian drives have 10th/12th and CGPA cut-offs). If you are applying off-campus a year or two after graduating, your degree and projects matter more — list 10th/12th as a single line, or drop them.
The skeleton is the same; what fills your Projects and Skills sections changes by stream.
| Stream | What to emphasise |
|---|---|
| CSE / IT | Coding projects with GitHub links, programming languages, DSA, a named tech stack |
| ECE / EEE | Embedded/IoT projects, tools (MATLAB, Verilog), plus any coding skills for software roles |
| Mechanical / Civil | Design projects, CAD tools (AutoCAD, SolidWorks), internships, domain software |
| Commerce / BBA | Internships, finance/marketing certifications (Tally, Excel, financial modelling), case competitions |
| Arts / Humanities | Internships, a writing or design portfolio, relevant tools, communication and research skills |
CSE / IT freshers should lead with projects and a clearly named tech stack, and link GitHub — for software roles, demonstrated coding ability outweighs CGPA. Core-branch (ECE, Mechanical, Civil) freshers targeting software roles should foreground their coding projects and DSA, treating the core degree as background; those staying in-domain should foreground domain projects and the relevant software (MATLAB, AutoCAD, SolidWorks). Commerce and BBA freshers should lead with internships and tool certifications (Tally, advanced Excel, financial modelling) and any case-competition results. Arts and humanities freshers should lead with internships and a portfolio link, and translate coursework into concrete skills — research, writing, communication, specific tools.
No internship? Lead with projects — academic, personal, freelance, or open-source — and treat each like work experience, with the tech used and a measurable outcome. Add relevant coursework, certifications, and volunteer or club roles. A well-described project beats an empty experience section.
A low CGPA? Don't lie, and don't draw attention to it. Show it on its native scale if asked or if it's borderline-acceptable; if it's weak and not required, keep education minimal and let strong projects, internships, and certifications lead. Many off-campus roles never see your CGPA at all — your projects do the talking.
A year drop or backlog during college? List your degree and graduation year plainly and move on. Don't add an explanation on the resume — focus it forward on skills and projects, and save the context for the interview, where you can frame it positively.
From a Tier-2 or Tier-3 college? College brand matters less off-campus than on. Compensate with stronger projects, a visible GitHub, coding-contest ratings, and exact keyword matching to each job description — these are signals the ATS and recruiter can verify regardless of where you studied.
Switching branches (e.g. Mechanical to software)? Frame yourself for the target role: lead with coding projects, relevant online certifications, and a summary that states the role you want. Let the degree sit as background rather than the headline.
Off-campus vs on-campus. On-campus drives often have fixed formats and CGPA cut-offs, so meeting the eligibility criteria matters most. Off-campus is harder: there is no campus filter, your resume faces the ATS cold, and you are competing against everyone. That means tailoring exact keywords from each job description matters far more — see why ATS rejects your CV if your applications are going silent.
These are the patterns that quietly sink fresher resumes — fix them before you apply.
Every job description hands you the keywords your resume needs. Read the posting, list the skills and tools it names, and make sure the ones you genuinely have appear verbatim in your resume — in your skills section and, better, inside your project or internship bullets. On Naukri, scroll to the "Key Skills" tags at the bottom of each posting; those are the exact terms the employer's system filters on. Entry-level keywords worth having where they apply include Python, Java, SQL, Git, REST APIs, Data Structures, Algorithms, OOP, Agile, and the specific frameworks in the JD.
| Element | India | US |
|---|---|---|
| Length | One page for freshers; two acceptable with experience | One page strongly preferred |
| 10th / 12th marks | Often included (campus context) | Never included |
| CGPA | On a 10-point scale | GPA on a 4.0 scale |
| Photo / DOB | Still common — but should be dropped | Never included |
| Page size | A4 | US Letter |
| "CV" vs "resume" | Used interchangeably | Distinct (CV is academic, longer) |
Indian companies — TCS, Infosys, Wipro, MNCs, and funded startups — use ATS, so your fresher resume has to be machine-readable first. The non-negotiables: single-column layout, standard headings (Education, Projects, Skills), no tables or text boxes, contact details in the body, and a text-selectable PDF exported from Word or Google Docs. The single most common fresher mistake, which ResumeLens sees constantly across hundreds of college resumes, is submitting an image-based PDF — a file that looks fine but contains zero readable text, so the ATS extracts nothing and the candidate never finds out.
For the full mechanics, see the complete ATS resume guide. To start from a clean, parser-safe layout, use an ATS-friendly resume template or Resume Builder.
➡ Upload your resume and see your ATS score before you apply, free on ResumeLens.
A one-page, single-column, reverse-chronological format with education and projects near the top, no photo or personal details, and the file saved as a text-selectable PDF. This is the format that both Indian recruiters and the ATS most companies use can read reliably.
One page. As a fresher you rarely have enough relevant content to justify two pages, and padding to fill a second page weakens the resume. Keep it to one page where every line earns its place.
Lead with projects and treat each like a job — name the tech, describe what you built, and add a measurable outcome. Add internships if any, relevant coursework, certifications, and achievements like hackathons or coding-contest ranks. A strong project section more than makes up for no formal experience.
Not necessary, but a focused 2–3 line summary helps by putting your strongest keywords at the top. Skip the generic "seeking a challenging role" objective; instead state your top skills, one proof point, and the role you want.
Two to three well-described projects, each with the tech stack, what you built, a measurable outcome, and a plain-text GitHub link. Quality beats quantity — two strong projects outperform five one-line entries.
No. A photo adds no value to a tech or corporate application, takes up space on page one, and — if placed in a header — can break ATS parsing. Leave it off unless the role specifically requires it.
Include them only if they are strong, or if a campus placement or company explicitly asks (many Indian drives have cut-offs). If you are applying off-campus after graduating, your degree and projects matter more — list 10th/12th as one line or drop them.
Don't hide it if asked, but don't headline it either. If it's borderline-acceptable, show it on its native scale; if it's weak and not required, keep education minimal and let strong projects, internships, and certifications lead. Many off-campus roles never check CGPA.
No. The "I hereby declare…" line with a place, date, and signature is a biodata holdover. It is not expected on a modern resume and just consumes space. Leave it off.
Keep one strong base resume, then tailor the keywords and emphasis to each job description before you apply. You don't rewrite it each time — you adjust which skills and projects lead so they mirror the role's language.
An ATS-safe font — Arial, Calibri, or Times New Roman — at 10–12pt for body text and 12–14pt for headings. Avoid decorative fonts, which can turn into garbled characters during parsing.
A4. US Letter is the standard in the United States, but in India A4 is expected. Never use A3 or any oversized format.
Be careful. Many Canva templates use columns, graphics, and image exports that break ATS parsing — and image-based PDFs are the most common fresher mistake. If you build in Canva, export it, run it through an ATS checker, and switch to a plain template if it scores poorly.
Related guides: How to Optimize Your Resume for ATS (Complete Guide) · ATS Resume Format for Software Developers · Resume Bullet Points That Pass ATS · ATS-Friendly Resume Templates · Free ATS Resume Checker
An employment gap won't get you auto-rejected by the ATS — it reads your dates, not your story. Here's how recruiters read gaps after the 2023–25 layoffs, and how to present yours honestly.
Jun 25, 2026 · 11 min read
Read
ResumeLens vs Jobscan compared honestly: where each wins, pricing, India/Naukri support, and who should pick which. A candid head-to-head, not a sales pitch.
Jun 25, 2026 · 10 min read
Read