You have more to work with than you think. Here's how to actually show it.

There's a particular kind of dread that sets in when a job application asks for your CV and the honest answer to "what experience do you have" is very little, or none at all. It feels like being asked to build a house with no bricks. But this fear is based on a misunderstanding of what a skills section is actually for. It was never meant to be a list of jobs you've held. It's meant to be evidence of what you can actually do, and that evidence exists in far more places than a payslip. Coursework, class projects, volunteering, a part-time gig, a personal project you built out of curiosity, even the way you organised a family event, all of it can be genuine, defensible evidence of real skill, if you know how to present it properly.

The good news backed by actual research on how CVs get read: recruiters scan a resume in roughly 7.4 seconds on the first pass, and the skills section is one of the very first things they look at. That's not bad news for someone with little experience. It's an opportunity. A tight, specific, well-evidenced skills section can do more work in those seven seconds than a thin, apologetic work history ever could, precisely because it's the part of the CV a recruiter is scanning for first.

Start by Understanding What You're Actually Being Asked to Prove

Before listing a single skill, it helps to separate the two categories a hiring manager and an ATS are both quietly checking for.

Hard skills are specific, teachable, and usually measurable: a software tool, a language, a certification, a technical method. These are what most Applicant Tracking Systems are scanning for first, and they matter enormously at the very first filtering stage, since a large share of resumes never make it past this initial keyword screen at all.

Soft skills are the interpersonal, behavioural traits, communication, adaptability, teamwork, problem-solving, that decide whether you actually get invited to interview once a human is reading. ATS software can technically recognise soft-skill keywords, but weighs them far less heavily than hard skills, and a resume that leans too heavily on soft skills alone tends to read as vague rather than credible.

The practical implication for someone with little experience: hard skills get you noticed by the filter, soft skills, proven rather than just claimed, get you taken seriously by the human reading afterward. You need both, in the right proportion, and neither should be a guess.

Where to Actually Find Skills You Didn't Know You Had

This is the part most guides skip past too quickly. If you're staring at a blank skills section convinced you have nothing to put there, work through these sources deliberately, one at a time, before concluding you have nothing to add.

Your coursework and academic projects. A final-year project, a group assignment, a dissertation, a case study you presented to a class, these are genuine evidence of applied skill, not just "school stuff." If you used Excel to analyse survey data for a class project, that's a real, specific, hard-skill claim, not a filler line.

Internships, industrial attachments, or SIWES placements. Even short or informal placements count as real experience. What matters is describing what you actually did there, not just that you were present.

Volunteer work and community involvement. Organising an event, managing a small budget, coordinating a group of people, this builds exactly the kind of transferable skill (project coordination, communication, stakeholder management) that a paid role would also build, and it counts as legitimate evidence when described specifically.

Part-time or informal work, even work that doesn't feel "professional" enough to mention. Running a small side business, tutoring, freelance graphic design for a friend's shop, managing a social media page for a family business, all of these demonstrate real capability if described with the same rigour you'd apply to a formal job.

Self-directed learning. In 2026, online certifications are taken seriously by employers precisely because they show initiative. A completed course on Google Analytics, a Coursera data science specialisation, a LinkedIn Learning programme, these are legitimate, listable evidence of both a specific hard skill and the soft skill of self-motivation.

Leadership roles outside formal employment. Leading a student society, captaining a sports team, organising a church or community programme, these all generate real, describable leadership and organisational evidence.

The underlying principle: a skill doesn't become real only when someone paid you to use it. It becomes real when you can describe, specifically, a situation where you applied it and something happened as a result.

How to Actually Write Them, Not Just List Them

This is where most CVs with little experience go wrong, not in having too little to say, but in saying it too vaguely.

Be specific, not generic. "Good communication skills" tells a recruiter nothing, because every single applicant writes some version of the same sentence. "Presented research findings to a class of 40 and a panel of two lecturers" tells them something real. The test worth applying to every line: could literally anyone else applying for this role have written the exact same sentence? If yes, it's too generic to be useful.

Attach evidence to every claim wherever possible, ideally with a number. Instead of listing "Excel" as a bare skill, write that you used Excel to clean and analyse survey data for a research project covering several hundred responses. The number does real work here, it turns a claim into something that sounds measured and specific rather than asserted.

Keep the list focused, not exhaustive. As a fresher, somewhere between ten and fifteen genuinely relevant skills is a reasonable range, tailored specifically to the role, rather than fifty scattered, half-relevant ones. A long, unfocused list reads as padding. A short, tailored list reads as intentional.

Mirror the language of the job description, honestly. If a job description names a specific soft skill explicitly, use that exact phrasing rather than a synonym, since both ATS systems and human readers are often matching against the specific words used in the posting. This only works, however, if the skill is genuinely true of you, copying language you can't actually back up in an interview creates a problem later, not an advantage now.

Avoid clichés that every applicant already uses. "Hard worker," "self-motivated," "passionate," "team player" as bare, unsupported labels are treated by recruiters as noise rather than signal, precisely because everyone writes them regardless of whether it's true. If you genuinely are a strong team player, prove it with a specific example instead of the label.

Don't overload on soft skills at the expense of hard ones. A skills section that's mostly soft-skill adjectives with very little technical or role-specific substance reads as though you're compensating for a lack of real capability, even when that's not actually the case. Balance matters.

Choosing the Right CV Format for Your Situation

A standard chronological CV, organised around job titles in reverse date order, works well when you have a clear work history to lean on. When you don't, a skills-based or combination format tends to serve you better, since it organises the CV around skill categories, such as "Data Analysis," "Communication," or "Project Coordination," each backed by evidence drawn from coursework, projects, or informal experience, rather than forcing a thin, apologetic-looking employment section to carry the whole CV on its own.

A sensible structure for a fresh graduate or early-career CV, built around this idea: a brief, specific professional summary; an education section that includes relevant coursework and projects, not just the degree title; a skills section organised by category with evidence attached; internships, attachments, or volunteer experience described with the same rigour as a paid role; and any certifications or self-directed learning that's genuinely relevant to the role you're applying for. Keep it to one page. At this stage of a career, a tight, well-organised single page reads as more confident and more competent than a padded two-page document straining to look substantial.

A Quick Before-and-After

Weak: "Skills: Communication, teamwork, Microsoft Office, hardworking, fast learner."

Stronger: "Coordinated a 6-person team to deliver a final-year research project on schedule, presenting findings to a panel of lecturers. Used Excel to clean and analyse a dataset of 500+ survey responses. Completed a Google Data Analytics certification covering SQL and data visualisation."

Notice what changed. The second version doesn't claim more skill than the first, it's very possibly describing the exact same person. What changed is specificity: a number, a real situation, a named tool, a completed credential. That's the entire difference between a skills section that gets scrolled past and one that actually holds a recruiter's attention for the few extra seconds it takes to decide you're worth a closer look.

The Underlying Point

Having little formal work experience is not the same as having little skill, and treating a CV's skills section as a confession of what you lack, rather than a deliberate presentation of what you can actually do, is the real reason so many early-career applications underperform. You have almost certainly done more, learned more, and built more real capability than your current CV is giving you credit for. The work isn't inventing experience you don't have. It's taking the experience you already have, wherever it actually happened, and describing it with the same seriousness and specificity you'd want from someone who'd been doing the job for years.

This article draws on current CV writing and applicant tracking system research, including recruiter scanning behaviour and hard-skill versus soft-skill screening patterns, current as of mid-2026.