Launch Special: Get started with a free AI resume analysis — Upload your resume today

Resume Tips

How to Include Side Projects on Your Resume

Knowing how to include side projects on your resume can set you apart from candidates who only list job titles. Side projects prove you build things without being asked to — a trait hiring managers in tech, design, data science, and creative fields consistently rank among their top signals. The key is treating them with the same rigor as professional experience: clear project names, specific technologies, and measurable outcomes. Here is exactly how to position, format, and select projects that strengthen your application.

Where to Place Projects on Your Resume

Placement depends on how central the projects are to your candidacy. If you are changing careers and your side projects are your strongest proof of relevant skills, create a dedicated Projects section immediately after your summary and before work experience. This ensures recruiters see your most relevant qualifications first.

For candidates with solid professional experience, place the Projects section after work history. This positions projects as supplementary evidence rather than a substitute for on-the-job performance. A third option: if a project was substantial enough — generating revenue, attracting users, or lasting more than six months — you can list it within your experience section labeled as "Independent Project" or "Freelance."

Formatting Each Project for Maximum Impact

Every project entry should follow a consistent structure that mirrors how you format jobs. Use this template:

Project Name | Tech Stack or Tools Used | Link (if available)
One-line description of what the project does, followed by 2-3 bullet points covering your role, the technical approach, and the outcome.

For example:

BudgetPilot | React, Node.js, PostgreSQL | budgetpilot.app
Built a personal finance dashboard that aggregates bank transactions and categorizes spending using ML classification.

Notice each bullet quantifies something: requests, users, stars. Numbers transform hobby projects into professional credentials.

Choosing Which Projects to Feature

Not every project belongs on your resume. Apply a simple filter: does this project demonstrate a skill the target role requires? A machine learning side project strengthens a data science application. A personal blog built with custom CSS strengthens a front-end application. An Arduino home automation system adds nothing to a marketing resume.

According to a 2025 Stack Overflow Developer Survey, 63% of hiring managers said a candidate's GitHub profile or portfolio project influenced their hiring decision — but only when the project was relevant to the role.

Prioritize projects with these qualities: real users or customers, open-source contributions others have engaged with, hackathon entries (especially prize winners), personal websites or apps that are live and functional, and anything that generated revenue. If you are applying for remote positions, self-directed projects are especially powerful because they demonstrate the autonomy remote roles demand.

Open Source Contributions as Resume Material

Contributing to open source projects carries particular weight because it shows you can navigate existing codebases, collaborate asynchronously, and write code that passes external review. You do not need to be a core maintainer. Even well-crafted pull requests to popular repositories count. List these contributions under your Projects section with the repository name, your specific contribution, and any metrics (PRs merged, issues resolved).

If you maintain your own open-source project, include download counts, stars, or forks to indicate community adoption. A tool with 500 weekly npm downloads is more compelling than a private repo nobody has seen.

When NOT to Include Side Projects

Side projects can backfire if they create the wrong impression. Remove projects that are unfinished with no clear outcome — they suggest you abandon things. Remove projects unrelated to your target industry unless they show extraordinary results. Remove anything controversial or politically charged unless you are specifically applying to an advocacy organization. Finally, if you have more than ten years of relevant professional experience, side projects may not add enough value to justify the space. Use that room for deeper professional achievements instead.

Key Takeaways

Frequently Asked Questions

Where should I put side projects on my resume?

Create a dedicated "Projects" section below your work experience. If a side project is directly relevant to the target role, you can also integrate it into your experience section with a label like "Independent Project" or "Freelance."

How many side projects should I include on my resume?

Include 2-4 projects maximum. Choose only those that are relevant to your target role and demonstrate measurable outcomes. Quality matters far more than quantity — one strong project with real users beats five unfinished experiments.

Should I include hackathon projects on my resume?

Yes, especially if you won a prize or built something with continued use. Frame them like any other project: name, tech used, what it does, and the outcome. Hackathons also demonstrate collaboration and ability to deliver under pressure.

Can side projects replace professional experience?

Side projects can supplement limited professional experience but rarely replace it entirely. They are most powerful for career changers, recent graduates, and candidates breaking into new fields where formal experience is thin.

Ready to Upgrade Your Resume?

Upload your resume for a free AI-powered ATS analysis — no payment required.

Get Your Free Resume Review