Resume with no work experience
A resume example for a first job, built from coursework, a volunteer role and one self-directed project — with an honest account of what a page like this can and cannot do.
Student or first job · Updated 2026-08-05
What this resume has to prove
The advice usually given here is that you should reframe everything as experience: group projects become team leadership, a class assignment becomes a client deliverable, being on a sports team becomes stakeholder management. It is well-meant and it does not survive contact with a reader. Anyone hiring for entry-level roles reads dozens of these a week and can spot inflated language instantly, and the effect is worse than plain description because it makes them wonder what else is being oversold.
The honest position is more useful. With no work history, the resume cannot prove you will be good at the job — nothing available to you can. What it can do is prove three narrower things: that you finish what you start, that you can write clearly, and that you are already interested in this specific kind of work rather than applying everywhere. Those are all demonstrable from coursework, a volunteer commitment, and one thing you made because you wanted to. That is the whole strategy, and it is enough, because the people you are competing with are submitting a page of adjectives.
Two structural notes. Education goes first, which is the only stage of a career where that is correct — it inverts within a year or two of your first job. And the projects section carries more weight than anything else on the page, so a single thing you built and finished, with a link, is worth more than four listed coursework titles. One finished thing beats four started ones, every time.
The decisions worth copying
One finished project, with a link, doing most of the work
Campus Bike Registry — built and ran a registration tool the campus police department now uses; 380 bikes registered in the first semester.
This is the strongest thing an applicant with no work history can have, because it demonstrates initiative, completion and consequence all at once, and it cannot be borrowed from a template. It does not have to be technical or impressive in scale. It has to be finished, real, and something you can talk about for ten minutes without preparing.
The volunteer role is described exactly like a job
Front desk volunteer, 6 hours a week for 18 months: checked in 40–60 visitors a shift and handled the intake paperwork.
Unpaid work is real work, and the sustained commitment is the point — eighteen months of showing up every week says something about reliability that no adjective can. Describe it with the same specificity you would use for a paid role: hours, duration, volume, responsibility. Do not apologise for it or file it under a separate heading that signals it counts less.
Coursework is filtered down to what is relevant
Relevant coursework: Database Systems, Statistics, Data Structures
Three courses chosen because they map to the job, not a transcript. Listing eleven courses signals that you cannot tell which ones matter, which is itself information about your judgement. This line is only worth including at all when the courses genuinely connect to the posting; drop it entirely rather than padding it out.
What to put on the page, and what to keep off it
Take the terms that are true of you and put them where they belong in your own sentences. Pasting a keyword block at the bottom of a resume is visible to a human and does nothing a parser rewards. Check yours against a specific posting rather than against a generic list.
- What to draw evidence from
- relevant courseworkcapstone projectvolunteer experiencestudent organisationpart-time workinternshippersonal projectcertification in progress
- Transferable skills worth naming, if true
- written communicationdata entry accuracyschedulingcustomer interactionteamwork under deadlinebasic SQLExcel
- Phrases to avoid
- hardworkingfast learnerteam playerdetail-orientedpassionatego-getterresults-driven
Where these resumes usually go wrong
The objective statement
'Seeking an entry-level position where I can utilise my skills and grow professionally.' This appears on most first-job resumes, describes what you want rather than what you offer, and burns the most-read line on the page. Replace it with two sentences naming what you have actually done — the project, the volunteer role, the coursework — and what kind of work you are aiming at.
Inflating a class assignment into a professional engagement
'Led a cross-functional team to deliver a client solution' when it was a four-person group project for a grade is the specific move experienced readers are watching for, and finding one makes them re-read everything else sceptically. 'Four-person course project; I built the database layer and wrote the final report' is smaller, obviously true, and gives an interviewer something real to ask about.
Listing every skill you have heard of
Filling the skills section with software you have opened once is transparent, and it is the section a reader scans for calibration. Three things you could be tested on today is a stronger claim than fifteen you could not. This is also self-protective: everything on that list is legitimate interview material.
Thinking the page has to fill itself
A first-job resume that runs three quarters of a page with real content beats one padded to a full page with high school achievements and hobby lists. Nobody is measuring length at this stage, and white space reads as confidence. The instinct to stretch is where most of the damage in this category comes from.
Opening this in the editor replaces the placeholder content with fields you can type over. Nothing is uploaded and there is no account — the draft stays in this browser, and the PDF downloads free.