The resume format for freshers in India is one page, single column, with education above projects and projects standing in for work experience. That is the whole answer, and the rest of this page is what goes in each section, in what order, and the formatting decisions that decide whether an applicant tracking system can read the file at all.
I have watched a lot of fresher resumes go out, and the failures cluster in two places. Either the file is beautiful and unreadable to software, or it is readable and spends its one page on the wrong things. Both are format problems, which is good news: they are fixable in an evening without inventing experience you do not have.
The section order that works
| # | Section | Why it sits here |
|---|---|---|
| 1 | Contact details | Name, phone, email, city, one link. In the body, never in a header |
| 2 | Headline | One line naming the role you want, in the words a recruiter would search |
| 3 | Summary | Two sentences. Branch, strongest skills, target role |
| 4 | Education | Freshers get filtered on degree, branch and year before anything else |
| 5 | Projects | Your evidence section. This replaces work experience |
| 6 | Internships | Even a six-week one. Real workplace exposure counts |
| 7 | Technical skills | Plain text list. This is what recruiter search actually matches |
| 8 | Certifications | Exact names, because they are searched as exact strings |
| 9 | Extras | Positions of responsibility, publications. Only if space remains |
Education above projects is the one that surprises people, because every guide written for experienced candidates says the opposite. For a fresher it is correct. Campus and entry-level filters in India narrow by degree, branch, graduation year and often a CGPA cut-off, and a recruiter checking whether you clear the bar should not have to hunt for it.
Contact details, and the header trap
Name, phone number, email address, city, and one link that is worth clicking. That is a GitHub profile for engineers, a portfolio for designers, a LinkedIn URL for everyone else.
The trap is putting all of it inside the document’s header region. It looks tidy and it is the single most common reason a resume scores badly: many parsers skip headers and footers entirely, so your name and phone number simply do not exist in the extracted text. Put contact details in the body of the page, as ordinary text on the first lines.
Use a professional email address. An address built for school still turns up regularly and it costs credibility for no reason.
The headline
One line, directly under your name, naming the role you are targeting in the vocabulary a recruiter would type.
B.Tech CSE 2026 | Java, Spring Boot, MySQL | Backend Developer
Not “Hardworking and passionate individual seeking a challenging role”. That sentence appears on a large share of fresher resumes, matches nothing, and burns the most valuable line on the page. The headline exists to be matched and skimmed, so it should read like a search query.
The same logic applies to your Naukri profile, and the Naukri profile headline examples post has copy-paste starting points by role including a fresher section.
Summary, not objective
Two sentences. What you studied, what you can actually build, what you are looking for.
The traditional objective format (“To secure a challenging position in a reputed organisation where I can utilise my skills”) tells the employer what you want. They do not need that, and it occupies the space where evidence should sit. A summary naming your branch, your strongest two or three technical skills, and your target role does the same job and reads like this decade.
Full treatment with copy-paste examples by branch is in resume summary for freshers.
Education
Degree written out in full, institution, graduation year, and your CGPA or percentage exactly as printed on your marksheet.
Write the branch out. “B.Tech Computer Science and Engineering”, not “BTech CSE” alone. Recruiters filtering campus hiring search the expanded form as often as the abbreviation, and the expansion costs you four words. Including both is not stuffing, it is coverage.
Do not convert your CGPA into a percentage yourself. If your marksheet says 7.8 CGPA, write 7.8 CGPA. Recruiters set cut-offs in the unit the marksheet uses, and a self-converted number lands in the wrong comparison.
Class 10 and 12 marks are worth one compact line each, and only while you are a recent graduate. They come off the resume within a year or two of your first job.
Projects, the section doing the real work
This is the section that decides whether a fresher resume is any good, and the format rule is simple: format each project exactly the way you would format a job.
Campus Placement Portal Jan 2026 - Apr 2026
React, Node.js, PostgreSQL, deployed on AWS EC2
- Built a role-based portal used by 400+ students across 6 departments
- Cut placement-cell data entry from 3 hours a week to under 20 minutes
- Wrote 40+ unit tests, keeping coverage above 80% through three refactors
Title, stack in plain text, a date range, then two or three bullets that say what you built and what changed because of it. Numbers are available to you even without a job: users, records, requests, percentage improvements, test counts, team size, weeks saved.
Two or three real projects beat six tutorial clones. “Built a to-do app” is a line every reviewer has read hundreds of times. A project with a stated user count and a measured outcome is not.
The stack line matters more than it looks. It is the plain-text evidence that you have used the exact tools the posting names, and it is what recruiter search matches against.
Internships and technical skills
Any internship goes on, however short and however unglamorous, in the same format as a project. Six weeks in a real workplace is a signal about how you behave in one.
Skills go in as a plain-text, comma-separated list, grouped loosely: languages, then frameworks, then databases, then tools. Six to twelve items for a technical fresher.
What to leave out: skill bars, star ratings and percentage meters. They parse as nothing, and no recruiter has ever believed a four-out-of-five in Python. Soft skills like communication, teamwork and leadership are almost never filtered on, so one short line at most and only if the posting explicitly asks.
Which specific terms belong in that section depends entirely on your branch. The ATS keywords list by job role has the pool for ten role families taken from live Indian postings, and resume for freshers by branch covers what changes between B.Tech, BCA, B.Com, MBA and the non-engineering routes.
One page, and what to cut to reach it
One page is not a stylistic preference for a fresher. It is a consequence of how the first scan works: seconds, top-down, looking for a reason to keep reading. A second page moves your projects below the point where anyone is still looking.
If you are over, cut in this order, and none of these will be missed:
- Photo. Not expected in India for corporate roles, and it eats a large block of prime space.
- Date of birth, father’s name, marital status, nationality, full postal address. City is enough.
- The declaration line and signature. Inherited from a form-filling era. Nobody reads it.
- Hobbies, unless one is genuinely relevant to the role.
- School marks, compressed to one line each.
- Tutorial projects, so the good ones get more room.
What you should not cut to save space: the stack lines under your projects, or the numbers in your bullets. Those are the content.
The formatting that decides whether it parses
Everything above assumes software can read the file. Often it cannot, and the resume is never seen by anyone.
| Choice | Verdict |
|---|---|
| Single column | Yes. Two columns scramble reading order in many parsers |
| Real text-based PDF | Yes. Select text in your file: if words highlight, it is fine |
| Image or scanned PDF | No. Software sees an empty page |
| Contact details in the body | Yes |
| Contact details in a header or footer | No. Frequently skipped entirely |
| Standard section names | Yes. “Education”, “Projects”, “Skills” |
| Creative section names | No. “My Journey” matches nothing |
| Tables and text boxes for layout | No. Reading order becomes unpredictable |
| Icons instead of labels | No. An envelope glyph does not parse as “email” |
| Standard fonts, 10 to 11.5pt | Yes |
The design-tool export is the most common failure in this list. A resume built in a graphics tool and exported as a flattened image looks the best of anything on the recruiter’s desk and contains, as far as any applicant tracking system is concerned, no text at all.
The fastest way to know is to run the file through a checker that extracts text the same way a parser does. Ours is free with no login, and ATS score for freshers covers what to aim for and the three checks that quietly fail entry-level resumes. If you would rather start from something that exports cleanly by default, the free resume builder does that.
Common fresher resume mistakes
- A two-page resume with one page of content. Almost always marks, hobbies and a declaration.
- The objective paragraph. Four lines saying nothing, in the best position on the page.
- Listing coursework as skills. “Studied DBMS” is not the same claim as “PostgreSQL”.
- No dates on projects. Undated entries break chronological sorting and read as vague.
- Inflated skills. Every term on your resume is a question you have agreed to answer.
- One resume for every role. Reorder the skills line per target role. It is a ten-minute edit.
- A file named
resume_final_v3_updated.pdf. UseFirstname-Lastname-Resume.pdf.
Rule of thumb
One page, single column, education above projects, projects formatted like jobs with numbers in the bullets, skills as plain text, exported as a real PDF. Get there once, confirm it parses, and then stop editing.
The last part is the one freshers get wrong most often. Past a clean, readable, specific one-pager, further polish stops paying and the returns move entirely to how many suitable roles you apply to, and how early. There is more on that in how to write a resume for freshers with no experience and the wider ATS-friendly resume checklist.
ApplyCove reads each job description before applying and answers screening questions for you, on Naukri and LinkedIn, up to 200 applications a day by plan. From Rs 349/month with a free plan always available. See how it works.
