How to List Projects on a Resume (With Examples)

A project on a resume is any defined piece of work with a goal and a result, such as a capstone, a freelance job, a personal app or a work initiative.

List 2 to 4 projects with a title, context, dates, the tools you used and 2 to 3 result bullets, in a Projects section or under the job where you did them.

Jump to resume projects section examples.

Why Projects Matter on Your Resume

Projects demonstrate practical application of skills in ways traditional work experience sometimes can't. They show initiative, technical competency, and the ability to deliver results, paid or unpaid.

Projects are particularly valuable for:

• Career switchers showing transferable skills in a new field
• Recent graduates compensating for limited work experience
• Freelancers proving expertise across multiple clients
• Professionals with employment gaps demonstrating continuous skill development
• Technical roles requiring portfolio evidence (developers, designers, data analysts)
• Project management roles needing concrete examples of scope, timeline, and stakeholder management

Three projects that match the job description will do more than ten that don't. The key is showing how your project work connects to the job description requirements.

When to Include Projects on Your Resume (And When to Skip Them)

The decision depends on your experience level, the role you're targeting, and whether projects add value beyond your work experience.

Include Projects When

You're changing careers: Projects in your target field prove practical skills that coursework alone can't. A marketing professional moving into data analytics should highlight data projects, even if unpaid, because a career change resume depends on that kind of proof.

You have limited work experience: Academic projects, internships, and volunteer experience demonstrate capabilities when your employment history is thin.

Projects showcase technical skills: Developers, designers, data scientists, and other technical professionals need tangible proof of what they can build.

You're freelancing or consulting: Projects replace traditional employment history and show the breadth of your client work.

You have employment gaps: Personal projects, freelance work, or skill-building initiatives show you stayed current during time away from traditional employment.

Skip Projects When

Your work experience is sufficient: Senior professionals with 15+ years of relevant experience don't need to list college projects. Your employment history speaks for itself.

Projects aren't relevant to the target role: That photography side hustle doesn't strengthen your application for a financial analyst position unless you can connect it to relevant skills.

Projects are outdated: A website you built in 2010 using obsolete technology doesn't demonstrate current capabilities.

You're stretching to fill space: Listing every minor task as a "project" dilutes the impact of genuinely significant work.

Types of Projects to Put on Your Resume

Personal Projects

Side projects, apps, open-source contributions, and hackathon builds all count when they solve a real problem and you can show the result. Link the code or the live version so a recruiter can check it. Club and hackathon work can also sit with your extracurricular activities if it fits better there.

Academic and Capstone Projects

Put 1 or 2 school projects under your degree in the education section. Use a dedicated Projects section when you have 3 or more, or when they're your strongest evidence for the job. Pair them with relevant coursework only where the class directly supports the project.

Freelance and Client Projects

Treat client work like a job entry, with the client, the scope, and a result. If the client is confidential, name the client type instead, such as "regional healthcare network" or "Series A fintech startup." Writers, designers, and developers can build most of a freelance resume from entries like this.

Work Projects

Projects you led or delivered in a job belong as bullets under that job. Name the project in the bullet so it stands out from routine duties.

Ongoing Projects

List ongoing projects with "Present" as the end date, or with "Expected completion" and a month and year. Give the results you have so far, so the entry still shows impact.

Where to Place Projects on Your Resume

The placement of your projects section depends on how central projects are to your value proposition.

Option 1: Dedicated "Projects" Section

Best for: Freelancers, career switchers, recent graduates, and technical professionals where projects are primary evidence of skills.

Placement: After your resume summary, before or after work experience depending on which is stronger. See how to order your resume sections.

When to use this structure:

• Projects are more relevant than your employment history
• You have 3+ substantial projects to showcase
• You're applying for roles where portfolio work is expected

Option 2: Integrated Within Work Experience

Best for: Mid to senior-level professionals where projects occurred within employment.

Placement: As bullet points under the relevant employer in your work experience section.

When to use this structure:

• Projects were part of your job responsibilities
• You have strong employment history at recognized companies
• Projects demonstrate progression within your career

Option 3: Combined "Projects & Freelance Work" Section

Best for: Professionals with a mix of traditional employment and independent project work.

Placement: After work experience or as a separate section if freelance work is substantial.

When to use this structure:

• You balance full-time employment with side projects
• Freelance projects are significant but not your primary work
• You want to show entrepreneurial initiative alongside traditional experience

Option 4: Within Education Section

Best for: Recent graduates and students where projects were part of academic work.

Placement: Under the relevant degree in your education section.

When to use this structure:

• Projects were thesis work, capstone projects, or significant coursework
• You're within 2-3 years of graduation
• Academic projects directly relate to your target role

What to Name Your Projects Section

• Projects: most resumes
• Technical Projects: developer, data, and engineering roles
• Selected Projects: when you show a subset and link to a portfolio
• Academic Projects: students and recent graduates
• Projects & Freelance Work: a mix of independent and client work

Keep to one of these standard names so ATS software can recognize the section.

How Many Projects to List

List 2 to 4 projects. Recruiters scan rather than read, so a few strong entries get more attention than a long list. If you have more worth showing, link a portfolio or GitHub profile and let it hold the rest.

How to Write a Project Description on Your Resume

A strong project description follows the same principles as effective work experience: clear context, specific actions, and quantifiable results.

Basic Project Entry Structure

Project Title | Context | Date

One-sentence description of what you built and why

• Action verb + specific task + measurable outcome
• Action verb + technical skill/tool used + result
• Action verb + challenge solved + impact

Essential Elements to Include

Action Verbs That Strengthen Project Descriptions

For technical projects: Developed, Built, Engineered, Designed, Implemented, Architected, Deployed, Optimized

For analytical projects: Analyzed, Evaluated, Researched, Investigated, Identified, Assessed, Measured

For creative projects: Created, Designed, Produced, Launched, Conceptualized, Illustrated

For management projects: Led, Coordinated, Managed, Organized, Facilitated, Directed, Oversaw

Full Project Description Example

Resume Projects Section Examples by Role

Example 1: Software Developer (Career Switcher)

Why this works: Each project includes specific technologies (matching job description keywords), quantifiable outcomes, and links to verifiable work. The projects demonstrate full-stack capabilities and collaborative skills, which is exactly what a hiring manager scanning a front-end developer resume wants to see. The stack line under each title also shows your programming skills on your resume in context.

Example 2: Data Analyst (Recent Graduate)

Why this works: Combines academic and freelance projects to show both theoretical knowledge and practical application. Metrics demonstrate real business impact on top of technical execution, the same pattern used across these data analyst resume examples.

Example 3: Marketing Professional (Career Switcher to Product Management)

Why this works: Frames marketing projects through a product management lens as user research, cross-functional leadership, and data-driven decision making. It shows transferable skills without forcing the narrative, the core move in product manager resume examples for career switchers.

Example 4: Freelance Graphic Designer

Why this works: Treats freelance projects as professional work experience. Includes client context, business outcomes, and links to portfolio evidence.

Want a layout with a projects section built in? Start from one of our free resume templates.

How to Quantify Project Achievements

Numbers transform vague descriptions into compelling evidence. Some projects lack obvious metrics, but these prompts help you find them even when data isn't immediately apparent.

Direct Metrics (Preferred)

• Users/audience reached: "Served 500+ active users" or "Generated 10,000 page views"
• Time savings: "Reduced processing time from 2 hours to 15 minutes"
• Cost impact: "Decreased infrastructure costs by $5,000 annually"
• Revenue influence: "Contributed to 15% increase in quarterly sales"
• Efficiency gains: "Improved load time by 40%"
• Quality improvements: "Reduced bug reports by 60%"

Indirect Metrics (When Direct Data Isn't Available)

• Scope indicators: "Managed dataset of 100,000+ records" or "Designed system handling 50 concurrent users"
• Complexity markers: "Integrated 5 third-party APIs" or "Coordinated 4-person team"
• Timeline achievements: "Delivered 2 weeks ahead of schedule" or "Completed in 6-week sprint"
• Adoption signals: "Adopted by 3 departments" or "Featured in company newsletter"
• Recognition: "Selected as top capstone project" or "Received client testimonial" (formal honors can also go with your awards on your resume)

Framework for Finding Your Numbers

Ask yourself these questions about each project:

• How many people used/benefited from this?
• How much time did it save (for you or others)?
• How much faster/better/cheaper was it than the previous solution?
• What was the scope (data size, users, features, timeline)?
• What measurable outcome changed as a result?

If you genuinely can't quantify, describe the technical complexity or business context instead: "Built recommendation engine processing user behavior across 12 product categories" is stronger than "Built recommendation engine."

Common Mistakes When Listing Projects

Listing Every Project You've Ever Done

A laundry list of minor projects dilutes your strongest work. Ladders found that recruiters spend an average of 7.4 seconds on an initial resume screen, so they won't read 10 project descriptions.

Vague Descriptions Without Context

"Created a website" tells recruiters nothing about complexity, purpose, or impact. Say who it was for, what problem it solved, what you used, and what happened.

Ignoring ATS Optimization

If your projects section lacks the job description's keywords, it may not get past ATS filters, so mirror the role's exact terms where they're truthful. An AI resume optimizer can flag missing keywords, and an ATS resume checker confirms the section parses.

No Links to Actual Work

For technical roles, claiming you built something without evidence raises skepticism. Link to GitHub, a live site, or a portfolio, or describe confidential work in enough technical detail to show expertise.

Outdated or Irrelevant Projects

An old Java applet or an unrelated hobby project wastes valuable resume space. Keep projects from the last 3-5 years that relate to your target position, unless you can connect an older one to a skill the job needs.

Tailoring Projects to Specific Job Descriptions

The most effective resumes tailor project descriptions to match what each employer is actually looking for.

The Tailoring Process

Step 1: Analyze the job description

Identify the top 5-7 required skills and experiences, and compare them with the skills for your resume you already list. Note the exact language used: if they say "cross-functional collaboration," use that phrase in place of "teamwork."

Step 2: Select relevant projects

Choose projects that demonstrate those specific requirements. You might highlight different projects for different applications.

Step 3: Rewrite descriptions to emphasize relevant aspects

The same project can be framed differently depending on what the role prioritizes. A web development project might emphasize front-end skills for one role and database optimization for another.

Step 4: Incorporate job-specific keywords

Naturally weave in terminology from the job description. If they mention "agile methodology," and you used it, say so explicitly.

Example: Same Project, Two Different Roles

For Product Manager Role:

E-commerce Platform Redesign | 2024

Led 5-person team through 3-month redesign of checkout flow and conducted user research with 50+ customers to identify pain points. Prioritized features using RICE framework, which drove a 28% increase in conversion rate and 40% reduction in cart abandonment.

For UX Designer Role:

E-commerce Platform Redesign | 2024

Designed end-to-end checkout experience based on usability testing with 50+ users. Created wireframes, prototypes, and high-fidelity mockups in Figma across 4 design iterations. Final design increased conversion rate by 28% and received 4.6/5 user satisfaction score.

Same project, different emphasis based on what each role values.

Time Saving Tip

Choosing which projects to feature, and how to frame them, for every job adds up across a full search. Resume optimization platforms like Upplai analyze job descriptions and suggest how to reframe your project descriptions to match what specific employers are looking for, while keeping your content truthful and authentic.