How to Write a First Resume When You Have No Work Experience
You have more material than you think. The problem is usually not a thin resume — it is a vague one.
Meera Prasad
Head of Career Development, Osmania Institute of Technology
28 August 20266 min read

Almost every student who says "I have nothing to put on my resume" is wrong. What they usually mean is that nothing they have done came with a job title. That is a different problem, and it is fixable.
Start with what you actually did
Before you open a template, write a plain list of everything you have spent more than twenty hours on in the last two years. Coursework projects. The fest you helped organise. The dataset you cleaned for a professor. The app you abandoned halfway. The tutoring you did for two juniors.
That list is your raw material. It will feel unimpressive because you were there for all of it. A reader was not.
The bullet that gets read
Most student resume bullets describe a category of activity. Employers cannot do anything with a category.
Weak: Worked on a college project using Python.
That sentence tells a reader nothing about scale, difficulty, or what you contributed. Compare:
Better: Analysed 18 months of hostel mess records in Python and found that Wednesday wastage was three times the weekly average; the committee changed the menu after the report.
The second version is the same project. What changed is that it contains a number, a method and an outcome. You are not exaggerating — you are being specific.
Try this structure for each bullet:
- What was the situation or the size of it
- What you personally did
- What changed because you did it
If nothing changed, say what you learned instead. An honest "the app was never adopted, and the reason was that we designed for students when the drivers were the real users" is more impressive than a vague claim of success.
What to do about the gaps
Two things students hide, and should not:
Coursework. A well-described academic project is legitimate experience. Describe it the same way you would describe work.
Failed projects. A project that did not work, described honestly with what you would do differently, reads as maturity. Hiring managers for early-career roles are not expecting a track record. They are looking for evidence that you can think about your own work.
Formatting rules that matter
Everything else is noise, but these three are worth the effort:
- One page. You do not have two pages of material yet, and a padded second page is obvious.
- Reverse chronological within each section, and consistent date formats throughout. Inconsistency reads as carelessness.
- No skill bars. A bar that says you are "80% proficient in Python" communicates nothing, and reviewers know it.
Before you send it
Read every bullet and ask: could this sentence appear on someone else's resume without changing a word? If yes, it is too generic. Add the detail that makes it yours.
Then give it to someone who does not know your work — a friend from a different department is ideal. Ask them to tell you what you did, from the resume alone. Where they hesitate, rewrite.
The goal of a first resume is not to look experienced. It is to make a busy reader understand, in about twenty seconds, that you are specific about your own work. That is rarer than experience.
- Resume
- First Job
- Internships
Put this into practice
Build your profile, generate a resume from it, and see which open opportunities you actually match.

