How to List Projects on a Resume (With Examples by Field)

A projects section transforms your resume from a list of job titles into proof of what you can actually build, solve, and deliver. With 70% of employers now using skills-based hiring (NACE Job Outlook 2026) and 76% of hiring managers saying portfolio work can outweigh formal education (Resume Genius, 2025), the projects you showcase may carry more weight than your degree. This guide covers exactly where to place projects, how to format each entry, and what strong examples look like across software, engineering, business, creative, and healthcare fields.

Why Projects on Your Resume Matter More Than Ever

The hiring landscape has shifted decisively toward demonstrated skills over credentials. According to NACE's 2026 Job Outlook survey, 70% of employers now use skills-based hiring practices, up from 65% the prior year. The same data shows that only 42% of employers screen by GPA in 2026, down from 73% in 2019. Employers want evidence that you can do the work, not just that you attended the right school.

70%

of employers use skills-based hiring (NACE, 2026)

76%

say portfolio work outweighs formal education (Resume Genius, 2025)

40%

more interview callbacks with optimized portfolio (CyberPath, 2025)

88%

of employers look for problem-solving evidence (MyPerfectResume, 2024)

Projects are the most direct way to demonstrate problem-solving ability, technical skills, and initiative. A 2025 CodePath survey of over 200 engineering leaders found that side projects and portfolios were the top hiring criterion at 38%, beating internship experience (35%) and public code portfolios (34%). For candidates with limited work experience, projects fill the gap. For experienced professionals, they show ambition beyond day-to-day responsibilities.

Six Types of Projects Worth Including

Not all projects belong on your resume. The key filter: does this project demonstrate a skill relevant to the job you want? Here are six categories that hiring managers consistently value, ranked by how commonly they appear on strong resumes.

Project Type	Best For	Example
Work / Professional	Experienced professionals highlighting cross-functional or stretch assignments	Led ERP migration for 3 regional offices, reducing processing time by 35%
Personal / Side Projects	Developers, designers, and anyone showing initiative beyond their job description	Built a React budgeting app with 2,400 monthly active users
Academic / Capstone	Students and recent graduates with limited professional experience	Senior capstone: designed a solar-powered water filtration system for rural communities
Open-Source Contributions	Software engineers, data scientists, and DevOps professionals	Contributed 14 merged PRs to Apache Kafka, improving consumer rebalance latency
Freelance / Contract	Consultants, designers, writers, and anyone with client-facing project work	Redesigned checkout flow for e-commerce client, increasing conversion rate 22%
Volunteer / Pro Bono	Career changers and anyone demonstrating transferable skills in a new field	Built donor management database for local nonprofit, tracking 1,200+ contributors

Quality over quantity. A single well-described project with measurable outcomes beats five vaguely listed ones. Resumes with hard metrics have up to a 40% higher chance of securing an interview (Resume Now, 2025).

Where to Place Projects on Your Resume

Placement depends on your career stage and how central the projects are to your candidacy. Use this decision framework:

Project Placement Decision Framework

Your Situation	Recommended Placement	Section Header
Student or new graduate with limited experience	Dedicated section above or immediately after Education	"Relevant Projects" or "Academic Projects"
Career changer demonstrating new-field skills	Dedicated section right after Professional Summary	"Selected Projects" or "Portfolio Projects"
Professional whose projects were part of a job	Under the relevant job in Work Experience	Sub-bullets or "Key Project:" prefix within the role
Developer or engineer with strong side projects	Dedicated section between Experience and Education	"Projects" or "Technical Projects"
Senior professional with extensive experience	Under Experience as highlights within each role	Integrated into role descriptions

The dedicated section approach works best when your projects are more relevant to the target role than your job titles suggest. This is especially common for career changers: 52% of employers have relaxed educational requirements to focus on skills and experience (SHRM, 2025), so leading with project evidence of those skills puts your strongest foot forward.

How to Format a Project Entry

Every project entry should follow a consistent structure that gives recruiters the information they need in seconds. Use this template:

Project Entry Template

Project Name | Your Role | Dates (Month Year to Month Year)

Technologies / Tools: [list relevant tools, languages, or frameworks]

Action verb + what you did + quantified result
Action verb + specific contribution + measurable impact
Action verb + challenge solved + outcome with numbers

Before and After: Weak vs. Strong Project Entry

Weak Example

E-Commerce Website

Built a website for an online store
Used various technologies
Worked with a team to complete the project

Strong Example

ShopStream E-Commerce Platform | Lead Developer | Jan 2025 to May 2025

React, Node.js, PostgreSQL, Stripe API, AWS S3

Architected a full-stack marketplace serving 850+ product listings with sub-200ms page loads
Integrated Stripe payment processing, handling $12K in test transactions across 3 payment methods
Led a 4-person team using Agile sprints, delivering 2 weeks ahead of the academic deadline

Notice the difference: the strong example names the project, specifies technologies, quantifies outcomes, and demonstrates leadership. Each bullet starts with a strong action verb and includes at least one number.

Field-Specific Project Examples

What counts as a strong project varies significantly by industry. Below are realistic resume snippets for five fields, each following the format template above.

Software Engineering and Computer Science

For tech roles, 73% of hiring managers prioritize a strong portfolio over a polished resume (CyberPath, 2025), and 84% prefer seeing working applications over standalone code repos (ProFy, 2024). Link to live demos or GitHub repositories whenever possible.

CS Project Example: Open-Source CLI Tool

LogLens CLI | Creator & Maintainer | Mar 2025 to Present

Python, Click, Rich, GitHub Actions | github.com/username/loglens

Developed a command-line log analysis tool that parses and visualizes application logs from 6 formats (JSON, syslog, Apache, Nginx, CloudWatch, custom)
Grew to 340+ GitHub stars and 12 external contributors within 4 months of release
Implemented CI/CD pipeline with 94% test coverage using pytest and GitHub Actions

CS Project Example: Full-Stack Application

MealMap | Full-Stack Developer | Sep 2025 to Dec 2025

React, TypeScript, Express, MongoDB, OpenAI API | mealmap-demo.vercel.app

Built an AI-powered meal planning app that generates personalized weekly menus based on dietary restrictions and budget constraints
Processed 4,200+ meal plans during a 3-month beta with a 4.6/5 average user satisfaction rating
Reduced API costs 60% by implementing response caching and prompt optimization strategies

Engineering (Mechanical, Civil, Electrical)

Engineering hiring managers value capstone projects, design competitions, and research that demonstrate hands-on problem solving. Include specific design parameters, testing results, and standards compliance.

Engineering Project Example: Senior Capstone

Autonomous Soil Moisture Monitoring System | Team Lead (5 members) | Aug 2025 to May 2026

Arduino, SolidWorks, PCB Design, LoRaWAN, MATLAB

Designed and prototyped an IoT-based soil monitoring network for precision agriculture, covering a 2-acre test field with 18 sensor nodes
Achieved 97.3% data transmission reliability over LoRaWAN at distances up to 1.2 km
Reduced estimated irrigation water usage by 28% compared to timer-based systems in 6-week field trial
Presented findings at the university engineering symposium; awarded Best Interdisciplinary Project

Business, Finance, and Analytics

Business roles value projects that show analytical thinking, process improvement, and measurable business impact. Case competitions, consulting projects, and data analysis work all qualify.

Business Project Example: Process Improvement

Accounts Payable Automation Initiative | Process Analyst | Jan 2025 to Apr 2025

Power BI, SQL, UiPath, Lean Six Sigma methodology

Mapped the end-to-end AP workflow across 3 departments, identifying 7 manual bottlenecks consuming 45+ hours per week
Designed and deployed 4 UiPath bots that automated invoice matching and approval routing, reducing processing time from 6 days to 1.5 days
Built a Power BI dashboard tracking processing volume, error rates, and cycle times for 15 stakeholders
Delivered $180K in annualized labor cost savings validated by the Finance Director

Creative and Design

For creative roles, the project itself is the proof. Always link to the portfolio piece, campaign result, or published work. Quantify reach, engagement, or client outcomes when possible.

Creative Project Example: Brand Campaign

Refresh Collective Brand Identity | Lead Designer | Feb 2025 to Apr 2025

Figma, Adobe Illustrator, After Effects | portfolio.example.com/refresh

Created complete brand identity system (logo, typography, color palette, brand guidelines) for a 50-person sustainability startup
Designed 28 social media templates that increased the client's Instagram engagement rate from 1.8% to 4.2% over 3 months
Delivered motion graphics for a product launch video that generated 45K views in the first week

Healthcare and Research

Healthcare employers value clinical research, quality improvement initiatives, and public health projects. Include IRB approval status, sample sizes, and publication or presentation details.

Healthcare Project Example: Quality Improvement

Emergency Department Wait Time Reduction | QI Project Lead | Oct 2024 to Mar 2025

PDSA Cycle, Epic EHR, Tableau, statistical process control

Led a multidisciplinary team of 8 (nurses, physicians, admin staff) through a 5-month PDSA improvement cycle
Analyzed 14,000+ patient encounter records to identify triage bottlenecks during peak hours (2 PM to 8 PM)
Implemented a split-flow model that reduced median door-to-provider time from 47 minutes to 29 minutes
Presented results at the regional ACHE conference; paper accepted for publication in Quality Management in Healthcare

How Many Projects to Include and How to Prioritize

The right number depends on your experience level, but most resumes work best with 2 to 4 projects. Students and career changers can go up to 5 if projects are their primary evidence of capability. Experienced professionals should stick to 2 to 3 that directly support the target role.

Project Prioritization Framework

Rank each project on these four criteria, then include only the top scorers:

Relevance to the target role: Does the project use skills or tools mentioned in the job description? This is the most important factor by far.
Recency: Projects from the last 2 to 3 years carry significantly more weight. Older projects should only appear if they are exceptionally relevant.
Measurable impact: Can you quantify the outcome? Projects with numbers (users, revenue, efficiency gains, test scores) always outperform those without.
Complexity and scope: Multi-month projects involving collaboration, real users, or production systems demonstrate more capability than weekend prototypes.

When tailoring your resume for a specific job, re-rank your projects against each posting. A project that ranks #1 for one application may not make the cut for another. This is the same principle behind tailoring your skills section to each role.

Common Mistakes That Weaken Your Projects Section

Even relevant projects lose their impact when presented poorly. Avoid these pitfalls:

Mistake

No metrics or outcomes. "Built a website" tells a recruiter nothing about your capability level.
Including irrelevant projects. A data science project on your marketing resume wastes space unless the role involves analytics.
Too much technical detail. Three paragraphs about your database schema overwhelm non-technical reviewers.
Missing links. If your project is live or on GitHub, not linking to it is a missed opportunity. 60% of hiring managers prioritize portfolios with collaborative or open-source work (DEV Community, 2025).
Listing outdated technology. A jQuery project from 2018 suggests your skills haven't kept pace.

Fix

Add at least one number per bullet. Users, revenue, time saved, accuracy improved, team size, deadlines met.
Match projects to the job description. Use the same language and action words that appear in the posting.
Keep it to 2 to 4 bullets per project. Lead with the outcome, then explain the method briefly.
Always include URLs. Use shortened or clean URLs that are easy to type from a printed resume.
Replace old projects with current ones. If you must include an older project, note that you have since migrated or updated the tech stack.

ATS Tips for Project Sections

Applicant tracking systems parse your resume before a human ever reads it. A poorly formatted projects section can get stripped, misread, or ignored entirely. Follow these guidelines to ensure your projects survive ATS parsing.

ATS-Friendly Formatting Rules for Projects

Use a standard section header. Stick with "Projects," "Relevant Projects," or "Technical Projects." Creative headers like "What I've Built" may not be recognized by ATS parsers.
Mirror job description keywords. If the posting says "machine learning," use that exact phrase in your project description rather than just "ML" or "AI." Most ATS systems use keyword matching to score candidates, so matching terminology matters.
Avoid tables, columns, and graphics. Many ATS systems cannot parse multi-column layouts or embedded images. Use simple bullet points and standard formatting.
Spell out acronyms on first use. Write "Natural Language Processing (NLP)" rather than just "NLP" so the ATS catches both the full term and the abbreviation.
Include both the tool name and the category. Write "Tableau (data visualization)" or "React (JavaScript framework)" so the ATS matches you against both specific and general keyword searches.
List technologies in a readable format. "Python, TensorFlow, PostgreSQL, Docker" works better for ATS than embedding tools only within paragraph text.

For a deeper look at how ATS systems parse and score your resume, see our guide to quantifiable achievements and the engineering resume examples article, both of which cover ATS optimization strategies for technical fields.

Frequently Asked Questions

Yes, if they demonstrate skills relevant to the target role. Personal projects are especially valuable in tech, where 73% of hiring managers prioritize portfolio strength over resume polish (CyberPath, 2025). A side project that solves a real problem, has real users, or uses tools listed in the job description is worth including. Skip hobby projects that do not connect to professional skills.

Two to four projects is the sweet spot for most candidates. Students and career changers can include up to five if projects are their primary evidence of skill. Experienced professionals should limit it to two or three that directly support the target role. Each project should earn its space by demonstrating a skill the job description requires.

It depends on your career stage. Students and career changers benefit from a dedicated "Relevant Projects" section placed prominently, either after the summary or after education. Working professionals should list workplace projects under the relevant job in their experience section. Developers with strong side projects often place a dedicated "Technical Projects" section between experience and education.

Absolutely, especially if you are a student or recent graduate. Academic projects, capstone work, and research are legitimate evidence of your skills. The key is to present them professionally: give the project a name, specify your role and contribution, list the tools you used, and quantify results wherever possible. As you gain professional experience, academic projects should gradually be replaced by work or side projects.

Yes, always include links when the project is publicly accessible. GitHub repositories, live demos, published research, and portfolio pages give hiring managers a way to verify your claims and see the quality of your work firsthand. Use clean, shortened URLs and test that every link works before submitting. For ATS submissions, place the URL on its own line or after the project title so it does not get garbled by parsing software.

Treat each project like a job. Give it a title, specify your role (even if self-directed, use "Developer," "Researcher," or "Project Lead"), include dates, and write bullet points that start with action verbs and end with measurable outcomes. Focus on what you built, what tools you used, what problems you solved, and what the results were. Hiring managers understand that students and early-career candidates will draw from academic, personal, and volunteer work.