How to Write a Resume With No Experience

A resume with no work experience leads with education, projects and coursework rather than jobs, and keeps the ordinary reverse-chronological format underneath. Course projects, volunteering, societies and self-taught work all belong on the page. What makes an entry worth including is that you did something and something came of it, not that someone paid you for it.

The phrase "no experience" is almost always inaccurate. It usually means no job title, which is a much narrower thing. People who describe themselves this way have finished degrees, built things, run events, taught themselves software, held committee positions and worked unpaid for organisations that depended on them. All of that is experience. It is simply not arranged in the shape a resume traditionally expects.

The work, then, is not inventing material. It is recognising what you already have and putting it in an order a reader can follow.

What Actually Counts as Experience

Anything where you were responsible for an outcome counts. That is the test, and it is broader than most people apply to themselves.

Course and personal projects. A final-year project, a dissertation, a dataset you cleaned, an app you built to solve your own problem. These are the closest thing to professional work most graduates have, and they are frequently left off entirely because nobody assigned them at a job.

Volunteering. Charity shop shifts, tutoring, coaching a team, helping run a community group. Unpaid work is still work, and it demonstrates reliability over time, which is exactly what someone hiring for a first role is trying to establish.

Societies, committees and student roles. Treasurer, events officer, course representative. These involve budgets, deadlines, other people, and consequences when something goes wrong.

Self-directed learning. A certification you completed, a language you are studying, a tool you learned well enough to use properly. Worth listing when it is relevant to the role and specific enough to be checked.

Part-time and seasonal jobs unrelated to your field. Hospitality, retail, warehouse, delivery. People discount these because they are not "relevant", which is the wrong test. They evidence turning up, handling pressure and dealing with the public, and a hiring manager filling an entry-level role knows it.

The mistake worth avoiding is padding. One substantial project described properly is worth more than six vague lines about things you touched briefly. A reader can tell the difference immediately, and a padded resume raises the question of what else has been inflated.

Reorder the Sections, Do Not Abandon the Format

The standard advice for a resume with no experience is to switch to a functional or skills-based format, which groups everything by skill and drops the dates. It is worth understanding why that advice is wrong before following it.

A functional resume tells an experienced reader that something is being concealed, because that is overwhelmingly what the format is used for. It also parses badly in applicant tracking systems, which expect a reverse-chronological structure and can scramble or drop your history when they do not find one. Our guide to applicant tracking systems covers what happens to a non-standard structure in screening, and our guide to employment gaps reaches the same conclusion for the same reason.

What you want instead is the ordinary format with the sections in a different order. Keep reverse-chronological. Keep month-and-year dates. Simply lead with the section carrying your strongest material:

1. Name and contact details
2. Summary
3. Education
4. Projects
5. Experience, however you have it: volunteering, part-time work, committee roles
6. Skills

Education sits near the top while it is your most recent significant thing, and moves down the page once you have a year or two of work behind you. Nothing about that arrangement is unusual to a recruiter. It is what they expect from someone early in their career.

Write a Summary That Says What You Are Aiming At

Two or three lines under your name, naming what you are looking for and what you bring to it. Not an objective in the old sense. "Seeking a challenging position in a dynamic organisation" says nothing, and readers have been quietly ignoring it for twenty years.

Weak:

Recent graduate seeking an entry-level position where I can utilise my skills and grow professionally.

Better:

Computer science graduate with a final-year project in natural language processing and six months of volunteer web development for a local charity. Looking for a junior backend role where I can keep working in Python.

The second version is stronger because every phrase is checkable. It names a field, a specific piece of work, a real commitment and a concrete thing wanted. The first could be attached to any application by anybody.

If you genuinely do not yet know what you are aiming at, write the summary last, after the rest of the page exists. What you have collected usually points somewhere.

Give Projects the Same Treatment as Jobs

A project entry should look structurally like a job entry: a title, a context, dates, and bullets describing what you did and what resulted.

Final-Year Project: Sentiment Classifier University of Manchester · September 2025 – April 2026

• Built a text classifier in Python and scikit-learn, trained on a hand-labelled set of 4,000 reviews.
• Wrote the labelling guidelines and recruited four classmates to label independently, then measured agreement between them before training.
• Presented the results to a panel of three academics and documented the method so the dataset could be reused by the following year's cohort.

That reads as work because it describes work. Note what it does not do: it does not claim the project was commercially deployed, and it does not dress a coursework exercise up as a startup. The detail about measuring agreement between labellers is the kind of thing that makes a reader believe the rest, precisely because nobody invents it.

Include a link if there is something to look at. A repository, a live page, a write-up. For technical roles especially, a link that works does more than another bullet.

Writing Bullets When You Had No Job Title

The structure that works here is the one that works everywhere: what you did, how, and what came of it. The difficulty with no experience is usually the third part, because the outcomes feel small.

Small outcomes are fine. Specific beats impressive.

• "Helped at a charity shop" becomes "Ran the till and the floor alone on Saturdays, the shop's busiest day, after four weeks of training."
• "Was treasurer of the film society" becomes "Managed a 3,200-pound annual budget across twelve events, and moved the society from a spreadsheet to shared accounting software so the next treasurer inherited a clean handover."
• "Did a group project" becomes "Coordinated a five-person group project, split the work by strength rather than evenly, and delivered two days before the deadline."

None of those claims a revenue increase. Each describes a real thing that happened, with enough specificity that it could be discussed in an interview, which is the actual point of a bullet. Our main resume guide covers the bullet structure in more depth, and it applies here unchanged.

If you catch yourself reaching for a number that does not exist, do not invent one. A fabricated figure is the one thing on this page that can end an application outright, and interviewers ask about numbers.

Skills: Specific and Provable

List tools, languages and methods you could be asked about without embarrassment. The section is short and concrete, or it is noise.

Say "Python (pandas, scikit-learn), SQL, Git" rather than "programming". Say "Conversational Spanish (B1)" rather than "languages". Drop "Microsoft Office" unless the posting specifically asks for it, because it reads as filler on a page that has little else to spare.

Avoid self-rating bars and percentage meters. They claim a precision nobody can verify. What is 80% Python? They also carry no information at all in the extracted text of a PDF, which is what screening software actually reads.

Match the wording to the posting where it is genuinely true. If the role asks for PostgreSQL and you have used PostgreSQL, write PostgreSQL rather than "databases". That is tailoring rather than keyword stuffing, and our guide to tailoring a resume covers where the line sits.

What to Leave Off

A photo, in the UK and US. Common elsewhere, but it invites bias, and some screening processes discard resumes carrying one.

Your full home address. City and country is enough.

Secondary school results, once you have a degree. They take space from material doing more work.

Hobbies, unless they are doing something. "Reading, socialising, travel" is the most skippable line in resume writing. "Maintain a small open-source library used by about forty people" is not a hobby entry at all. It is a project entry, and it belongs higher up the page.

"References available on request." Assumed, and space you do not have.

One Page, and Why That Is Genuinely Right Here

One page is correct for a first resume, and not because of an arbitrary rule. It is correct because the material genuinely fits, and stretching it to two is visible: wider margins, inflated line spacing, a skills section padded to fill a column. A reader recognises a page being stretched, and it undercuts everything on it.

The constraint is also useful. Having one page forces the choice between the project you are proud of and the four you half-finished, and making that choice is most of what turns a list into a resume.

Where a Resume Tool Helps

The hard part of a first resume is rarely the formatting. It is looking at a set of unrelated things (a degree, a summer job, a society role, a project) and seeing what they add up to.

That is the part Get AI Resume is built for. You describe what you have actually done in plain language, and it drafts the structure and the bullets, which is usually easier than facing a blank page and a cursor. Every template exports a real text layer, so nothing you write is lost to screening software, and the layout stays consistent while you rewrite the words. What it will not do is invent experience for you, and you should be suspicious of anything offering to.

Frequently Asked Questions

What do I put on a resume if I have never had a job? Education, projects, volunteering, societies and self-directed learning. Lead with education while it is your most recent significant achievement, and treat a substantial project like a job entry, with dates, context and bullets describing what you did and what resulted.

Should I use a functional or skills-based resume if I have no experience? No. Recruiters associate the format with concealment, and applicant tracking systems expect a reverse-chronological structure and may mis-parse anything else. Keep the standard format and put education and projects above your experience section.

Do I need a resume objective instead of a summary? Write a summary. The old-style objective, "seeking a challenging role where I can grow", says nothing about you. Two or three lines naming your field, one concrete thing you have done and the kind of role you want will do far more.

Does volunteering count as work experience on a resume? Yes. Unpaid work demonstrates responsibility, reliability and dealing with other people, all of which are what someone hiring for a first role is trying to establish. List it with dates in your experience section like any other entry.

How long should a resume be with no experience? One page. The material fits, and padding to a second page is obvious to a reader through wider margins, inflated spacing and filler sections. The constraint also forces you to keep only your strongest material.

Can I put coursework on a resume? Yes, when it is relevant to the role and specific. Name the module or project and what you produced rather than listing course titles, since the output is the part a reader can assess.