The Student Resume Guide

Most student resumes are bad in a very specific way: they try to look like they were written by someone with ten years of experience. They are full of abstract claims ("passionate", "dedicated", "fast learner") that mean nothing, and empty of the concrete evidence students actually have.

Students have less of one thing (experience) and more of another (recently acquired skills and recent projects). The right resume for a student leans into the second.

What you actually have

Even if you have never had a job, you have more evidence than you think:

• Coursework. A specific module is evidence of a specific skill. "Distributed systems module (final project: replicated key-value store)" is real experience.
• Projects. Coursework projects, side projects, hackathons, open-source contributions. Even partial work counts if you can describe the outcome.
• Academic achievement. Grades, scholarships, deans lists, prizes — these signal both capability and reliability.
• Volunteer and club work. Organising events, running a society, tutoring — these are real responsibilities with measurable outcomes.
• Part-time and informal work. Retail, hospitality, delivery — these count, and they demonstrate soft skills that matter.

Section order that works for students

The standard resume order (Experience, Education, Skills) assumes you have experience. For a student with limited work history, re-order it:

1. Contact header
2. Education (degree, institution, dates, relevant modules)
3. Projects (coursework, side, hackathon)
4. Experience (any work — paid or unpaid)
5. Skills
6. Awards and activities (if not covered above)

This order puts your strongest evidence first. Education is your strongest asset early in your career.

The summary — do not skip it

A student summary should be two sentences:

• Sentence 1: What you are studying and where.
• Sentence 2: What you are looking for and what you bring.

Example: "Final-year Computer Science student at the University of Manchester, graduating June 2026. Two internships, one national hackathon win, and a portfolio of shipped side projects. Looking for a graduate software engineering role where I can grow into systems work."

Note the evidence in the second sentence. Even without job experience, you have shown that you have shipped things.

Projects are your strongest asset

A project entry should describe:

• What it does (one sentence).
• What you used (technologies, briefly).
• What happened (outcome — users, stars, grade, deployment, publication).

Example: "Ledger Lite — open-source double-entry accounting engine written in Go. 1.2K GitHub stars. Used by three small accounting firms in production."

That single line communicates: you can write Go, you can ship software that other people use, and the work is non-trivial. It is worth more than three generic bullets about being a team player.

Skills — only what you have actually used

Every technology you list will be tested in an interview. If you have used a language for one coursework assignment, list it as intermediate or omit it. If you have shipped multiple projects with it, list it as advanced.

Group skills by category if you have many: Languages (Python, Go, TypeScript), Frameworks (React, Django), Tools (Git, Docker, AWS). This makes the section scannable.

What to leave off

Students commonly include things that work against them:

• "Objective" statements — these are always generic. Use a summary or nothing.
• Secondary school details if you have a university degree (or are about to).
• Every single module. List only the ones relevant to the role.
• References. "Available on request" is assumed.
• Photos. Skip unless the market requires them.