How to Write a Strong Resume With No Work Experience
A practical guide to writing a compelling resume as a new graduate or first-time job seeker, using coursework, projects, and activities instead of a job history.
"Requires experience" is the line every new graduate dreads, because it sounds like a trap you can't escape — you need experience to get a job, but you need a job to get experience. In reality, employers hiring entry-level candidates aren't expecting years on the job; they're looking for evidence you can learn fast and get things done, and that evidence exists even if you've never held a formal job.
1. Reorder your resume's sections
The standard template puts "Work Experience" right at the top, right after contact info — great if you have years of it, but it makes a new graduate's resume look empty at first glance. Flip it: lead with Education, then Skills, then Projects, then any experience you do have (internships, part-time, volunteer), and push a thin "Work Experience" section further down instead of leaving it awkwardly at the top.
2. Turn coursework and personal projects into real experience
A capstone project, a class assignment, or even a side project you built on your own is genuine experience — as long as you describe it in terms of what you did and what happened, not just what the assignment was about. Instead of "Final year project on data analysis," write: "Collected and analyzed survey data from 500+ respondents to produce marketing recommendations presented to a university department."
- Any internship or co-op — even a two-week one.
- Organized volunteer work (running an event, managing a nonprofit's page, an awareness campaign).
- Any leadership role in a student club or association.
- Freelance work, even a single paid gig or a favor for a friend.
- Technical skills backed by an online certificate or a project you can actually point to (e.g. on GitHub).
Don't write "No experience" or leave the section blank — either delete that section entirely if you truly have nothing to put there, or rename it "Projects & Experience" and fill it with the items above.
3. Make your skills section specific, not generic
"Excellent communication skills" tells a hiring manager nothing. Replace vague traits with verifiable specifics: named software (Advanced Excel, Photoshop, Python), languages, tools that are actually relevant to the field you're applying to. If you're unsure what to list, read the actual job posting and note which terms repeat — those, stated honestly, are exactly what belongs on your resume.
4. Write a summary line that earns you a second look
The two or three lines at the top of a resume (the summary) are the most-read part of the entire page — sometimes the only part that gets read at all. For a new graduate, a formula that works is: field + one concrete skill or achievement + what you're looking for. Example: "Recent software engineering graduate who built a full-stack web app with React and Node.js for a capstone project, seeking a frontend developer role to start my career."
How to write an achievement when you have never held a job
The problem is rarely the absence of experience — it is the phrasing. Most first CVs list duties ("was part of the project team") instead of results. Use the same structure professionals' bullets use: an action verb, then what you specifically did, then a measurable outcome. And the outcomes already exist in your history, even if you have never looked at them that way: how many students you tutored, how many people attended an event you organised, the rise in engagement on an account you ran for a university society, the time in which you delivered a project scheduled for longer, the number of people using a small tool you published. An honest modest number beats a large adjective with no number behind it.
The skills section: separate what you have used from what you can name
This section is the first thing asked about at interview, so write it the way you will defend it. A skill you list should be attached to something concrete you did — a project, a practical course, an internship, volunteer work — not a tool you read about or watched a course on. And avoid percentage bars and five-star ratings: they claim a precision you cannot defend, and nobody knows what "Python 70%" is supposed to mean. Better to name the skill and then prove it in the projects section with a single line showing where you used it.
The photo, the template and the page count
Some templates in the CV builder deliberately leave out the profile photo, because the automated systems that read CVs can fail to parse complex layouts, and a layout that wraps a photo in columns and frames is the first thing to confuse them. For a first CV specifically, one page is right — two pages with no work history means there is padding in it, and padding reads as padding. The live preview helps here: watch whether the template is filling the page with real content or with whitespace.
Good design does not compensate for weak content, and the reverse holds too: specific, numbered content in a plain template beats generic content in an elegant one. Build the content first, then pick the template. And review your wording with the other CV tools here before exporting the final file — a first CV is read with a more sceptical eye, and it has no track record to cover for a weak phrase.
Once the content is in order, presentation matters just as much — a clean, well-organized resume signals attention to detail before anyone reads a single word. You can build the whole thing, pick a fitting template, and export it as a ready-to-send PDF from a CV builder, then use a resume summary generator or bullet-point generator whenever you need help phrasing a section more professionally.