How to Write a Resume With No Work Experience

Writing a resume with no work experience feels like being asked to prove something you haven't done yet. The standard template — reverse-chronological job history, each role with achievements — assumes a history you don't have, and staring at an empty Experience section is genuinely discouraging.

But the assumption underneath that feeling is wrong. Employers hiring for entry-level roles already know you haven't held the job. What they're screening for is evidence that you can do work: that you finish things, take direction, solve problems, and show up. That evidence exists in your life already — it's just not filed under "employment."

This guide covers how to find it, how to structure a page around it, and how to write it up so it reads as substantive rather than padded.

Reframe What Counts as Experience

The single mental shift that makes this easier: a resume documents demonstrated capability, not payroll history. A paid job is the most convenient proof of capability, which is why resumes default to it. It is not the only proof, and hiring managers for entry-level roles know that.

What counts, and is regularly undersold by the people who did it:

• Coursework with real output — a capstone project, a research paper with findings, a semester-long team build. Not "took a class in," but "produced X."
• Personal and side projects — an app, a website, a dataset analysis, a YouTube channel, a small business, a mod, a zine. Anything with an artefact at the end.
• Volunteer work — organising, coordinating, teaching, fundraising, managing a rota. This is unpaid work, not non-work.
• Student organisations and societies — especially any role where you handled a budget, ran an event, recruited people, or produced something on a deadline.
• Freelance and gig work — tutoring, design commissions, reselling, dog walking, content writing. Clients and deliverables are experience.
• Family and caregiving responsibilities that involved coordination, budgeting, or managing a business — a family shop, a farm, care logistics.
• Competitions and hackathons — placement is a bonus; participation with a finished submission is already evidence.
• Athletics and performance — sustained training, team roles, and captaincy demonstrate discipline and coordination in a way employers do read.

You are not writing a resume with nothing on it. You are writing a resume whose evidence happens to sit outside the Experience section — and your job is to move it in.

How to Structure the Page

With no employment history, the standard section order works against you — it puts your emptiest section highest. Reorder so the reader hits your strongest material first.

Two notes on this. First, don't rename Experience to something evasive — call the section Experience and put volunteer or freelance work in it with honest labels. Second, keep it to one page. Padding to reach a second page is more visible than a short, confident single page. Our guide on resume length by career stage covers why that's the right call here.

Mining Your Own History for Proof

Most people can't think of anything to write because they're searching their memory for "jobs." Search for these instead — write down everything, filter later:

1. Anything you finished that had a deadline. A dissertation, a group project, an event, a fundraising target.
2. Anything you built that another person used. A spreadsheet a society still runs on, a website for a friend's business, a script that saved someone time.
3. Anything you organised involving other people. Rotas, trips, tournaments, study groups, campaigns.
4. Anything you were trusted with. Keys, cash, a younger sibling's schedule, a club's bank account, a shift handover.
5. Anything you taught or explained. Tutoring, onboarding a new volunteer, running a workshop, writing documentation.
6. Anything you improved. A process that was slow, a document that was confusing, a system nobody had bothered to fix.

Aim for fifteen to twenty raw items. Then pick the four or five with the clearest outcomes and the most relevance to the roles you're targeting. The rest are interview material.

Writing Bullets That Don't Sound Like Padding

The difference between a project entry that reads as substantive and one that reads as filler is entirely in the specifics. Same underlying activity, written two ways:

• Padding: "Participated in a group project for my final year module, working with team members to complete the assignment."
• Substantive: "Led a four-person team building a course-scheduling tool in Python over eleven weeks; handled the constraint-solver logic and the weekly client check-ins with the faculty sponsor. Delivered on schedule and the department piloted it for one term."

The second one contains a team size, a duration, a specific technical responsibility, a stakeholder relationship, and an outcome. None of that is inflated — it's just not omitted.

Practical rules for every bullet you write:

• Open with a verb. Built, organised, taught, analysed, coordinated, wrote, launched. Never "Responsible for" or "Helped with."
• Include a number wherever one honestly exists. Team size, hours, attendees, weeks, revenue, downloads, percentage improvement. Estimates are fine if defensible.
• Name the specific thing you did, not the thing the group did. "Handled the constraint-solver logic" beats "worked on the project."
• State the outcome, even a modest one. Adopted, published, delivered, raised, reduced, presented to.
• Drop the pronoun. No "I" — resume convention implies it.

These are the same standards that apply to any resume; the difference is only where the material comes from. The wider set is in our guide to writing a resume that gets remembered.

The Summary Matters More Here Than Anywhere

With no job history to frame you, the opening three lines carry unusual weight. They tell the reader what to make of everything below before they've formed their own conclusion.

A weak version: "Recent graduate seeking an entry-level position where I can apply my skills and grow professionally." This says nothing and asks for something.

A working version: "Computer science graduate with a focus on data engineering and two years of coursework building production-style pipelines. Built a course-scheduling tool now piloted by the university's registrar office. Looking for an analyst role where I can keep working close to real data."

The structure is the same one that works at every career stage — identity, specialisation, proof, direction — just sourced differently. The full breakdown with examples is in our guide on writing the opening summary.

What a Finished Entry Looks Like

A projects section done properly reads almost exactly like an experience section:

Course Scheduling Tool — Final Year Project, University of Leeds · Sep 2025 – Dec 2025

• Led a four-person team building a Python constraint-solver that generates conflict-free timetables for 1,200 students across 84 modules
• Owned the solver logic and the weekly stakeholder check-ins with the faculty sponsor
• Cut manual timetabling effort from an estimated three weeks to under two hours; department piloted the tool for the spring term

Treasurer — University Cycling Club · Oct 2024 – Jun 2025

• Managed a £9,400 annual budget across equipment, travel, and event costs for 60 members
• Rebuilt the membership payment process onto an online form, ending a recurring cash-reconciliation problem and cutting admin time by roughly six hours a month
• Secured £1,800 in local sponsorship, the club's first external funding in three years

Neither entry is a paid job. Both read as work, because both describe scope, decisions, and outcomes.

What to Avoid

• Apologising for the gap. Never write "despite limited experience" or "although I am new to the field." Present what you have as what it is.
• Padding with filler sections. An "Interests" list of reading and travelling, an objective statement, "References available upon request" — all of these announce that you ran out of content.
• Listing coursework as a bare list of module names. "Relevant coursework: Data Structures, Algorithms, Databases" is weak. One project with an outcome beats ten module titles.
• Inflating titles. "Founder and CEO" of a project with no revenue and no employees invites scrutiny you don't want.
• Skill bars and rating graphics. They look designed and are invisible to automated screening systems. Plain text with an honest proficiency label works better — see our guide on which skills to list and how.
• Sending the same page everywhere. Entry-level applications are high-volume and heavily filtered, so keyword alignment with the posting matters more here, not less. Our walkthrough on getting past automated screening covers what the systems are actually matching.

Getting the first resume onto the page is the hard part. If you'd rather work from a structure than a blank document, the free resume builder prompts you section by section and outputs a clean, single-column layout. And once you have a draft, running it against a real job posting will show you which of the posting's requirements you're already meeting and which language you're missing — usually a faster route to a strong second draft than another hour of staring at it. The first check is free, and volume options are on the pricing page.

One last thing worth saying plainly: the resume gets you into the room. Nobody expects an entry-level candidate to have a decade of proof. They expect evidence that you can be given something and be relied on to do it. You almost certainly have that already — write it down properly and it will read that way.