Most students writing a first resume get stuck on one sentence: "I do not have any experience." It is rarely true. The experience just does not look like a job yet, so it gets left off and the page looks almost empty.
Graduate recruiters know you have not run a team. They read for signs that you can learn, finish what you start, and work with other people. That evidence is already in your life. Here is where to find it.
Four sources you already have
Coursework. Any module with a project, a lab, a report, or a group presentation counts. Do not stop at the module title. Write down what you produced.
Personal projects. A website, an app, a data analysis, a set of designs, a short film, a small business plan, revision notes you shared with your class. Work nobody asked you to do is often the most interesting item on the page, because it shows you chose it.
Part time and casual work. Retail, hospitality, delivery, tutoring, helping in a family shop. This is real work with real customers and real pressure. It belongs on the page even when it has nothing to do with your degree.
Volunteering and society roles. Running an event, coaching a junior team, fundraising, managing a club account, mentoring first years. These are the closest thing to a job most students have, and they show organisation and responsibility.
Put the sections in the order a reader scans
A student resume usually reads best like this:
- Name and contact details, two lines at most.
- A short summary of two or three sentences: what you are studying, what you are aiming for, one thing you are good at.
- Education, with the degree, the institution, and the dates.
- Projects or work experience, whichever is stronger. Most students lead with projects and internships.
- Skills, split into tools and languages where that makes sense.
- Anything extra that adds something: awards, certificates, a competition placing.
Keep education near the top. A recruiter looks for the degree first, and burying it under an unrelated summer job costs you attention you cannot get back.
Write bullets about what you did
The common mistake is writing about learning instead of doing. "Learned the basics of Python" says almost nothing. "Built a script that reads a spreadsheet of orders and prints a weekly summary" says what was made, and quietly shows that it worked.
Give each bullet the same shape: what you did, what you used, who it was for, and how it turned out. The same work, written two ways:
- Weak: "Worked in a group for a university project."
Stronger: "Worked in a group of four to survey 30 shoppers and presented the findings to the class."
Weak: "Responsible for social media."
Stronger: "Ran the society account, posting twice a week and replying to messages from new members."
Numbers help when they are true. Count people, hours, sessions, items, events, or donations. If a number is an estimate, say so.
Give the projects section real detail
For each project write the name, a date, one line on what it is, and two or three bullets on your part. Then add how it ended: a mark, a demo link, a competition, a prize, or simply that people used it.
If you have nothing there yet, start something small this week. A tidy project with an honest description is worth more than an invented internship, and you can talk about it for ten minutes. Nobody can talk about a made up job that long.
Leave these off
- A photo, your age, your date of birth, your marital status, or your full home address.
- School results, once you are past your second year at university, unless they are strong and relevant.
- Hobbies that say nothing, such as watching films.
- Referees. Write "references available on request" or spend the space on something better.
- Any skill you could not discuss for two minutes if asked.
Keep it to one page and make it easy to read
One page. One column. A clear heading for each section. A font nobody has to squint at. Save it as a PDF unless the application asks for something else, and name the file after yourself rather than "resume final final".
Structure also matters to the software that reads your file before a person does. Tables, columns, text boxes, and headers tend to break when a screening system parses the page, so keep the layout plain.
Read the advert again before you send it
Change your summary line and the order of your skills so they point at the job you are applying for. Ten minutes of that does more than sending the same page to fifty employers.
Then get ready for what comes next. Once your resume makes sense on the page, you will be asked about those projects out loud, and most people find that harder than expected. It is worth saying the answers once before they count, which is what a scored mock interview is for: it builds the questions from your own resume, so the projects you just wrote down are what you get asked about.
Top comments (0)