How to Write the Projects Section

1. The project name, and your role if it was a team project.
2. Dates, so the reader knows how recent it is.
3. The tools or methods you used. These are searchable terms, so name them.
4. A link to the code, a live version or a write-up, if one exists.
5. Two or three bullets: what it does, one decision you made, and a result.

Write a project entry the way you write a job entry: what you built or organised, how, and what came of it. The examples below use illustrative numbers.

Each sample below is a complete entry: a heading line, the tools, a link where one exists, and the bullets. The people, projects and numbers are invented for illustration. Use them for the shape of an entry, and fill in your own facts.

Use technical or scope results instead: the size of the data, the speed you reached, or a constraint you worked within. For example: "Built an offline scheduling tool with conflict resolution that runs entirely in the browser, with no server costs."

A link lets the reader check your claim, which is the advantage a project has over most job bullets. Use a short, readable address written out in full, such as github.com/yourname/project, so it still makes sense when the resume is printed or turned into plain text.

Before you add a link, open it in a private browser window. Make the repository public, add a README that says what the project does and how to run it, and remove passwords, API keys and personal data from the code and its history. A broken or empty link costs you more than no link.

• Tutorial projects where you followed along step by step.
• Projects your whole class built the same way.
• Unfinished projects, unless you say what is left to do and why it is difficult.
• Any project where you cannot explain a decision you made.

With little work history, put Projects after Skills and Education. With several years of relevant work, put Projects after Work Experience or leave the section out. A project you did as part of a job belongs under that job as a bullet, where the employer and dates already give it context. The resume structure guide covers section order.

The builder's Completeness Checker estimates your career stage from your dates and jobs, and gives a Projects section more weight for a student or recent graduate. The ATS checker reports a critical issue if your resume has neither an Experience nor a Projects section.

Projects work for non-technical roles too. A marketing student can list a campaign run for a college fest, with its budget and turnout. A commerce graduate can list a GST reconciliation done for a family business. A teacher moving into instructional design can list a course they built. Write each one the same way: what you did, with what, and what came of it.

If the project was paid or done for a real client, it may belong under Experience as freelance work instead. The fresher resume guide lists the other kinds of work that count as experience, and the ATS resume checker reports when a resume has neither an Experience nor a Projects section. The resume guides cover the sections that sit around your projects.