How to Write a Resume With No Work Experience

The first resume is the hardest, because the standard structure assumes you have something to put under “Experience”. When you do not, the temptation is to pad — long lists of adjectives, secondary school achievements, a paragraph about your passion for the industry.

It is worth reframing what a hiring manager for an entry-level role is actually looking for. They are not expecting a track record. They are looking for evidence that you can finish things, learn quickly, and be relied on. That evidence does not have to come from a job.

Start by taking an inventory

Before writing anything, list everything you have done in the last three years that had a beginning, an end, and someone depending on you. Include:

• Coursework projects — especially capstones, group projects, and anything with a real client or dataset.
• Personal projects — apps, sites, mods, analyses, hardware builds, a YouTube channel, a game you shipped.
• Volunteering — committee roles, tutoring, event organising, charity fundraising.
• Part-time and casual work — retail, hospitality, delivery, care work, farm work. All of it counts.
• Clubs and societies — treasurer, captain, editor, society president.
• Freelance or informal paid work — fixing a family friend's website, photographing a wedding, private tutoring.
• Competitions and hackathons — including ones you did not win.
• Open source contributions — even documentation and small bug fixes.
• Certifications and self-study — completed courses with something to show for them.

Most people find eight to twelve items. You need four or five good ones, described well.

A structure that works

Reorder the standard resume so your strongest material is highest on the page:

1. Contact — name, one line with email, phone, city, and links (GitHub, portfolio, LinkedIn).
2. Summary — two lines stating what you are trained in and your single best piece of proof.
3. Skills — concrete tools and methods, grouped.
4. Projects — three or four, described like jobs. Usually your strongest section.
5. Education — degree, institution, expected or actual graduation, relevant modules.
6. Experience — any paid work, however unrelated.
7. Volunteering, activities, certifications — as space allows.

One page. There is no version of a first resume that justifies two, and a padded second page actively hurts you.

Describing projects like real work

A project entry should carry the same information as a job entry: what it was, what you built, what tools, and what came of it. Give it a title, a date range, and two or three bullets.

The strong versions all do three things: name the project so it sounds like a thing that exists, state the scale or result, and make the technology concrete. The same bullet-writing principles apply as for jobs — see writing bullet points that get read.

Using education properly

While you are studying or within a year of graduating, education sits high on the page and can carry detail. Include:

• Degree, institution, and graduation date — “expected June 2027” is fine.
• Grade — if it is strong by local convention; omit it otherwise rather than drawing attention.
• Relevant modules — four or five that map to the job, not your whole transcript.
• Thesis or capstone title — if it is relevant to the role.
• Scholarships, prizes, or dean's list — one line.

Drop secondary school entirely once you are in higher education, unless you are applying for your first part-time job. And drop all of this detail within a year or two of starting work — education compresses to two lines as soon as you have real employment.

What to leave out

• An objective statement. “Seeking an opportunity to grow” is the weakest possible opening line.
• Soft-skill lists. “Hard-working, motivated, quick learner” — asserted by everyone, believed by nobody.
• Every course you took. Four or five relevant modules, not thirty.
• Skills you cannot demonstrate. Listing a language you used once will surface in the first screening question.
• A photo, date of birth, or full address. Unnecessary in most Western markets.
• “References available upon request.” Assumed.

If the inventory really is empty

Then the fastest route to a better resume is not more writing — it is one small, finished, visible project. Two or three focused weeks is enough to produce something with a link.

Pick something with a real constraint: analyse a public dataset about somewhere you live and publish the findings; build a tool that solves an annoyance for a club you belong to; volunteer to fix the website of a small charity. The key word is finished — a completed small thing beats an ambitious half-thing every time, because completion is precisely the quality being assessed.