May 9, 2026 · 3 min read

How to Write a CV with No Experience: Practical Guide

Step-by-step guide on writing a strong CV with no work experience: structure, keywords, transferable skills, and ATS-safe formatting that gets interviews.

Writing a CV with no formal work experience is a problem of perception, not content. Recruiters do not expect entry-level candidates to have a long history. They expect a focused, specific document that shows you can think, learn, and contribute fast.

This guide walks through the same structure professional career coaches use, adapted for the European market and ATS systems. The goal is not to fill space — the goal is to make your CV easy to scan and easy to trust on first read.

Why this matters more than the experience itself

Recruiters spend 6–8 seconds on the first screening pass. They look for three signals: clarity, relevance, and a sense that you have done something. With no jobs to list, these signals must come from the way you frame what you have done — academic projects, internships, volunteer work, side projects, certifications.

  • Replace generic statements ("hard worker", "team player") with concrete examples
  • Lead with what you built or delivered, not just what you attended
  • Use the same vocabulary as the job description so the ATS picks it up

The structure that works

  1. Header: name, email, phone, LinkedIn, city. No photo unless you target Germany or Italy.
  2. Summary: 2–3 lines stating who you are, what you can do, and what you are looking for. Specific.
  3. Education: degree, institution, expected/completion date, relevant courses or thesis.
  4. Projects: 2–4 academic, freelance, or personal projects with measurable outcomes.
  5. Skills: hard skills (tools, languages, frameworks) + soft skills with specific examples.
  6. Experience (if any): internships, volunteer roles, part-time jobs — formatted as real experience.
  7. Languages, certifications, awards: short, scannable.

When you have no experience, the Projects section is what carries the CV. Treat each project like a job: title, period, role, what you did, what changed because of it.

What to optimise first

  • Keyword match: paste the job description into our [ATS keyword scanner](/cv-builder) — your CV should match 60–80% of the technical terms.
  • Quantify everything you can: "tutored 12 students", "built a 200-user app", "raised €1,500 for charity".
  • Active verbs: built, designed, led, analysed, automated. Avoid "responsible for".
  • One page: with no experience, two pages signals padding. Stay to one.

Before and after

Before: Computer Science student passionate about technology and looking for opportunities to grow.

After: Computer Science student (final year, ISCTE) with 3 published Python side-projects. Built an open-source CLI used by 400+ developers. Looking for a junior backend role in a product team.

The second version makes a specific claim, backs it with proof, and tells the reader exactly what role you want. Same person, completely different signal.

Mistakes that get junior CVs rejected

  • Filling space with generic phrases that any candidate could write
  • Listing classes instead of skills you actually used in projects
  • Hiding the strongest project at the bottom of the page
  • Forgetting to match keywords from the job description
  • Using a fancy template that breaks ATS parsing

Quality checklist

  • A recruiter can identify your target role in 5 seconds
  • Each project shows what changed because of your work
  • Keywords from the job description appear naturally in skills and projects
  • The document is 1 page, readable on mobile, exports cleanly to PDF
  • No typos and no inconsistent date formats

FAQ

How do I list internships if they were unpaid?

List them under Experience exactly like paid roles. Title, company, dates, 2–3 bullet points with measurable outcomes. The ATS does not care if you were paid; the recruiter cares about what you delivered.

Should I include hobbies on a junior CV?

Only if they prove a relevant skill: a public GitHub, a published portfolio, competitive programming, language exchanges, organising student events. Skip "watching films".

Is one page really enough?

Yes — and recommended. With no experience, a one-page CV that is dense with proof beats a two-page CV padded with theory. Recruiters value clarity over volume.

Final takeaway

A CV with no experience wins by being specific, focused, and easy to trust. Pick the 4–5 strongest things you have ever done, frame them with measurable outcomes, and let the structure do the rest. Use [Textaris CV Builder](/cv-builder) to assemble it in 10 minutes, get an ATS score, and download a clean PDF.

Free tool

Try it yourself — no sign-up required.

📄 Try CV Builder →