How to Put Projects on Your Resume (Format and Examples)

Projects on a resume solve a specific problem: your job titles do not show everything you can do. Maybe you are a student with no full-time experience, a teacher learning data analysis, or an engineer whose best work happened on a side project. A well-written project entry gives a recruiter concrete proof instead of a claim.

The catch is that most people write projects badly. They list a title and a sentence of description, skip the results, and blur whose work it was. A recruiter reading that cannot tell whether the project was a weekend tutorial or a shipped product.

This guide covers which projects to include, where they go, how to format each entry, and how to write bullets that show outcomes even when there is no revenue to report. You will also find examples for students, career changers, freelancers, and experienced professionals.

Why projects on a resume carry weight#

Employers increasingly judge candidates on what they can do rather than which titles they have held. NACE's Job Outlook 2026 Spring Update reports that nearly 70% of employers now use skills-based hiring, and advises students to prepare examples of times they used their skills to solve problems.

Recruiters search for skills, too. LinkedIn's Future of Recruiting 2023 report found that recruiters were 50% more likely to search by skills than by years of experience. A project is one of the clearest places to show those skills in use.

Projects are evidence, not decoration#

When NACE asked employers what they look for on new graduates' resumes, nearly 90% said evidence of problem-solving and nearly 80% said teamwork. A project bullet is built to supply exactly that kind of evidence: a problem, what you did, and what happened.

Who benefits most from a projects section#

• Students and new graduates, whose projects may be their strongest proof of skill
• Career changers, who need to show the new field's skills before they have the title
• People returning from a gap, who can show current skills through recent work
• Technical and creative professionals, where portfolios and repositories are normal
• Freelancers and contractors, whose work is naturally organized by project
• Experienced professionals with one standout project that their job titles undersell

Projects outside tech#

Projects are not just for developers and designers. A sales rep can list a territory expansion plan that opened new accounts. An HR generalist can list an onboarding redesign that improved 90-day retention. A teacher can list a curriculum unit adopted by the whole grade level. A financial analyst can list a forecasting model that replaced a manual spreadsheet process. If a piece of work had a defined goal, a start and end, and a result, it can be written up as a project.

Internship and co-op applications#

For internship applications, projects often carry as much weight as past jobs, because most applicants have little formal experience. Put your strongest project near the top, right after education, and match its tools to the internship posting. Our internship resume guide shows a full layout.

When to leave projects off#

Projects are not always worth the space. If you have several years of relevant experience and your bullets already show the skills the job needs, a projects section mostly repeats what the reader has seen. Leave projects off, too, when they are unrelated to the role, when they are older than your current skills, or when you could not explain them in detail. A resume with no projects is better than one with weak projects that invite awkward questions.

Types of projects you can list on a resume#

Almost any structured piece of work with a goal and an outcome can count as a project. What changes is where it goes and what you emphasize.

Academic projects#

Capstones, theses, lab research, and substantial course projects all count. They work best when you describe them like a job: what problem you tackled, which methods and tools you used, and what you found or built. Mention a grade, award, or presentation only if it was notable. Our guide to relevant coursework on a resume covers when to list classes instead.

Research projects and theses#

Undergraduate research, a master's thesis, or a lab assistantship can be listed as a project when you are applying outside academia. Translate the work for a non-academic reader: say what question you investigated, which methods and tools you used, how much data you handled, and what you found. Save the full publication list and conference details for an academic CV.

Personal and side projects#

Apps, websites, data analyses, published writing, design work, and small businesses all qualify. They show initiative and the ability to finish something without a manager. In technical fields, this is common: in Stack Overflow's 2024 Developer Survey, 68.3% of respondents said they code as a hobby outside work, and only 11.9% said they do not code outside work at all.

Much of that learning happens outside school, too. In the same survey, 82.1% of respondents said they learn to code from online resources, compared with 49.1% who named school. Projects are how self-taught skills become visible to an employer.

That is also a reminder that a side project alone will not set you apart in software. What stands out is a side project that is finished, used by real people, and described with results.

Freelance and client projects#

Paid work for clients is real experience. List it in your experience section, either as one freelance entry with several client projects underneath or as separate entries for major engagements. Our guide to freelance work on a resume covers both layouts.

Work projects#

Major initiatives at your job, such as a system migration, a product launch, or a process redesign, usually belong inside the job entry as bullets. Pull a work project into a separate Projects section only if it was cross-functional, long-running, or more relevant to the target job than the rest of the role.

Open source, hackathons, and competitions#

These show that you can work with other people's code, deadlines, and judges. Name the project, describe your contribution, and add a link to the merged pull request or the competition result. For hackathons, the time frame ("built in 36 hours") is part of the story.

Volunteer projects#

A website you built for a nonprofit or a fundraising campaign you ran can go in a volunteer section or a projects section, depending on which tells the clearer story. See our guide to volunteer experience on a resume for the trade-offs.

Which projects to include: a selection filter#

You probably have more projects than space. Pick the ones that do the most work for this specific application. Run each candidate project through these questions in order.

1. Does it use skills from the job post? If the posting asks for SQL and dashboards, a SQL dashboard project beats a mobile game.
2. Is there a result you can state? Users, accuracy, time saved, a grade, an award, a client outcome. If you cannot name one, the project is weaker.
3. Was your contribution substantial? On a team project, you need a clear piece that was yours.
4. Is it recent? Projects from the last two to three years show current skills. Older ones need to be exceptional.
5. Can you talk about it for ten minutes? Interviewers often ask you to walk through a project in detail. Pick ones you can defend.
6. Can the reader check it? A live link, repository, or published result adds credibility.

How many projects to list#

Most resumes need two to four projects. How much space you give them depends on how much your work history already proves. The chart below is a rough model for a one-page resume, not a rule.

If you have more strong projects than fit, keep the best ones on the resume and put the rest in a portfolio or on your LinkedIn profile.

Where to put projects on your resume#

Placement depends on how central the projects are to your case. The more they matter, the higher and more prominent they should be.

A dedicated Projects section#

Title it Projects, Selected Projects, Relevant Projects, or Technical Projects. These standard labels parse well in applicant tracking systems. List projects in order of relevance to the job, not strictly by date.

Inside your work experience#

For projects you did at work, keep them inside the job entry. You can name the project in bold at the start of a bullet, such as "Billing migration: Moved 40,000 accounts to a new billing platform with zero lost invoices." Our guide to the work experience section shows how to structure job entries.

Under your education#

Recent graduates can list a capstone or thesis under the degree. This works when the project is part of a strong education story. If you have several projects, a separate section is easier to scan. See our guide to listing education on a resume.

How to format a project entry#

Every project entry should answer the same questions so a reader can compare them quickly. Use a consistent layout for all of them.

Titles that explain themselves#

A project title should tell the reader what it is. "Project Phoenix" means nothing outside your team. "Customer Churn Prediction Model" or "Volunteer Scheduling App" does. If the project has a brand name, add a short descriptor: "Pantry Pal (food bank volunteer scheduling app)."

Ordering multiple projects#

Put the most relevant project first, even if it is not the newest. Recruiters often read only the first entry in a section closely, so it should be the one that best matches the job post. Among equally relevant projects, put the one with the strongest result first.

Dates and status#

Use the same date format as the rest of your resume. For ongoing projects, write "2025–Present." If the project is unfinished, be honest about its status in the bullet, such as "beta with 30 test users," rather than implying it shipped.

Links that help instead of hurt#

A link is only useful if what is behind it is polished. A repository should have a clear readme with screenshots and setup steps. A case study should explain the problem, process, and result in a few minutes of reading. Use short, readable URLs and test them before every application.

How to write project bullets that show results#

Project bullets follow the same rules as job bullets: start with a strong verb, say what you did, and end with an outcome. The difference is that project results often are not revenue, so you need a wider set of measures. Our guide to resume bullet points covers the basic structure.

What to measure when there is no revenue#

• Usage: users, downloads, visitors, signups, repeat users
• Performance: load time, accuracy, error rate, processing time
• Efficiency: hours saved, steps removed, manual work automated
• Scale: rows of data, number of records, pages, screens, components
• Quality: test coverage, accessibility score, bug count after release
• Recognition: grade, award, placement, publication, adoption by others

If you need help finding a number, our guide on how to quantify achievements on your resume lists more options, and the accomplishments generator can turn rough notes into measurable statements.

Before and after: a project description#

Here is how the same project reads when written as a description versus as evidence.

The "after" version names the data, compares the result to a baseline, shows real usage, and includes a concrete engineering decision. The resume bullet point generator can help you draft bullets in this shape from rough notes.

Show decisions, not just tasks#

The best project bullets reveal judgment. Instead of listing every task, pick one or two decisions that shaped the result and say why you made them: "Chose a nightly batch job over real-time updates to keep hosting under $10 a month" or "Cut the survey from 30 to 12 questions after a pilot showed a 40% drop-off." Decisions like these give an interviewer something interesting to ask about, and they show how you think, which a task list cannot.

Team projects: claim your part precisely#

Group projects are where many candidates overreach. Say how big the team was and what you owned, then write bullets about your contribution. "Led the backend on a four-person team" is stronger than implying you built the whole product, because it holds up when an interviewer asks follow-up questions.

Projects on a resume: examples by situation#

These examples show different formats and contexts. Use them as structural models, then fill them with your own work.

Student or new graduate (data analysis)#

Software developer (personal project)#

For more on how projects fit a developer resume, see our software engineer resume and web developer resume guides.

Career changer (teacher moving into UX)#

Career changers should place this kind of section near the top, right under the summary. Our career change resume guide shows the full layout, and the UX designer resume guide covers portfolio expectations.

Registered nurse (quality improvement project)#

Projects are not only for technical fields. Clinical staff often lead improvement projects that belong on a resume.

Our registered nurse resume guide covers how to fit projects like this into a clinical resume.

Hackathon or competition#

Experienced professional (work project)#

Freelancer (client project)#

How to describe confidential or unfinished projects#

Not every project can be described in full. Some are under a nondisclosure agreement, some are internal, and some never launched. You can still include them.

Confidential projects#

Describe the type of client and the kind of work without names or sensitive numbers. Use relative figures, such as percentages, instead of absolute revenue if exact numbers are confidential. For example: "Redesigned the claims intake flow for a top-10 U.S. insurer, cutting average intake time by 30%."

• Replace client names with descriptors like "Fortune 500 retailer" or "regional health system."
• Use percentages or ranges instead of confidential figures.
• Leave out unreleased product names and internal code names.
• Do not link to private repositories or internal documents.

Unfinished or cancelled projects#

A project that never shipped can still show skills. Be honest about the outcome and focus on what you delivered: "Built the prototype and test plan for a scheduling feature later deprioritized; the testing approach was reused on two later releases." What matters is that your part was real and complete.

Projects for career changers and people with gaps#

Projects are the most practical way to show current skills in a field where you have no job title yet. They can also fill a gap in your employment history with evidence of what you were doing.

Build projects that mirror the job#

Look at five job posts in your target field and list the tasks they describe. Then design a project that performs one or two of those tasks with real or public data. A future data analyst might analyze public transit data and publish a dashboard. A future marketer might grow a small newsletter and report the numbers.

Project ideas that match common job requirements#

If you need a project for a target role and do not have one yet, start from the work the job actually involves. The table below pairs common roles with projects that produce a result you can report. Keep the scope small enough to finish in four to eight weeks.

A project built for a real user, such as a local nonprofit, is more convincing than one built for yourself. It also gives you a reference who can confirm the work.

Show the gap as active time#

If you spent a career break taking courses and building projects, you can show that period honestly. Use a short entry such as "Career break and professional development, 2025–2026" with one or two project bullets beneath it. Our guide to explaining an employment gap on your resume covers other ways to frame it.

Making projects work with ATS and in interviews#

Projects add keywords and interview material at the same time, if you write them with both in mind.

Use the job post's terms in your tools line#

The tools line under each project is a natural place for the technologies and methods the job post names. Write them the way the posting does: "Power BI," not "Microsoft BI tool." That helps recruiter searches find you and helps the reader see the match. Our guide to resume keywords explains how to find the right terms.

Keep formatting simple#

Use plain text for project titles, tools, and links. Avoid putting projects in tables, text boxes, or graphics, which some applicant tracking systems skip or scramble. Write URLs as visible text, since hyperlinks can be lost when a resume is printed or parsed.

Your resume versus your portfolio#

Your resume carries the summary of each project: what it was, what you did, and what happened. Your portfolio or repository carries the depth: screenshots, process, code, and lessons learned. Do not try to fit a case study onto the resume. Instead, make sure each resume entry links to the place where a curious reader can see more, and that the two tell the same story with the same numbers.

Prepare your project stories#

For each project, prepare a two-minute answer: the problem, your role, two decisions you made, the result, and what you would do differently. That last part often impresses interviewers, because it shows judgment. The STAR method answer generator can help you structure these stories.

Common mistakes when listing projects#

• Describing instead of showing results. "Built a website" is a task. "Built a booking site that took 60 reservations in its first month" is evidence.
• Listing tutorials as projects. Following a course walkthrough is learning, not a project. Extend it with your own features or leave it out.
• Too many projects. Six thin projects are weaker than two strong ones.
• Blurring team and individual work. Always state team size and your role.
• Broken or messy links. A dead link or a repository with no readme hurts more than no link.
• Inconsistent formatting. Every project should follow the same pattern of title, context, dates, tools, and bullets.
• Outdated tools. A project in a framework no one hires for may signal stale skills unless the logic transfers.

Projects section checklist and next steps#

Start with your project log or master resume. For your next application, pick the two to four projects that best match the job post and pass the selection filter. Then format each one the same way and rewrite the bullets until every one ends in an outcome.

Before you send the resume, run through this checklist.

• Every project uses at least one skill named in the job post
• Each entry has a clear title, context, dates, tools, and one to three bullets
• Every bullet ends in a result, such as users, time saved, accuracy, or recognition
• Team projects state team size and my specific role
• Links work and lead to polished, finished work
• Unpaid projects are not labeled as jobs
• I can talk about each project in detail for ten minutes

If you are a student or new graduate, pair this with our guides to a college student resume and a resume with no experience. Once your projects are solid, use the resume rewriter to tighten the rest of the page so every section is as specific as your project bullets.