What to Put on a Resume When You Have No Work Experience
No internships, no job history, one page to fill. Here is what genuinely belongs on a fresher resume, in what order, and what to leave out.
The hardest resume to write is your first one, because the section everyone tells you matters most — work experience — is the one you do not have. The instinct is to pad: list every subject studied, every workshop attended, every software you have opened once. That produces a page that is full and still says nothing.
A recruiter hiring a fresher is not looking for experience. They know you do not have it. They are looking for evidence that you can build something, finish something, and explain it.
The order that works
- Header: name, phone, email, city, and links (GitHub, LinkedIn, portfolio) if they contain something worth seeing.
- A two-line summary naming your degree, what you can build, and the role you want.
- Education, with your degree, institution, year and CGPA or percentage.
- Projects. For a fresher this is the most important section on the page.
- Skills, grouped and honest.
- Internships or training, if any.
- Achievements, positions of responsibility, certifications.
Projects sit above skills deliberately. A skills list is a claim; a project is the evidence for it. Readers who are deciding quickly want the evidence.
How to write a project entry
Three lines each. What it does, what you built it with, and what actually happened — a result, a scale, a deployment, a user count, a problem solved. A project with no outcome reads as a tutorial you followed.
Weather App — Created a weather application using React and an API. Learned about API integration and state management.
Weather App (React, OpenWeather API) — Shows a seven-day forecast for any city with offline caching so repeat lookups work without a network. Deployed on Netlify; used by about 40 classmates during the semester.
Both describe the same project. The second one tells a reader you thought about a real problem (offline use), shipped it somewhere public, and that other people used it.
If you have no projects yet
Then that is the task before the resume. Two weekends produces something worth writing about, and it does not need to be original. Rebuild a tool you already use, automate something tedious in your own life, or take a public dataset and answer one specific question with it. Put it on GitHub with a README that explains what it does and why.
A resume cannot manufacture evidence that does not exist. It can only present it well.
On skills lists
Group them so a reader can scan: languages, frameworks, databases, tools. And apply one filter before anything goes on the list — could you answer questions about this for five minutes without preparation? If not, remove it. A padded skills list is not a neutral risk, because the first technical round will select from exactly that list.
Drop the proficiency bars and star ratings too. They compress a complicated thing into a number nobody trusts, they mean different things to different readers, and graphical elements frequently do not survive parsing.
What to leave off
- Photo, date of birth, marital status, father’s name, full postal address. City and state are enough.
- Class 10 and 12 marks once you hold a degree, unless a specific employer asks for them.
- Declaration statements and signature lines. Nobody verifies them and they consume space.
- "Hobbies: reading, listening to music, travelling" — unless a hobby is genuinely relevant to the role.
- Every workshop and seminar attended. Attendance is not achievement.
One page, always
With no work history there is no honest way to fill two pages, and a reviewer will read the second one as padding. Cut until the strongest material is what remains.
ThunderCV has fresher-specific templates that put education and projects above experience by default, so the layout matches the order above without rearranging sections yourself.