The Fresh Graduate Resume Template (When the Page Is Mostly Empty)

It's the same scene every year, in every country, in a few million bedrooms. You've opened a resume template. You've typed your name. You've typed your degree. And now the cursor is blinking under a heading that says EXPERIENCE, and you have nothing to put under it, and the whole exercise suddenly feels like an elaborate way of proving you shouldn't be hired.

So you start reaching. You add a line about being a fast learner. You describe the group project as though it were a startup. You put Microsoft Word under skills. And the document that comes out the other end is the specific, recognisable genre of a resume that is embarrassed about itself — and a recruiter can smell that in about a second and a half.

Here is the reframe that fixes it, and it is genuinely just a reordering problem.

Why is the order the whole problem?

A resume is read top to bottom, and the top is worth vastly more than the bottom. The standard template — Summary, Experience, Education, Skills — was designed for someone whose strongest asset is their last job.

That is not you. Your strongest asset is your degree and the work you did during it. So you move that to the top, and suddenly you are not a person with an empty Experience section — you are a person leading with your best material, which is what every good resume does.

Why are projects experience?

Because a hiring manager isn't reading for employment. They're reading for evidence that you can do the work. Employment is just the most common way people acquire that evidence. It is not the only way, and it's not even the best way for an entry-level hire — a first job teaches you a company, but a project you designed and shipped teaches you the thing they're actually hiring for.

So describe your projects exactly like a job. What was the problem? What did you build? What decision did you make that someone else would have made differently? What happened?

• Final Year Project — built a web application using React and Node.js.
• Group Project — created a database system for a local business.

• Built a route-planning app for the campus shuttle after realising the
  timetable was wrong most mornings. Scraped the live GPS feed, cached it,
  and shipped it to ~400 students in a term. Learned the hard way that the
  GPS feed lies for the first 90 seconds after a bus starts moving.
• Designed the schema for a local bakery's ordering system, then rewrote it
  when we realised the original couldn't handle a customer changing an order
  after it was placed. That rewrite is the thing I'd do differently first.

Read those again. Neither of them is a job. Both of them are unmistakably the work of someone who has actually built something, hit a wall, and thought about it. That is what the reader is looking for, and it beats "Responsible for social media" at a real internship every single time.

What does it look like assembled?

Why is the retail job on there?

Because graduates cut it, and they are wrong to. It's the section people are most embarrassed by and it's doing more work than they realise.

Read it again: sixteen hours a week alongside a full course load, for three years, including every Christmas. That is not a line about selling books. It is evidence of reliability, time management, and dealing with difficult people under pressure without falling apart — and those are exactly the three things a manager quietly worries about when hiring someone with no professional history. Your degree proves none of them.

It also proves something subtler and more valuable: you have held down a commitment you didn't enjoy, for years, because you'd said you would. Nobody puts that in a bullet. Everybody reads it.

What should you never do?

• Never pad. A short, honest, one-page resume with white space on it reads as confident. A page stuffed with "Proficient in Microsoft Word" and "Excellent communication skills" reads as nervous — and nervous is the impression you can least afford.
• Never inflate a title. You were not "Project Manager" of a group assignment. You were a student, and everyone reading knows it.
• Never list a skill you'd panic about. "Java" on a resume is an offer to be asked about Java.
• Never write "references available on request." It has been assumed since about 1994, and it's a whole line you could have used for something true.

The empty page isn't the problem. Being embarrassed by it is — because that's what makes people pad, and padding is the only thing on a graduate resume that a recruiter can spot from across the room.