Beginner · 9 min read
How to Write a CV with No Experience (and Still Get Interviews in 2026)
You don't need a job to have things worth putting on a CV. A practical guide for students, first-jobbers and career changers — written by someone who's read thousands of them.
"I don't have anything to put on my CV." I hear this from students, career changers, parents returning to work, and people who've spent five years in a job that didn't really do anything they want to talk about. It's almost never true. What's usually true is that you don't yet know how to translate what you've done into the language a recruiter recognises.
This guide is the version I wish I'd had at 21. It's also the structure ResumAI's chat builder uses under the hood when someone tells it "I have no experience" — the AI asks the right questions to surface things the user didn't think counted.
The lie hiding in "no experience"
When most people say "no experience," they mean "no full-time paid job in the field I want." Recruiters know that. For a junior role, a first job, or a career pivot, nobody expects ten years. What they're scanning for is evidence — any evidence — that you can do the basics of the role and that you'll show up.
Evidence comes from anywhere:
- Coursework, capstone projects, dissertations
- Internships, even one-day shadowing
- Part-time jobs (yes, the café job counts)
- Volunteering, student societies, tutoring
- Side projects, GitHub repos, blog posts, a YouTube channel
- Family business, helping a parent with bookkeeping, running a school event
- Online certifications (Coursera, Google, AWS, HubSpot)
If you breathed and did something, you have evidence. The job is to choose the bits that map to the role.
The structure that works for a no-experience CV
Forget the standard chronological format for a second. When you don't have a job history, lead with what you do have. The order that works:
- **Header** — name, one-line title, email, phone, city, LinkedIn, portfolio.
- **Summary** — 2 to 3 lines. Who you are, what you're aiming for, one credible signal.
- **Education** — degree, institution, dates, relevant modules, GPA only if strong.
- **Projects** — the heart of the CV. Each one a mini case study.
- **Experience** — even one part-time job. Frame transferable skills.
- **Skills** — tools, languages, frameworks. Keyword-rich.
- **Certifications, volunteering, languages** — round it out.
The summary is where most beginners blow it. "Motivated graduate seeking opportunity" tells a recruiter nothing. Try this instead: "Computer science graduate (Edinburgh, 2025) with two ML side projects in production and a 6-month internship at a fintech. Looking for a junior backend role in Python."
That sentence does work. It names the field, the recency, the proof, and the ask.
Writing project bullets when you've only built toy things
A side project is a job in miniature. Treat it that way. Three bullets max:
- What you built and why it matters (one line).
- The hard part you solved (one line, with a tool/framework name).
- The outcome — users, stars, grade, deployment (one line, with a number if you can).
Example:
> Recipe Finder — personal project (2025) > - Built a full-stack recipe app in React + FastAPI that suggests meals based on ingredients on hand. > - Implemented fuzzy-matching with PostgreSQL trigram indexes after the naive query hit 800ms. > - Deployed to Railway, 120 weekly users from a Reddit post, 4.6/5 average rating.
That bullet is stronger than half the "professional experience" sections I read. Numbers, tools, outcome, evidence.
What to do with the part-time café job
Don't hide it. Reframe it. A recruiter for a graduate scheme is not looking down on retail — they're looking for signal that you can show up, deal with humans, and not crumble under pressure.
> Barista — Costa Coffee, Manchester (2023–2025, part-time) > - Handled 200+ transactions per shift in a high-volume city-centre store. > - Trained four new starters and wrote a one-page onboarding doc adopted by the store manager. > - Promoted to shift supervisor after eight months; ran a team of three.
That's leadership, ownership, training and operational pressure — the exact things graduate-scheme assessors probe for at interview.
The skills section is keyword bait — use it that way
ATS systems and human recruiters both scan this section first. Mirror the language of the job ad. If the ad says "TypeScript, React, Node.js, AWS Lambda, REST APIs," your skills section should say exactly that — not "JavaScript frameworks and cloud experience." Specificity wins.
Don't lie. Don't pad. But if you genuinely have brushed against a tool, name it.
What to skip
- Photos. (Unless you're applying in a country where it's standard — most of Europe says no in 2026.)
- Date of birth, nationality, marital status.
- "References available on request." Everyone assumes this.
- Hobbies, unless they're remarkable (competing nationally, running a non-trivial side project).
- A two-page CV. One page is plenty when you have no experience.
How AI helps when you genuinely don't know what to write
The hardest part for a first-time CV writer isn't formatting — it's interviewing yourself. You don't know which of your stories matter. This is what a good AI chat builder is for: it asks the questions, you answer in plain English, it converts the answers into structured bullets with action verbs and numbers.
If you'd rather not stare at a blank template, [start with the ResumAI chat builder](/ai-cv-builder) — it takes about five minutes, costs nothing, and you walk out with an ATS-safe PDF.
The mindset shift
A first CV isn't a record of your career. It's a pitch deck for one specific role. You're not summarising your life; you're arguing that you can do this job. Choose the evidence that backs that argument and cut the rest.
You have more material than you think. The job is to translate it.