- Put education at the top. For a student resume, education is the most relevant section.
- Coursework, class projects, and personal projects count as real experience. List them, describe them specifically.
- Part-time and casual work matters more than students usually think. It shows reliability and often involves customer-facing skills.
- One page is plenty. Focus on quality over quantity — three strong bullets beat eight weak ones.
The right structure for a student resume
The most common mistake on a student resume is copying the order used by experienced professionals. A working professional's resume leads with experience, because that is where the story is. A student's resume should lead with education, because that is where the story is.
The order that works best for most students:
- Name and contact details. Standard.
- Education. Degree, institution, dates, and — crucially — the modules or coursework that matter for the role.
- Projects. Course projects, personal projects, hackathon work, anything you have built or investigated.
- Experience. Internships, part-time work, volunteering, and any work that demonstrates the qualities the role requires.
- Skills. Tools and technologies, framed in the language of the job posting.
- Awards and activities. If any of them are relevant or notable.
This is the structure that Advoke CV's Category E templates use. If you are not sure where to start, choose "Student First Resume" or "Graduate Professional" and fill in the sections from the top.
Getting the education section right
Most students list their degree and university and leave it at that. This is a mistake. The education section has room for two or three lines of specifics that make you a stronger candidate, and those lines are often the difference between a recruiter reading on and a recruiter moving to the next application.
What to include:
- Degree and institution. The basics.
- Dates. Start and expected end.
- Grade or GPA, if it is strong. Above 3.5 on a 4.0 scale, or first-class honours, or equivalent. If your grade is not strong, leave it off — the absence is not a signal.
- Relevant modules. Two or three that connect directly to the role you are applying for. Do not list every module you have taken. Choose the ones that a hiring manager will recognise as relevant.
- Dissertation or thesis topic. If it is even loosely related to the role, include it. If it is not related, leave it off.
- Academic awards. Dean's list, scholarships, prizes. One line.
Two lines of specific coursework almost always beats a bullet point that lists generic coursework. "Coursework: algorithms, distributed systems, databases" is more useful to a hiring manager than "Studied a variety of computer science topics".
Projects — the student's secret weapon
For a student with limited work experience, projects are the strongest asset on the resume. They show what you can do, and unlike coursework, they show that you can start from nothing and produce something finished.
Projects worth listing include:
- Final-year projects and dissertations.
- Hackathon entries.
- Personal projects you built on your own time.
- Open-source contributions.
- Significant group coursework that involved leading or producing something specific.
- Freelance work — a website you built for a family business counts.
For each project, write two or three bullets that describe:
- What you built or investigated. One line. Scope and purpose.
- What you used or how you did it. Tools, technologies, methods. This is where the ATS-matching keywords live.
- What the outcome was. If there is a measurable outcome — user counts, test results, a grade, a competition placing — include it. If not, describe what you learned or what the project delivered.
Bullets like "Built a course-planning web app in React and Node.js that helps 340 students plan their degree requirements by semester" carry much more weight than "Built a web app for a class".
Making limited experience count
Many students leave part-time work off their resume on the grounds that it is not relevant. This is almost always wrong.
A part-time job at a retail store, a coffee shop, a restaurant, or a call centre demonstrates a set of qualities that matter in almost any role: reliability, customer interaction, working under pressure, handling complaints, working as part of a team, managing a shift. These are exactly the qualities that hiring managers look for in early-career candidates, because they cannot be inferred from grades.
Describe the work in the language the job posting uses. If the posting asks for "customer focus", describe a situation where you handled a difficult customer interaction well. If the posting asks for "attention to detail", describe a specific task where precision mattered. Do not simply write "worked at a coffee shop".
Internships and any professional work go first in this section, followed by part-time and casual work. Volunteer work usually goes last, unless it is unusually relevant.
The student summary (and when to skip it)
A student resume can include a summary, but it is optional. If you include one, keep it to three sentences: what you are studying, what you have built or done, and what you are looking for.
If your resume is already tight on space, skip the summary. A well-organised education and projects section makes a stronger first impression than a summary that repeats what the reader is about to read anyway.
Skills for students
The skills section matters more on a student resume than on a senior one. This is because you are applying for roles where the reader is looking for specific tools and technologies, and they scan the skills section to check for them.
Include:
- Programming languages, frameworks, and tools you have used in coursework or projects.
- Software you are genuinely competent with. Be honest — you will be asked about anything you list.
- Languages spoken, with a level of proficiency.
Leave off:
- Software you have "used" but not at a professional level. Microsoft Word, PowerPoint, and Excel are not skills at the junior level — everyone has them. Only list Excel if you can write formulas and pivot tables.
- Generic soft skills. "Team player" and "hard worker" are not skills.
- Irrelevant tools. Unless the role involves design, a graphic designer's tool list does not belong on a software engineer's resume.
Student resume checklist
- Is education at the top? For student resumes, it should be.
- Does your education section include relevant modules or a thesis? If not, add two or three that match the role.
- Have you listed your projects with specifics? A project description of one line is not enough. Aim for two or three bullets per project.
- Is part-time work on the resume? If not, add it, described in the language of the role.
- Is the resume one page? For a student, one page is almost always the right length.
- Have you matched the language of the posting? Look at the tools, technologies, and capabilities the posting names, and use them if they are accurate for you.
- Have you proofread? Student resumes often have small typos that a senior resume does not, because they have been reviewed fewer times. Read it out loud, then have a friend read it.
Remember: every experience professional started with a resume that looked like yours. What makes an early-career resume strong is not length of experience, but clarity, specificity, and honesty about what you have done.