Fresher Resume Guide (2026): ATS Reality, One-Page Structure & Project Bullets
Updated August 2026
Almost every resume tip aimed at Indian freshers is about beating the ATS, and the premise is mostly wrong. An applicant tracking system is a database with a search box, not an artificial intelligence that judges you. It parses your file into text and lets a recruiter search and filter. It does not score your personality, and in most fresher pipelines it is not what rejected you.
The two filters that actually remove freshers are less glamorous. The first is eligibility — CGPA thresholds, active backlogs, branch and batch year — which is applied automatically and which no amount of formatting will change. The second is a human being skimming for a few seconds to decide whether to open your profile properly. Those are the two things a resume can be built for, and building for a mythical AI gatekeeper instead is why so many carefully formatted resumes go nowhere.
So the working definition on this page: your resume has one job, which is to survive a six-second skim and leave the reader with something specific to ask you about. Everything below follows from that. If you want to check your own file mechanically afterwards, the resume ATS checker and the resume template on our tools pages will catch the parsing problems this page describes.
Frequently asked questions
What does an ATS actually do, and can it reject me?
It parses your file into plain text, stores it against your application, and lets recruiters search and filter — by keyword, by CGPA, by branch, by batch. That is close to the whole of it for fresher hiring. It does not read for quality or rank you against a personality model. Two things genuinely do reject you automatically: eligibility filters set by the recruiter, and a file it cannot parse, which happens with resumes built as images, heavy multi-column layouts or text inside headers and footers. Fix the parsing, meet the eligibility, and stop optimising for a machine that is not judging you.
Should a fresher resume be one page?
Yes, essentially always. You have no work history to justify more, and a second page signals padding rather than depth to someone skimming. If you are over one page, the material to cut is almost always the same: an objective statement, a declaration, personal details, hobbies, coursework lists and school marks. What survives is education, skills, projects, any internships, and genuine achievements. If you are still over after that, your project descriptions are too long rather than too many.
What order should the sections be in?
Contact details, education, skills, projects, internships or experience if you have any, then achievements. For freshers, projects carry the most weight after eligibility, so they belong high and should occupy the most space. Two adjustments worth making: if you have a genuinely relevant internship, move it above projects; and if you are targeting a specific role, order your skills so the relevant ones appear first, because a skimming reader stops reading a line partway through.
How do I write project bullets that actually work?
Each bullet should answer three things: what the thing does, what you personally built, and what came of it. The weak version is "Worked on a machine learning project using Python" — it identifies a category of activity and could belong to anyone. The strong version names the problem, your contribution and a concrete result: "Built a model to flag duplicate support tickets from 40,000 historical tickets; wrote the preprocessing and the training loop; reduced manual triage in testing by about a third." Start with a verb, keep to one or two lines, and prefer a specific detail over an adjective. If a number is genuine, use it; if it is not, do not invent one, because the follow-up question will expose it.
How many projects should I list, and what if mine are tutorial projects?
Two or three described properly beats six listed. On tutorial projects, be honest with yourself about what a reader sees: a to-do app, a portfolio site and a weather dashboard appear on thousands of resumes and signal that you followed instructions. The cheapest fix is not building something more ambitious but taking one existing project and adding something that was your own decision — a real dataset, a feature nobody in the tutorial had, deployment somewhere public, or a problem you actually hit and solved. One project you can talk about for ten minutes is worth more than five you can describe for thirty seconds.
What should I put in the skills section?
The things you would be comfortable being questioned on, grouped simply — languages, tools, databases, frameworks. The mistake is listing everything you have ever touched, because interviewers frequently pick the item you are weakest on, and a long list invites that. Drop anything you cannot discuss for two minutes. Avoid self-assessed proficiency bars and star ratings, which are unverifiable, take space and read as filler. If you know one language properly and two superficially, listing the one is stronger than listing three.
What should I cut from the standard Indian resume template?
The conventional template carries a lot that costs you space and gains nothing: the objective statement, which every fresher writes and no recruiter reads; the declaration and signature; date of birth, marital status, father's name and full address, none of which are relevant and some of which are information you have no reason to volunteer; "references available on request"; and hobbies unless one is genuinely unusual and worth a conversation. Photographs are conventional in some sectors and unnecessary in most technology hiring — omit unless a specific employer asks. What you free up goes to projects.
Should I put my CGPA on my resume if it is low?
Include it. Most fresher applications require it in the form anyway, eligibility is checked against records rather than your resume, and omitting it reads as concealment to anyone skimming — which invites more scrutiny than a modest number does. A resume is not the place to explain it either; there is no room and the format works against you. Prepare a brief, non-defensive explanation for the interview instead, one sentence of fact and what changed since, and let the projects section do the persuading in the meantime.
Do I mention backlogs on my resume?
No — a resume is a summary of what you offer, not a disclosure form, and there is no natural place for it. Where it does matter is the application form and the eligibility screen, where most recruiters ask for no active backlogs at the time of onboarding, and where you must answer accurately. Clear them at the earliest opportunity, answer honestly wherever asked, and have a short factual explanation ready for the interview. Concealing an active backlog on a form is a different matter entirely and can cost you an offer after it is made.
Should I tailor my resume for each company?
Not a rewrite — a fifteen-minute adjustment, which is the version people actually sustain. Read the job posting, and make sure the skills and projects it emphasises appear early rather than buried, using the same words the posting uses where they honestly apply to you. That last point is the only legitimate sense in which keywords matter: recruiters search the database for the terms in their own requirement, so if you built REST APIs and the posting says REST APIs, write REST APIs rather than a synonym. Stuffing terms you cannot defend is a different thing and fails at the interview.
What formatting keeps a resume parseable?
A single-column layout, standard section headings that say what they are, a common font, and no important text inside images, headers, footers or text boxes — those are the things parsers drop. Simple tables are usually fine now, but a multi-column design where a parser reads across columns instead of down them scrambles your resume into nonsense. Export as PDF unless a portal explicitly asks for Word, and check by opening your own PDF and copying the text into a plain text editor: whatever you see there is roughly what the system sees. Our resume ATS checker automates that check.
What should I name my resume file?
Your name and ideally the role — Rohit_Kumar_Software_Engineer.pdf. It sounds trivial and it is not: recruiters download hundreds of files, and resume.pdf or resume_final_v3.pdf is both unfindable and mildly careless in a way that a name is not. This is a ten-second fix that costs nothing and is skipped by a large share of applicants.
Should I include GitHub, LinkedIn or a portfolio link?
Include them if they help you, and check what a reader lands on before you do. A GitHub link with three empty repositories and no commits in a year actively hurts, because you invited someone to look and there was nothing there. Before adding it, make sure your pinned repositories are the projects on your resume, that each has a readme explaining what it does and how to run it, and that the commit history looks like work rather than a single upload. The same applies to a portfolio: a broken or half-finished site is worse than no link.
What if I have no internships?
Most freshers in most colleges do not, so this is normal rather than disqualifying, and the space simply goes to projects. What substitutes credibly is anything with real stakes: a project with actual users however few, freelance or college-department work, a contribution to an open-source repository, a competition entry, or a technical role in a college club with something concrete delivered. What does not substitute is a list of online course certificates, which are cheap to obtain and therefore weak signals — one certificate with a substantial project built from it is worth more than eight on their own.
How do I describe an internship where I did not do much?
Honestly and specifically, which is usually better than it feels. Describe what the team was building, what you were actually given, and what you understood by the end — including if the answer is that you shadowed, fixed small defects and learned how the codebase was organised. Interviewers know what a first internship looks like and are testing whether you can talk about real work. An inflated description falls apart in the first follow-up, and inflating is far more damaging than a modest but truthful account.
Do achievements and certifications matter?
Some do. Competitive programming ratings, hackathon results, published work, sports or leadership at a serious level, and scholarships all carry real signal because they are hard to obtain. Bulk online certificates do not, because everyone has them and completion required no selection. The test worth applying: could most of my batch get this by paying and spending a weekend? If yes, it belongs at most in a single compact line, not in a section of its own.
How long does a recruiter actually spend on my resume?
Seconds, on the first pass, which is the fact that should shape the whole document. What that reader is doing is locating a few things quickly: what you studied, whether you clear the bar, what you have built, and whether anything is worth a question. Which is why structure beats prose — short bullets, strong first words, the most relevant material highest on the page. If your resume requires careful reading to reveal its best point, that point will not be found. Read your own resume for six seconds and see what you retain.
What should a 2027-batch student do about their resume now?
Build the material rather than polish the document, because a resume is downstream of what you have done and no formatting rescues an empty one. In your pre-final year the highest-return moves are one project with a real dataset or real users that you can discuss in depth, a tidy GitHub with readmes, and any exposure with actual stakes — an internship, freelance work, a department project. Write the resume in final year in an afternoon once there is something to write about. And keep a running note of what you did as you do it, because reconstructing specifics a year later is how vague bullets get written.
Don't just read Resume questions — get asked them
Phiny's AI interviews you on exactly these topics, follows up on weak answers, and tells you what a stronger answer looks like. Text interviews are free and unlimited.
Start a free AI mock interviewHow to prepare
- Build for a six-second skim, not for an imagined AI gatekeeper. The real filters are eligibility, which formatting cannot change, and a human deciding quickly whether to look properly. Everything else on this page follows from that.
- Test parsing yourself in thirty seconds: open your PDF, select all, paste into a plain text editor. Whatever survives is roughly what the system stores — if your sections arrive scrambled or your contact details vanish, that is a layout problem worth fixing before anything else.
- Rewrite every bullet that starts with "worked on" or "was responsible for". Name what the thing does, what you personally built and what came of it. That single pass improves most fresher resumes more than any template change.
- Never write a number you cannot defend. Invented percentages are a common and easily exposed habit — the follow-up question is simply "how did you measure that?", and there is no recovery from not having an answer.
- Check your own links before you send them. A GitHub profile with empty repositories is worse than no link at all, because you invited the reader to look. Pin the projects on your resume, add a readme to each, and make sure the page loads.
Where these questions get asked
- TCS NQT guide and Infosys hiring guide — the two biggest exams these questions appear in.
- All company placement guides — pattern, syllabus and rounds for every mass recruiter.