How to write a resume with no work experience

If you're a student, a new graduate, a career-changer, or someone returning to work after a long gap, the standard resume advice — "lead with your most recent role" — assumes a thing you don't have. Most templates don't help. The blank Work Experience section stares back, and it's tempting to either fluff one entry into looking bigger than it was or give up and submit a sparse CV that won't get read.

Neither is necessary. A resume with no formal work experience is still a resume — it just uses different evidence. This guide is the structure that works.

Reframe: from "work experience" to "evidence of capability"

The thing a recruiter is actually looking for isn't a list of jobs. It's evidence that you can do the work. Formal employment is the most common kind of evidence, but it's not the only one. The other kinds — projects, coursework, freelance, volunteering, leadership in student or community organisations — are entirely valid material for a resume. The trick is to promote them into the structural slots a traditional resume reserves for jobs.

Concretely: where a senior PM has an "Experience" section with five roles, a recent graduate might have an "Experience" section with two internships, one substantial open-source project, one technical lead role in a student org, and a self-initiated freelance gig. Same section. Different evidence.

The recruiter doesn't penalise you for the change of evidence — they penalise you for the gap a missing section creates.

The new-grad / first-job structure

A structure that consistently works for resumes without traditional work experience:

1. Contact info — name, email, phone, LinkedIn, GitHub or portfolio link if relevant.
2. Summary (2 lines) — what you're aiming for and the strongest piece of evidence you have.
3. Education — degree, institution, graduation date, and 2–3 bullets if relevant (relevant coursework, thesis, GPA only if 3.5+).
4. Experience — internships, substantial projects, leadership roles, freelance work, anything that involved producing a result. Bulleted the same way a senior resume's experience would be: Verb + Action + Result.
5. Projects (optional separate section) — for technical roles especially, 2–4 portfolio projects with a 1–2 line description and a link.
6. Skills — tools, languages, frameworks.

Order matters. For most early-career applications, Education above Experience is correct because the degree is your strongest single credential and you want it on page 1 above the fold. For technical roles where you have a strong portfolio, swap Education and Projects — let the work speak.

Writing the summary when you don't have a job title

The standard summary template — "Senior [role] with N years in [domain]" — doesn't work yet. The early-career version replaces seniority with direction and capability:

Computer-science senior at [University], graduating June 2026. Most recently built and shipped a Rust CLI used by 200+ developers in the open-source community, looking for a backend engineering internship for summer 2026.

What this summary does in two lines:

• Says what you are (CS senior)
• When you're available (June 2026)
• One specific piece of evidence (a real shipped project with a number on it)
• What you want (backend engineering internship)

Notice it doesn't say "passionate about coding" or "eager to learn". Those are filler. The shipped Rust CLI is the evidence; the rest of the resume confirms it.

Filling the Experience section with non-job evidence

Here's where most candidates undersell. Each of the following is legitimate Experience-section material, if you write it like an achievement:

Internships

Software Engineering Intern, [Company] (Jun – Aug 2025) Shipped two production features in a 12-week internship: a transaction-export endpoint adopted by three internal teams and a database connection-pool fix that reduced p95 query latency 18%.

Open-source projects

Maintainer, [Project Name] (2024 – present) Built and maintain a Rust CLI for parsing tax-form CSVs, with 200+ weekly downloads and 14 external contributors. Wrote the test infrastructure (90% coverage), the documentation, and the release pipeline.

Course projects (when substantial)

Final-year project, [University] (Sep 2025 – Apr 2026) Designed and implemented a distributed key-value store as a four-person team — built the consensus layer (Raft), wrote 8,000 lines of Go, and presented to a faculty panel that graded the project 92/100.

Student leadership

President, [Student Society] (2024 – 2025) Grew membership from 45 to 130, raised £8,000 in sponsorship for the annual hackathon, and built the volunteer team that ran it (35 volunteers across 4 functional areas).

Freelance / contract

Freelance web developer (2024 – present) Designed and shipped 5 small-business websites end-to-end (Webflow + custom CMS integrations), averaging 3-week turnaround and £1.2k per project.

Each entry uses the same Verb-Action-Result structure as a senior resume. The format is identical; the content is what changes.

What if you genuinely have very little?

If you're early-college or returning-to-work and you don't yet have substantive projects, leadership, or freelance to fill the experience section, the answer is: go produce some, fast. A focused 4–6 weeks of project work — even just one substantial side project taken seriously — gives you a resume entry that signals capability better than three half-relevant short-term gigs.

Specific things that work:

• Build something small, shippable, and documented. A Chrome extension, a Discord bot, a simple SaaS tool. The shipping and documentation are what counts; the project size doesn't have to be big.
• Contribute to one well-known open-source project. Two or three accepted PRs to a popular repo is more credible than a year of "Personal Project (no link)".
• Volunteer for a real organisation. Not "I helped my church with the website" — "redesigned the booking flow for [nonprofit], increasing event registrations 38% in the first quarter".

In four to six weeks of focused work you can produce one resume-worthy entry. That entry will outperform a year of fluff.

The career-changer variant

If you're changing careers — say, from teaching to software engineering, or marketing to data analytics — your work experience isn't empty. It's categorised wrong. The fix isn't to hide your old career; it's to translate the parts that transfer:

• A teacher applying for a product role: emphasise curriculum design (user research), stakeholder management (parents, admins), measurable outcomes (test-score improvements).
• A marketing manager applying for data analytics: emphasise A/B testing, cohort analysis, SQL exposure, dashboard ownership.
• A consultant applying for product management: emphasise stakeholder alignment, scoping, the structured project work, and any technical exposure.

The structure is the same as the rest of this guide — Verb-Action-Result — but with the relevant subset of your existing achievements promoted to the top of each role.

The honest summary

A resume with no traditional work experience isn't a blank document. It's a resume with different evidence, and the structure is the same one a senior PM uses: a strong summary, a substantive Experience section (with non-job entries written like job entries), and a clean Skills section.

The mistake to avoid is trying to look like a senior resume that's missing pieces. You'll lose against actual senior candidates and look weak against your peer set. Own the format that fits your situation, and write the entries with the same rigour a 10-year veteran would.