Every resume guide assumes you already have something to put on it. If you are in your final year, or six months past graduation and still waiting for the first call, that advice is useless. You are not short of a job description. You are short of a job.
Here is the thing worth knowing before you write a single line: a first resume is not a weaker version of an experienced one. It answers a different question. An experienced resume answers "what have you delivered?" Yours answers "what can you clearly already do, and will you be worth training?" Those are different documents. Most fresher resumes read as apologetic because they are trying to be an experienced candidate's resume with the experience missing, when what the reader needs is a fresher's resume done well.
The order to put things in
For most freshers, this order works:
- Contact details — name, phone, email, city and state
- Education — degree, institution, year, CGPA or percentage
- Projects — your strongest two or three
- Internships — if you have any
- Skills — grouped, not a list of forty
- Certifications — if they are relevant to the role
Treat that as a sensible default, not a rule. If something you have built speaks directly to the job — you are applying for a data role and you have done real work with data — put projects above education so the strongest thing is read first. The order should follow whatever makes your case fastest, and the rest of this guide is about filling each section honestly.
You have more than you think, and none of it needs inventing
Before worrying about layout, list what actually exists:
- Degree, college, and your CGPA or percentage exactly as your institution
reports it
- Semester and final-year projects, including group ones
- Internships and industrial training, however short
- Certifications and courses you genuinely finished
- Positions of responsibility — class representative, fest organising
committee, club secretary, NSS or NCC
- Technical skills you could demonstrate if someone sat you down today
- Languages you actually speak, read or write
That list is your raw material. If it feels thin, the problem is usually description, not substance.
One rule holds over everything that follows: do not invent. Not a metric, not a tool you have only heard of, not an internship that was really a two-day workshop. Not a number you cannot explain. It is tempting when the page looks empty, and it is the single worst decision available to you, because the interview is where it unravels. An interviewer who asks "walk me through how you measured that" and gets silence has learned something far more damaging than inexperience. A modest resume you can defend line by line beats an impressive one you cannot.
Education, and why it sits near the top
By default, education goes directly below your contact details — with no work history, it is the most concrete thing you have. Include your degree, specialisation, institution, graduation year and your score. Use the format your college actually uses: if your marksheet says CGPA 8.4, write CGPA 8.4, not a percentage you converted yourself with a formula you found online.
Once you have a year or two of real work, experience moves above education and stays there. This is temporary, and that is fine.
Your projects are your experience section
This is where most fresher resumes are won or lost, and it is almost entirely a writing problem. Compare these two lines describing identical work:
Made a website using React.
Built a four-page site in React for our inter-college fest, including the registration form that collected entries for the events.
The second is not inflated. No number was added, no claim was stretched. It simply says what the thing was, who it was for, and which part you were responsible for — three facts the writer already knew and left out.
Do that for each project:
- What was it, in one concrete phrase
- What did you personally build or decide
- What did you use to build it
- What happened to it — used by a club, submitted for evaluation, deployed,
presented
If a project genuinely has a number attached — a dataset size, a user count from a club that actually used your tool — include it. If it does not, say what it was without one. An honest sentence with no metric is stronger than a metric nobody believes.
Group projects deserve a note: write your part, not the team's. "Handled the backend API and database schema for a three-person final-year project" is more useful and more honest than claiming the whole system.
Internships and training, described honestly
A six-week internship is a six-week internship. Give the organisation, the dates, and one or two lines on what you were actually given to do. If it was mostly observation, describe what you observed and what you learned to use — that is a real answer, and it is better than inflating shadowing into ownership.
Avoid the trap of dressing up a certificate course as an internship. The two are different things, and the difference tends to surface in the first question about what you actually did day to day.
Skills: group them, do not list forty
A wall of forty comma-separated technologies tells a reader nothing, because the reader cannot tell what you can use from what you have only heard of. Group them instead, and be willing to defend every entry:
- Languages: Python, Java, SQL
- Web: React, Node.js, REST APIs
- Tools: Git, Postman, Excel
Three or four honest groups beat an exhaustive list. A good filter: if an interviewer opened your laptop and asked you to do something small with it, would you be comfortable? If not, it does not belong there yet.
Ready to lay this out properly? Choose a template and start filling it in — the builder is free to use, and you only pay when you download.
One page, and what to cut first
For a first resume, one page. Not as a style preference but because a second page of a fresher resume is almost always padding, and padding reads as padding.
Cut in this order: declaration blocks, "References available on request", hobbies that say nothing ("reading, music"), your father's name, marital status, and your full postal address. City and state are enough. These sections are often unnecessary for a private-sector fresher resume; use the space for a relevant project instead. Check the application instructions before removing anything explicitly requested.
Formatting that survives being read by software
Some employers run applications through software before a person reads them, and you usually cannot tell which. You do not need to game that, and you should be suspicious of anyone promising a score for doing so. A few practical habits cover it:
- One column. Multi-column layouts can be read out of order
- Real text, never a screenshot of text
- Standard section headings — Education, Projects, Skills, Internships
- Dates in a consistent format throughout
- A PDF, unless the posting explicitly asks for something else
- A sensible filename: your own name, not "resume_final_v3"
If you want a layout built for exactly this, the Directline template is the one in our set tagged for campus placements, and it is a single-column design.
The checklist before you send it
- Phone number and email are correct — read them out loud and check
- Your email address is a professional one
- Every date is consistent and nothing overlaps oddly
- Your CGPA or percentage matches your marksheet
- Every skill listed is one you could use today
- Every claim is one you can discuss for two minutes without strain
- No spelling mistake in your own degree, college or the company name
- It is one page
- It is a PDF, and it opens correctly on a phone
- The filename is your name
That last set matters more than any formatting trick. A resume with a wrong phone number is not a resume.
Start from the version you can defend
Your first resume will be shorter than you want it to be. That is not a flaw to be concealed; it is accurate, and accuracy is the only thing that still holds up in the room. Write the version you can defend, send it, and update it the moment you have something real to add.
Build yours now — free to write, ₹99 once when you download, and no subscription.