How to Write a Resume When You Have No Work Experience

The first resume is hard for a reason that has nothing to do with writing. It is hard because the standard advice — quantify your impact, lead with achievements, show progression — assumes a career you have not had yet.

But the premise of "no experience" is almost always false. What is true is that your experience is filed under headings the resume format does not have. You have written a 12,000-word dissertation to a deadline. You have worked Saturdays in a shop for two years. You have run a society with a budget, or built something because you wanted to see if you could, or translated for a relative at appointments since you were fourteen.

None of that arrives labelled as professional experience. All of it is evidence, and the job of a first resume is to get it onto the page in a form a hiring manager recognises.

The order to put things in

The one structural decision that matters: when you have no employment history, education and projects move to the top. The conventional order — experience, then education — assumes the experience is the argument. Yours is not, yet.

A first resume runs roughly:

1. Header — name, city, phone, email, one link
2. Short summary — two or three lines, optional but useful
3. Education — including relevant coursework
4. Projects — academic, personal, or both
5. Experience — part-time, casual, volunteer, seasonal
6. Skills
7. Activities, leadership, awards — if there is room

If you have had two years of retail work alongside your degree, that section can move above projects. The rule is that whichever section is strongest goes first, not whichever section is more prestigious.

One page. Always, at this stage.

Education, done properly

More than the degree name and the year.

List the institution, the qualification, the graduation date — including an expected one if you have not finished. If your grade is strong, include it. If it is not, leave it out; an absent grade is unremarkable, a weak one stated is a decision.

Then add relevant coursework, which is the part most people skip. Not all of it — four to six modules that relate to the job. A finance role wants to see Corporate Finance, Financial Modelling and Econometrics. It does not want your full transcript.

If a module produced something real — a dissertation, a capstone, a lab project, a consulting brief for an actual client — give it a line of its own with what it was and what you found. That is a project, and it belongs in the projects section.

Projects, which are your work experience

For a first resume, projects do the job that employment history does later. They are also the only section where you control the difficulty of the material, which makes them the highest-leverage thing on the page.

Write them like jobs. A name, a timeframe, one line of context, and two or three bullets with outcomes.

If nobody used your project, that is fine — say what you built, what was technically hard about it, and what you learned from the part that went wrong. Honest specificity reads better than inflated claims, and interviewers ask about projects, so anything you overstate becomes a difficult ten minutes.

Personal projects count fully. A game, a bot, an analysis of a dataset you were curious about, an Etsy shop, a YouTube channel with real subscriber numbers, a mod, a translation. If you made it and can explain the decisions, it is evidence.

Part-time and casual work is not filler

There is a persistent belief that hospitality, retail and warehouse jobs do not belong on a "real" resume. Employers hiring for entry-level roles disagree, strongly, and for a specific reason: those jobs prove you turn up.

Reliability, working under time pressure, handling unhappy people, following process, and holding responsibility for money or safety are exactly what a manager taking a risk on a first hire is trying to establish. Write them as work, not apologetically.

Both of those describe casual work. Both describe someone you would hire.

Volunteering, family business work, caring responsibilities and student society roles follow the same rule. If you did the work, it goes on the page with dates. Treasurer of a society with a £4,000 budget is a finance role, and it should be described as one.

The summary, if you write one

Two or three lines, and only worth including if it says something specific.

Final-year economics student, graduating June 2026. Built a dashboard tracking regional unemployment against policy changes for my dissertation; two years of weekend retail work alongside study. Looking for a graduate analyst role.

That is orientation. It tells the reader what you are, when you are available, what you have made, and what you want — before they read anything else.

What to avoid is the version everyone writes: "Motivated and hard-working recent graduate seeking an opportunity to leverage my skills in a dynamic organisation." It is unverifiable, it is identical to every other applicant's, and it uses your best three lines to say nothing.

What to leave off

• Your full address. City and country is enough.
• Date of birth, marital status, photograph — unless you are applying in a country where it remains conventional.
• High school, once you have a degree or are well into one.
• Every module you took. Four to six relevant ones.
• "References available on request." It states the default and costs a line.
• Proficiency bars on skills you rated yourself.
• An objective that only says what you want. If you write anything at the top, make it about what you can do.

Applying without meeting every requirement

Entry-level postings routinely ask for two years of experience in a role that is supposed to be someone's first. That requirement is often aspirational, written by copying a previous posting.

Apply anyway if you meet most of it. What helps is addressing the gap directly rather than hoping it is not noticed — a cover letter is the right place, and one sentence is enough: name the thing you have not done, then name the closest thing you have. Our guide to writing a cover letter with no experience covers that in more detail.

What does not help is the functional resume format, which hides dates behind skill groupings. It is marketed at people in exactly your position and it makes recruiters suspicious, because they know why it gets chosen.

Before you send it

Read every bullet and ask whether it says what you did or what you were responsible for. First resumes are full of the second kind — "Responsible for assisting customers" — and converting them is the single biggest improvement available.

Then check the page holds together as one document rather than a collection of sections. If your projects, your Saturday job and your dissertation all point at the same kind of work, a reader will see a direction. That is what a first resume is really arguing.