A resume template assumes you have a work history. A fresher does not, which is why the standard advice produces a page that is 20% content and 80% padding — a bloated skills list, a paragraph of objective, the school percentages, three certificates from a video course, and a hobbies line.
The document works fine without work experience. It just needs a different order and a different centre of gravity.
The order
For someone with no full-time role yet, and in this sequence:
- Header — name, phone, email, city, one or two links.
- A two-line summary, if and only if you can be specific.
- Education — degree, institution, year, CGPA if it is decent.
- Projects — the largest section on the page.
- Internships / training, if any.
- Skills.
- Anything genuinely distinguishing — a competitive rank, a publication, a position of responsibility with real scope.
Education goes near the top for a fresher because it is the thing being screened on. Once you have two years of work, it drops to the bottom permanently.
One page. There is no version of this that needs two.
Projects are your experience section
This is the part that decides the shortlist, and the part most freshers write worst — usually as a title and a technology list:
E-commerce Website — HTML, CSS, JavaScript, PHP, MySQL
That tells a reader nothing except that you followed a common tutorial. What it needs is what any experience bullet needs: what the problem was, what you built, and what came of it.
Split — expense-sharing app for hostel rooms (React Native, Firebase) Built because we were settling mess and electricity bills over WhatsApp and constantly getting them wrong. Handles uneven splits and partial payments, keeps a running balance per person. Used by about 60 students across two hostels; roughly 40 weekly active as of March. [github.com/…]
Four lines, and it does a great deal of work. There is a real motivation, a real user count, a hard-ish problem in it (uneven splits and partial settlements), and a link. An interviewer reading that has three questions ready, and you will enjoy answering all of them.
Rules that hold generally:
- Two or three projects, described properly, beat six listed. The marginal project adds nothing; the marginal detail adds a lot.
- A link beats a description. A repo, a deployed URL, a published dashboard, a Behance page. Anything that can be opened.
- Say what was hard. "Handles partial payments" is more interesting than "user-friendly interface".
- Do not list tutorial projects as if they were yours. A to-do app, a portfolio site, a clone built step by step from a video — an interviewer identifies these in two questions, and the credibility cost is worse than the empty space would have been.
- Group project? Say what you did. "Team of four; I built the payment flow and the reconciliation job."
If you have nothing that meets this bar, the honest answer is to spend three weekends building one thing before you spend three months applying. One project you can talk about for fifteen minutes changes the shape of every interview you get.
Education, and how much of it to include
Degree, branch, institution, year of completion, and CGPA or percentage if it is above roughly 7.0 / 70%. If it is below that, leave it out — nobody asked, and the ones with a hard cutoff will ask.
Class 10 and 12 numbers are worth including only for campus placements and for companies that explicitly screen on them (a fair number of Indian services companies and banks still do). Once you have a degree and any real project work, they are taking space that projects should have.
Coursework lists add almost nothing. "Data Structures, DBMS, Operating Systems" is implied by the degree. Include a course only if it is unusual and relevant — a formal statistics sequence for an analytics role, a semester on embedded systems for a hardware role.
Internships, including the unimpressive ones
Write them like jobs: organisation, role, dates, two or three bullets with scope.
If your internship was mostly observation — which is common and not your fault — do not inflate it. Write what you genuinely did:
Intern, Finance — Sundaram Fasteners, Chennai | May–Jul 2025 Reconciled vendor ledgers for the two-wheeler division; cleared a backlog of ~300 open line items. Built the Excel model the team now uses for monthly ageing.
Small, real, and specific beats "gained exposure to financial processes and enhanced my knowledge", which is what most internship bullets say and what none of them are believed for.
No internships at all? It is not disqualifying. Freelance work, a college fest you actually ran the budget for, a family business you did real work in, an NGO project — all of it counts if you describe it with the same specificity.
Skills, without the scoreboard
Two or three grouped lines:
Languages: Python, Java, SQL Tools: Git, Postman, Power BI, Excel (Power Query) Coursework-level: React, Docker
That last grouping is a useful honesty device. It tells the reader which things you have used properly and which you have touched, and it pre-empts the interview question that otherwise catches people out.
Delete the star ratings and the percentage bars. Nobody has a calibrated scale for "Python: 80%", the reader knows it is a guess, and graphical bars parse badly. Delete anything you would not want to be questioned on — listing a skill is an invitation, and technical interviewers accept the ones you sound least sure about.
Also delete "MS Office" and "Internet" unless the job is genuinely clerical. And do not put soft skills — "team player", "quick learner" — in a skills list. They are assertions, not evidence, and every resume has them.
Certificates, honestly weighted
Certificates from short online courses are worth very little on their own, and freshers consistently overrate them. Six Coursera certificates do not equal one working project, and a screening recruiter has seen the same six on forty resumes this week.
Worth listing:
- Vendor certifications with a real exam — AWS, Azure, Google Cloud, Oracle, Cisco, Tableau. These are verified and they cost something.
- A course whose output was a real artefact, in which case list the artefact under Projects and mention the course in one line.
- Domain qualifications with standing — NISM, IRDAI, CFA levels, whatever your field's equivalent is.
Not worth a section: participation certificates, webinar attendance, "workshop on machine learning", one-day college events. If you need them to fill the page, the page needs another project instead.
The things to delete outright
Indian resume templates carry a set of conventions that are pure inheritance from government forms. On a private-sector application in 2026, all of these should go:
- The photograph. It invites bias, it breaks some parsers, and outside a handful of fields nobody needs it.
- Father's name, date of birth, gender, marital status, nationality, religion, caste. None of it is relevant to whether you can do the job.
- Full postal address. City and state is enough.
- The declaration — "I hereby declare that the above information is true…" with place and signature. It has no legal weight in a job application and eats a fifth of your page.
- "References available on request." Assumed.
- An objective paragraph about seeking a challenging position in a reputed organisation. It appears on a hundred thousand resumes and conveys nothing.
- Hobbies, unless genuinely distinctive. "Reading, music, travelling" is filler; "state-ranked chess" is a fact about you.
That is often half a page recovered, which goes to projects.
Format, so it survives the software
Single column. No tables holding your work history, no text boxes, nothing important in the page header or footer — many parsers skip those entirely. Standard section headings. Dates in one consistent format. A text-based PDF, not a scan.
Test it in thirty seconds: open the PDF, select all, copy, paste into a plain text editor. That is roughly what the parsing software sees. If it is scrambled, the template is the problem.
Name the file Firstname-Lastname-Role.pdf. The full mechanics of how recruiters search, and why the exact words matter, are in ATS keyword matching for Indian roles.
What to do when nothing on the page feels like enough
Two things, and neither is more applications.
Build the one project. Pick a problem you personally have, build the smallest thing that solves it, put it somewhere it can be opened. Three weekends. It will do more for your search than another two hundred applications with the current resume.
Get one person to look at it. A senior from college who is now working, a cousin in the industry, anyone who has screened resumes. Fifteen minutes of their time surfaces things you cannot see in your own document.
Then apply in volume, because the response rate at this stage is genuinely low and that is a property of the market rather than of you. The realistic arithmetic — how many applications, over how many weeks — is in how long a job search actually takes, and there are fresher openings listed here and internships here.