How to Write a CV With No Experience (Students, Graduates & Career Changers)

If you've never had a full-time job — or you're applying to a field where your past roles don't translate — you are not at a disadvantage as long as your CV is built for the situation you're actually in. The biggest mistake first-time CV writers make is trying to imitate a CV designed for someone with ten years of experience. That format is built around a thick Work Experience section. Yours isn't. You need a different shape entirely. This guide gives you that shape — what sections to use, what to put in them, and how to make a junior CV that lands without pretending to be senior.

What a no-experience CV actually has to do

Senior CVs are built to differentiate among candidates with similar track records — the question is "who's the strongest?". Junior CVs are built to answer a different question: "can this person actually do the job and learn the rest fast?". Knowing that recruiters are reading for that signal changes what your CV needs to demonstrate.

  • Concrete proof you can produce work — even small projects beat zero projects
  • Signs of initiative — that you'll do the work without being asked, which is the single thing junior recruiters are screening for
  • Evidence you'll learn quickly — recent learning, certifications, side projects all count
  • Communication that doesn't apologise for inexperience — confidence at the junior level reads as professionalism, not arrogance

Notice what's not on that list: years of experience, fancy titles, big-name employers. A junior candidate doesn't need those to compete; they need to demonstrate the four things above clearly and confidently. The CV format below is engineered to do exactly that.

The reshaped layout — different sections, different order

A junior CV's order of sections matters more than a senior CV's. The structure that works:

Top of page — name, contact, summary

Same as any CV: name, professional email, phone number, city, LinkedIn URL. Below that, a 2-3 sentence summary that owns where you are (more on this in the next section).

Education — moved near the top

Conventional CVs put education at the bottom. Junior CVs put it second, right under the summary. Include your degree, institution, expected or actual graduation date, and one or two strongest coursework topics if they map to the role. Skip GPA unless it's above 3.7/4.0 or your local top-decile equivalent. Drop high school entirely unless you're still in your first year of university.

Skills — early and prominent

Skills carry more weight on a junior CV than on a senior one. List the tools, languages, frameworks, or methodologies relevant to the role. Be honest about levels — „Python (proficient, 3 years), Go (learning, 6 months)" reads better than over-claiming and getting caught in a technical interview.

Projects / Coursework / Selected Work — the heavyweight section

This is where you put what you've built. University capstone projects, freelance work you did informally, open-source contributions, hackathon entries, a side business, a YouTube channel, a research paper, anything you built or contributed to that has a concrete output. Treat each project the same way someone with experience treats a job: a title, a date range, two or three bullets describing what you did and what it produced.

Experience — whatever you have

Part-time jobs, internships, freelance gigs, volunteer roles, university leadership positions. Don't gate this section behind „real" jobs only — anything where you did work for someone counts. Frame the work in skill-transferable language (the section below shows how).

Optional sections — certifications, languages, interests

Add only if substantive. Certifications: useful if relevant to the role (AWS, Google Analytics, language proficiency). Languages: useful if the role values them. Interests: include only one line if anything you do outside class genuinely reveals something useful (open-source maintainer, competitive runner, blog with real readership). Skip the generic „reading, traveling, music" filler.

How to write the summary when you don't have a job title

The hardest part of a junior CV is the summary, because the usual formula („Senior X with N years…") doesn't apply. The replacement structure: who you are academically, what you've already done that's relevant, what you're looking for next.

  • Computer-science graduate example: „Recent computer science graduate with strong fundamentals in distributed systems and three end-to-end side projects deployed in production. Looking for a backend engineering role where I can learn from a senior team while shipping production code from day one."
  • Marketing graduate example: „Marketing graduate (BSc, 2026) with two summer internships at consumer-brand agencies and a 2,000-subscriber personal newsletter on indie brand strategy. Looking for an associate marketing role at a consumer-brand company where I can apply campaign and content skills."
  • Self-taught/career changer example: „Self-taught developer with 18 months of nights-and-weekends learning (Stanford CS courses + 5 deployed projects + active Stack Overflow contributor). Looking for a junior software engineering role where I can transition formally into the field after a decade in adjacent work."

Notice what each summary does: owns the level without apologising, names concrete proof (project counts, follower numbers, course completions), and ends with a forward-looking ask. Three sentences, no buzzwords, no padding. The recruiter knows in 8 seconds whether you're the right shape of candidate.

The full structure that makes the junior-level summary land

The Projects section — the most important thing on the page

For a no-experience CV, the Projects section does the work that the Experience section does on a senior CV. Get this section right and the rest of the CV becomes supporting context; get it wrong and even the best summary won't save you.

What counts as a credible project for the Projects section:

  • University capstone or final-year project, with the topic and outcome named
  • Personal coding projects with public artefacts (GitHub repo, deployed site, mobile app store listing)
  • Hackathon entries — even ones that didn't win, if you built something that ran
  • Freelance or informal client work, even very small — building a website for a local business counts
  • Open-source contributions to a project anyone else uses
  • Research projects, including unpublished work with supervisors
  • Side businesses, even small ones — an Etsy shop, a small newsletter, a YouTube channel with real subscribers
  • Competition entries — Kaggle, design challenges, case competitions

How to format each entry: project title (bold), date range, one line of context (what it was), then 2-3 bullets describing what you did with action verbs and any measurable outcomes. Example: „Personal Finance Tracker (open-source) — Jan 2025-present. Built a self-hosted personal finance app in Go with React frontend; reached 800 GitHub stars, used by 200+ self-hosters; wrote complete documentation that gets cited in r/selfhosted threads."

How to quantify project outcomes when the work isn't formal employment

Transferable skills from non-traditional sources

Junior candidates often have more credible work experience than they realise — they just haven't been trained to label it. The work you did in non-corporate settings often demonstrates exactly the skills the corporate role needs. Five common sources and how to mine them:

Retail, hospitality, food service jobs

What you actually did: customer communication under pressure, problem-solving in real time, cash handling and accuracy, training new staff, escalation to management. All of this maps directly to corporate-role competencies — frame each bullet in the language the new role uses.

  • „Trained 6 new joiners during summer peak season" → demonstrates teaching, onboarding, leadership
  • „Resolved customer complaints under SLA pressure" → demonstrates communication, problem-solving
  • „Cash handling accuracy of 99.8% over 18 months" → demonstrates attention to detail, reliability

University clubs, societies, sports teams

Leadership roles in student organisations are real management experience. The fact that nobody paid you doesn't make the work less valid — it makes it more impressive, because you did it without external incentive.

  • „President, 200-member debating society — coordinated weekly meetings, organised three national competitions" → leadership, organisation, project management
  • „Captain, university rugby team — led 25-player squad through two-season campaign" → leadership, team dynamics, performance under pressure

Tutoring or teaching

If you tutored peers, younger students, or worked at a tutoring centre, that's communication, simplification of complex material, patience, and structured thinking. All four are corporate skills the new role likely needs.

Volunteering

Volunteer work with a named organisation counts as real experience. „Coordinated weekly food distribution for 300+ families at [organisation], scheduled 12 volunteer shifts per week" is operations and logistics experience that maps directly to many corporate roles.

Side projects you didn't think of as work

Maintaining a popular Discord community, running a small newsletter, building a Notion template that 5,000 people downloaded, helping run a local meetup. Anything where you built something other people used or interacted with counts as work — name it, frame it, put it in.

Action verbs that make informal experience read as real work

Initiative signals — what disproportionately helps juniors

Recruiters hiring for junior roles are largely screening for one thing: will this person do the work without being told to? Anything on your CV that proves you've already done that — outside school, outside paid work — disproportionately helps. Five signals to consider including:

  • GitHub link with 3+ real projects (not just course exercises) — single biggest signal for engineering/data candidates
  • Blog or published writing with consistent output — even 10 posts written over 6 months proves you can ship
  • Open-source contributions to projects others use — even small PRs to popular repos count
  • Conference talks, meetup presentations, community workshops — signals you can communicate beyond your immediate team
  • A small business, paid newsletter, podcast with real audience — initiative made tangible

You don't need all five — one credible signal is more than enough. The presence of any one of these on a junior CV often moves the candidate from „looks fine" to „let's talk to them". The artefact itself does the convincing; the CV just has to surface it.

What to leave OFF the no-experience CV

Junior CVs often get padded with filler that signals inexperience more loudly than the lack of experience itself. The patterns to cut:

  • High school details — beyond your first year of university, school name and exam grades don't add anything
  • Generic skills like „Microsoft Office", „team player", „good communicator" — every applicant has these; listing them signals you don't have stronger material
  • GPA below the top decile — if you're not above 3.7/4.0 (or local equivalent), skip the number; if you're at a top university, the institution name does the work
  • Long objective statements — „seeking a challenging position where I can grow…" wastes the most valuable space on the page
  • Hobbies listed without any specificity — „reading, music, traveling" tells the reader nothing. If a hobby is genuinely relevant (open-source contributor, competitive athlete, published photographer), keep it; otherwise cut
  • References — assumed by default since 2005, never include the line „References available on request"
  • Padding sections — don't invent „Achievements" or „Awards" if you have none. An empty section reads as denial of the gap
More junior-CV patterns that quietly hurt applications

Where to apply when you have zero experience

The CV format above gets you into the screening pool. Knowing which pool to apply to matters as much as the CV itself. Four entry-level routes that work disproportionately well for no-experience candidates:

  • Formal graduate schemes — large employers (banks, consultancies, big tech, professional services) run structured grad programmes specifically for no-experience hires. Higher acceptance rates than cold applications and built-in training
  • Internships first, full-time later — a paid 3-month internship is often the highest-conversion path to a full-time entry-level role, especially in tech, finance, and consulting
  • Apprenticeships and trainee programmes — increasingly available in tech (Microsoft, Google), finance (Goldman Sachs apprenticeships), and trades. Combine on-the-job learning with formal training
  • Smaller companies before bigger ones — startups and SMBs are more willing to take chances on no-experience candidates than large corporates with formalised hiring processes. The downside is less structured onboarding; the upside is faster responsibility growth

Cold-applying to entry-level openings at large companies without going through a grad scheme is the lowest-percentage route. Use it, but lean heavier on the structured routes above. The candidates who land roles fastest after graduation usually went through some combination of internships, grad schemes, and small-company first jobs — not just cold applications.

How to tailor your CV to each of these application routes

Pre-send checklist for no-experience CVs

  • Education near the top (under summary), not at the bottom
  • Skills section above experience
  • Projects/Coursework/Selected Work section exists and contains at least 2 substantial entries
  • Every project entry has measurable outcomes or concrete artefacts named
  • Non-traditional work (part-time, volunteer, club leadership) framed in transferable-skill language
  • At least one initiative-signal element (GitHub, blog, side business, conference talk)
  • Summary owns the junior-level status without apologising
  • High school details cut (unless first-year university)
  • Generic skills ("Microsoft Office", "team player") removed
  • GPA included only if top-decile; otherwise institution name does the work
  • One page total (junior CVs over one page almost always have padding)
  • Filename: FirstName-LastName-CV.pdf

A no-experience CV done well looks intentionally junior, not desperately senior. The shape is right, the projects do real work, the non-traditional experience is properly framed, and the summary owns the situation. Done right, you don't compete with five-year-experienced candidates — you compete with other juniors, and you win on substance because most of them are still imitating the wrong format.

Ready when you are

You've got the knowledge. Now build the CV.

Take what you just read and turn it into a CV that actually gets responses. Pick a template, start typing, and we save your work as you go.