How to write a resume with no experience (without pretending you have none)

Every CV guide starts the same way. Name, contact details, work experience. And if you are a student, a recent graduate, or someone trying to break into a new field, that third step is where the whole thing falls apart. You do not have traditional work experience. The blank section stares at you and you stare back.

The problem is not that you have nothing. It is that nobody taught you how to frame what you have as evidence. Because you almost certainly have evidence. Projects, coursework, volunteer roles, freelance bits, personal builds, community work, self-directed learning. All of it counts. But only if you present it like a professional would present paid work, with scope, actions, and results, not as filler to apologise for.

Stop thinking about what you lack

The mistake most people make when writing a resume with no experience is starting from a deficit. They look at what they do not have, feel bad about it, and then try to compensate with enthusiasm. Phrases like “eager to learn” and “passionate self-starter” appear. Skills sections get padded with every technology they have ever glanced at. The whole document ends up trying to prove you are not a risk instead of showing what you can actually do.

Flip it. Start from what you have done. If you built something, that is a project. If you helped an organisation, that is volunteer experience. If you studied a subject deeply enough to produce a dissertation, analysis, or portfolio piece, that is evidence. The reader does not care whether you were paid. They care whether you can demonstrate the ability to do real work. The National Careers Service says the same thing in plainer words, that you can focus on skills learned through projects, work experience or volunteering when the employment history is thin.

What to include on a resume with no work experience

Here is the practical structure. Not every section will apply to you, but most people will find they can fill at least three of these honestly.

Personal summary

Two or three sentences at the top. State who you are, what your strongest relevant skills are, and what kind of role you are looking for. This matters more on a no-experience CV than on any other kind because the reader has no career history to scan. Your summary is the first and sometimes only thing that tells them why your application is worth reading.

A bad summary sounds like this. “Motivated graduate looking for an opportunity to grow and develop my skills in a fast-paced environment.”

A better one sounds like this. “Computer science graduate with practical experience building full-stack web applications in React and Python. Looking for a junior development role where I can contribute to a product team and ship real work.”

The difference is specificity. The second version names actual skills and a clear direction. The first could belong to anyone applying for anything.

Skills

Lead with this section rather than hiding it at the bottom. Group your skills logically. Technical skills, tools, languages, frameworks, methodologies. If you are applying for a role that mentions specific technologies, make sure you include the ones you genuinely know.

Do not list things you have barely touched. If the interviewer asks about something on your skills list and you cannot talk about it, the damage is worse than not listing it at all.

Projects

This is where most no-experience CVs either shine or collapse. If you have built anything, this section is your experience section. Treat every project entry exactly the way an experienced candidate treats a job entry.

Give each project a clear name and a one-line description. State what the problem was, what you did, what tools or technologies you used, and what the outcome looked like. Even university coursework projects work here if you frame them properly.

Compare these two versions of the same project.

Weak version. “Group project to build a website for a local charity. Used HTML, CSS, and JavaScript.”

Stronger version. “Led a four-person team to redesign a local charity’s website, replacing a static WordPress site with a responsive build using HTML, CSS, and vanilla JavaScript. The new site reduced page load time from six seconds to under two and was adopted by the charity as their production site.”

Same project. Same truth. The second version tells the reader what you actually did and why it mattered. That is the entire game.

Volunteer and community work

If you have volunteered for anything, do not shove it into a single line at the bottom. If the work involved organising, coordinating, communicating, problem-solving, or delivering anything tangible, it belongs in the body of your CV and it deserves the same project-style treatment. State the organisation, your role, what you did, and what you achieved.

Education

If you are a recent graduate, your education section carries more weight than it would for someone with ten years of experience. Include your degree, relevant modules, your dissertation or final-year project if it connects to the role, and any academic achievements worth noting.

If you did not go to university, that is fine. Include any relevant training, certifications, bootcamps, or structured learning. What matters is whether you can demonstrate that you studied something seriously and came out the other side with usable skills.

Freelance, side work, and self-directed learning

If you have done any paid freelance work, even a small project for a friend’s business, list it. If you have completed online courses with real project outputs, not just certificates for watching videos, those count too. An independently built portfolio project where you chose the problem, designed the solution, and shipped something real tells the reader more about your ability than a dozen participation badges.

How to handle the experience section honestly

Here is the part that trips people up. Should you leave the experience section out entirely? Should you rename it?

The honest answer is that you should keep a section called something like “Experience” or “Relevant Experience” and fill it with the strongest evidence you have, whether that evidence is paid employment, projects, freelance work, or volunteering. The heading does not need to say “Work Experience” if most of your entries are not traditional jobs. Prospects calls this a skills-based CV and it is a perfectly normal format for graduates.

If you have had part-time or casual jobs, even ones unrelated to the field, they can go here too. Working in a coffee shop for two years proves reliability, customer interaction, and the ability to turn up and do a job. Do not overthink it. A hiring manager looking at a graduate CV is not expecting five years of industry experience. They are looking for signs that you can work, learn, and deliver.

What not to do

A few things that reliably make a no-experience CV worse.

Do not lie. Not about skills, not about projects, not about responsibilities. If you inflated your role in a group project, an interviewer will find that in about ninety seconds. Honest framing of real work, even small work, is always stronger than a vague claim that falls apart under a single question.

Do not pad the page. If your CV is half a page of real content, that is fine. A focused, honest half page is better than a full page of filler. Employers hiring junior candidates know the CV will be short. They are looking for quality of evidence, not volume.

Do not use a template that is louder than your content. Creative layouts, graphics, skill bars, and multi-column designs exist to dress up a CV, not to make it more readable. Use a clean single-column format with clear headings. Let the content do the work.

Do not write an objective statement that could belong to anyone. If you cannot read it out loud and have it sound like something a real person would say about themselves, rewrite it.

Building a resume from what you already have

The underlying problem with writing a resume when you have no experience is that nobody ever asked you to keep track of what you were doing while you were doing it. You finish a project and move on. You volunteer somewhere for six months and forget the details. You build something interesting and never write down what it involved.

This is where building a proper profile of yourself pays off. Not a CV, but a personal record of everything you have done, the skills you used, the scope of the work, the outcomes. With that profile in place, each job application becomes a matter of pulling the right evidence forward rather than trying to reconstruct your history from memory every time.

OutRung works this way. You build a master profile from whatever real experience you have, whether that is ten years in engineering or three university projects and a volunteer stint. The tool treats all of it as valid evidence. When you find a role worth applying to, it can score how well your profile matches and generate a tailored CV that pulls the most relevant parts forward. It does not care whether your evidence came from a salaried position or a self-directed side project. Evidence is evidence.

The real takeaway

You are not starting from nothing. You are starting from a messy pile of real things you have done that nobody asked you to organise. The job of a resume with no experience is not to pretend you have experience you do not have. It is to present the evidence you do have clearly enough that a reader can see you are capable of doing the work.

Frame your projects like jobs. Lead with skills and a real summary. Be specific about what you did and what came of it. Keep it honest, keep it focused, and stop apologising for the experience you have not had yet. Most hiring managers are not expecting a polished career narrative from a first-time applicant. They are looking for signs of competence, initiative, and the ability to communicate clearly.

That bar is entirely within reach. You just need to stop looking at the blank page and start looking at what you have already done.