How to List Side Projects on a Resume

TL;DR:

• Put projects where they support the job you want, not as a dump of everything you’ve built.
• Use the same evidence recruiters expect from work experience: scope, tools, outcome, and your role.
• Keep the format scannable; 3–5 strong bullets per project usually beat a long paragraph.

If you want to list projects on resume pages that actually get read, treat each project like a proof point, not a hobby entry. Recruiters spend seconds on an initial scan, and hiring managers care less about whether a project was paid or unpaid than whether it demonstrates relevant skill, judgment, and results. A side project can be a strong signal for a new grad, a career changer, or a senior candidate showing technical depth. The trick is to present it with the same discipline you’d use for a job at Google, Deloitte, or a 20-person startup: clear title, date range, tools used, and measurable outcome. This list projects on resume guide shows how to do that without cluttering your document.

Why side projects deserve a real section

A strong project section solves a specific problem: your resume may not have enough directly relevant experience yet, or your best proof of skill lives outside paid work. That is especially true for software engineers, product managers, designers, marketers, analysts, and students. A candidate who built a Shopify app, redesigned a nonprofit’s donation funnel, or created a Python dashboard for a local business can show capability that a class project alone cannot.

Here’s a mini case study. Maya, a junior data analyst, had 14 months of internship experience at a regional bank but wanted a role in consumer tech. Her resume originally listed two internships and a certification, which made her look narrow. She added a project section with three projects: a churn model in Python, a Tableau dashboard for a student housing survey, and a SQL analysis of public transit delays. Each project had one line on the problem, one line on methods, and one line on outcome. After that change, her recruiter calls improved because the resume finally showed transferable skills: SQL, visualization, stakeholder thinking, and data storytelling.

The key lesson is that projects should answer the question, “Can this person do the work?” A GitHub repo with 12 commits is not enough by itself. A recruiter wants to see context, ownership, and business relevance. If you want a cleaner structure while you list projects on resume sections, use a resume builder or compare your draft against a resume scorer before sending it out.

How to list projects on resume: the best formats

There are three common ways to present projects, and the right choice depends on how much experience you already have. The format should make the most relevant proof easiest to find. If a project is central to your candidacy, give it its own section. If it is supportive, fold it into education or experience.

Format	Best for	Example	Risk
Dedicated Projects section	Students, career changers, technical candidates	“Projects” with 3–4 entries	Can feel thin if projects are weak
Under Experience	Freelancers, consultants, internal builders	“Freelance Analytics Project” under work history	May blur paid and unpaid work
Under Education	Recent grads with class projects	“Capstone Project” beneath degree	Can look academic if not framed well

A practical rule: if the project took 20+ hours, involved a tool stack, and produced a result you can explain in an interview, it deserves more than a throwaway line. If it was a one-hour class assignment, leave it off unless it directly maps to the role.

For each project entry, include four elements in this order: project name, one-line description, tools/skills, and outcome. Example:

Retail Demand Forecasting Dashboard — Built a Power BI dashboard that tracked weekly SKU demand for a 1,200-item catalog; used Excel, SQL, and Power BI; reduced manual reporting time by 6 hours per week.

That format works because it gives a recruiter enough to scan in 5–10 seconds. If you need help tightening language, pair your draft with a resume scanner and then tailor the bullets to the job description.

What hiring teams look for, and the numbers that matter

Industry data shows that hiring teams generally reward relevance, clarity, and evidence over volume. A resume with six weak projects is usually less effective than one with two strong, job-aligned projects. Typical recruiter screens are fast, so the first bullet of each project has to do real work. If the role is for a frontend engineer, “Built a React app” is too thin. “Built a React app that cut appointment booking time from 4 minutes to 90 seconds for a local salon” is memorable because it combines stack, user impact, and a number.

Use numbers wherever you can, but only if they are true and defensible. Good examples include:

• 3-person team
• 8-week timeline
• 1,200 rows of cleaned data
• 27% increase in newsletter click-through rate
• $4,500 in monthly revenue for a freelance client

The strongest project bullets usually follow this formula: action + scope + tools + result. For example, a marketing candidate might write, “Launched a landing page A/B test in Webflow and Google Analytics that lifted trial signups by 18% over 21 days.” A product candidate might write, “Mapped a checkout drop-off flow in Figma and Hotjar, then proposed three fixes that reduced abandonment by 11% in a pilot.”

If you are unsure whether your project section is doing enough, compare it with job requirements. A role asking for SQL, stakeholder communication, and experimentation should be matched with projects that show those exact skills. You can also check how your resume aligns with the employer side of the market by reviewing jobs and building a tailored story around the role, or by preparing for interviews with mock interview practice once you get callbacks.

A step-by-step playbook to make projects count

Step 1: Pick only projects that map to the job

Start with the job description and identify 3–5 repeated skills. If the posting mentions Python, dashboards, and experimentation, choose projects that show those exact capabilities. A project that looks impressive but does not match the role will not help much. For a UX designer, a Figma redesign with usability testing beats a generic AI art experiment.

Step 2: Write bullets with evidence, not adjectives

Replace words like “innovative,” “impactful,” and “successful” with facts. Use numbers, tools, and outcomes. Instead of “Built an app to help users save money,” write “Built a budgeting app in React Native that tracked 500+ transactions and helped 40 beta users categorize spending in under 2 minutes per session.” Specificity makes the claim believable.

Step 3: Format for scan speed

Keep project entries compact. Three bullets per project is often enough, and four is usually the ceiling unless you are applying for a highly technical role. Put the most important detail first, because many recruiters never reach the third line. Use bolding sparingly and keep dates consistent. If your resume is crowded, move older or less relevant projects to a portfolio page or LinkedIn, and keep the resume to the top 2–4 projects only.

A useful test: if you removed the project name, would the bullets still show the skill? If not, the project is too vague. If you want a stronger companion document, use a tailored cover letter to connect the project to the employer’s pain point. That is especially useful when you are changing industries and need to explain why your side work matters.

Common mistakes when you list projects on resume

The biggest mistake is treating projects like a portfolio dump. Recruiters do not need every hackathon, class assignment, or weekend experiment. They need the 2–4 projects that best support your target role. A long list of unrelated items signals poor judgment, not range.

Another common mistake is hiding the outcome. “Built a website using HTML, CSS, and JavaScript” tells the reader almost nothing. So does “Completed a capstone project on machine learning.” What mattered? Who used it? What changed? If there was no measurable result, describe scale, complexity, or user feedback. For example, “Presented a recommendation engine to a 12-person product panel” is better than nothing.

Avoid these pitfalls:

1. Listing only tools — Tools matter, but they are not the story.
2. Using vague labels — “Personal project” is weaker than “Customer Support Triage Dashboard.”
3. Overstating ownership — If a 4-person team built it, say so.
4. Including dead projects — If nothing was shipped, it usually belongs in notes, not on the resume.
5. Mixing unrelated work — A photography portfolio does not help for a financial analyst role unless the job is visual or media-related.

A final trap is failing to update the project section for each application. A candidate applying to Stripe should not use the same project ordering as someone applying to HubSpot or a local nonprofit. Tailoring takes 10 minutes and usually matters more than adding another bullet. If you want a faster workflow, combine your resume draft with whos-hiring to target active openings and prioritize the projects that fit.

FAQ

Should I put side projects on a resume if I already have work experience?

Yes, if the projects strengthen your case for the role. A senior engineer, marketer, or analyst can use 1–2 projects to show depth in a niche skill, like automation, experimentation, or AI. The key is relevance. If the project does not support the job you want, leave it off.

How many projects should I list on a resume?

Most candidates should list 2–4 strong projects. That is enough to show range without crowding the page. Students and career changers may use 3–5 if the projects are highly relevant. If you have more than that, keep the best ones on the resume and move the rest to a portfolio or LinkedIn.

Where should I place projects on my resume?

Place them near the top if they are your strongest proof of skill, especially for early-career candidates. For experienced professionals, put them after work experience unless the projects are directly tied to the role. If the project came from school, it can sit under education, but frame it like work, not coursework.

Should I include GitHub or portfolio links?

Yes, if the project is technical or visual and the link adds useful evidence. Make sure the repo, portfolio, or live demo is clean and current. A broken link hurts credibility fast. If the project is not public, mention that it is available on request or summarize the outcome clearly in the bullets.

Can freelance work count as a project?

Absolutely. Many freelance assignments are better presented as projects if they were short-term, outcome-driven, or client-specific. Use the same structure: problem, tools, result. If the work was paid and ongoing, it may belong under experience instead. The deciding factor is how you want the recruiter to interpret it.

Do I need metrics for every project bullet?

No, but you should use them whenever possible. If you cannot quantify the outcome, quantify the scope: users, pages, datasets, team size, timeline, or deliverables. Numbers make the project easier to compare and remember. Even a simple figure like “built in 10 days” is more useful than a vague praise word.

If you want a faster way to list projects on resume sections that are clear, tailored, and ATS-friendly, start with a draft in the resume builder and then refine it with the resume scorer. That combination helps you keep the projects that matter and cut the ones that do not. Once your resume is tight, you can move to interview prep with mock interview and apply with more confidence.