How to List Side Projects on Your Resume (GitHub, Apps, Freelance)
No internship? No problem. Side projects prove you can build real things—and for many tech roles, a strong project portfolio is worth more than a brand-name internship.
Why Side Projects Matter (Especially for Students)
Side projects solve the classic chicken-and-egg problem that every student faces: you need experience to get hired, but you need to get hired to gain experience. A well-executed side project demonstrates initiative, technical skill, and the ability to complete something independently—three qualities that hiring managers consistently rank among their top criteria for entry-level candidates.
In technology specifically, side projects can be more impressive than internships. An internship shows you can follow instructions and contribute within a structured environment. A side project shows you can identify a problem, architect a solution, choose the right tools, and ship a finished product without anyone telling you to. Many top engineers at major tech companies cite side projects as the most important factor in landing their first job.
Beyond the resume, side projects give you concrete material for interviews. When an interviewer asks "Tell me about a technical challenge you faced," or "Walk me through a project you're proud of," having a side project you built from scratch gives you a rich, authentic story to tell. You can discuss your design decisions, the tradeoffs you made, bugs you debugged, and what you'd do differently next time.
What Counts as a Project
The definition of "side project" is broader than many students realize. Personal applications and websites count—a budgeting app you built for your friends, a workout tracker, a recipe organizer, or a campus events aggregator. Open-source contributions count, whether you maintained your own project or contributed pull requests to existing ones. Hackathon projects count, especially if you continued developing them after the event ended.
Freelance work is a project, too. If you built a website for a local business, created a data pipeline for a professor's research, or developed a mobile app for a campus organization, these are professional-grade projects that demonstrate real-world delivery. Even if you weren't paid, the work product is the same. School projects from advanced courses can also qualify, particularly if they involved significant independent work beyond the assignment requirements.
What doesn't count—or counts for much less—are tutorial follow-alongs, boilerplate projects, and apps where you simply followed a YouTube video step by step. Recruiters and engineers can spot a to-do list app built from a React tutorial instantly. Your projects need to show original thinking and problem-solving, not just the ability to copy code from a tutorial. If your project looks identical to a popular course project, it won't differentiate you.
Formatting a Projects Section on Your Resume
Create a dedicated "Projects" section on your resume, typically placed after Experience and before or after Education (depending on which is stronger). Each project entry should include: the project name, a brief description or tagline, the technologies used, the date or date range, and a link to the live project or GitHub repository.
Format each project like a mini experience entry with two to four bullet points. Lead with the project name and tech stack in bold or as a header: "BudgetBuddy – Personal Finance Tracker | React, Node.js, PostgreSQL, Plaid API | github.com/yourname/budgetbuddy." Then use bullet points to describe what you built, why you built it, and what the outcome was.
Prioritize projects by relevance to the role you're applying for. If you're applying for a frontend role, lead with your most impressive UI project. If you're targeting data science positions, lead with your ML project or data analysis pipeline. You don't need to include every project you've ever built—three to four strong, relevant projects are better than eight mediocre ones.
Writing Project Bullet Points That Impress
The best project bullet points follow the same formula as experience bullet points: action verb + what you did + technical details + result or impact. "Built a full-stack task management application using React, Express, and MongoDB, featuring real-time collaboration via WebSocket, user authentication with JWT, and deployed on AWS EC2 serving 50+ active users" is infinitely stronger than "Created a to-do list app using the MERN stack."
Include metrics and usage numbers wherever possible. "Developed a Chrome extension that automates email sorting using NLP, achieving 200+ weekly active users and a 4.6-star Chrome Web Store rating" tells a recruiter that real people found your project useful—not just your mom. Even modest metrics matter: "Built a study group matching tool used by 30 students in my department" shows traction and real-world utility.
Mention the technical decisions you made and why. "Implemented a Redis caching layer to reduce API response time from 800ms to 120ms" shows engineering depth. "Chose PostgreSQL over MongoDB for relational data integrity in a multi-user budgeting application" shows architectural thinking. These details signal that you understand system design, not just syntax—and that's what separates junior engineers who are ready to contribute from those who still need extensive hand-holding.
Which Projects NOT to Include
Not all projects strengthen your resume. Tutorial projects where you followed a step-by-step guide produce work that looks identical to thousands of other students' repos. If your "e-commerce store" is the same one from a Udemy course, experienced reviewers will recognize it immediately. These projects don't demonstrate problem-solving or originality—they demonstrate your ability to follow instructions, which is a much lower bar.
Unfinished projects can also hurt more than help. A GitHub repo with a half-built application, no README, and commits that stopped three months ago suggests you start things without finishing them. If a project isn't in a presentable state, either finish it or leave it off your resume. Every project you list is one a recruiter might click on—make sure what they find reflects well on you.
Avoid projects that are technically trivial for your experience level. A calculator app or a basic HTML/CSS portfolio page might be appropriate if you're a first-semester CS student, but by the time you're a junior or senior, you should be showcasing projects that demonstrate intermediate to advanced skills: API integrations, database design, authentication systems, deployment, testing, or machine learning models with real datasets.
Making Your Projects More Impressive
The simplest way to make a project more impressive is to deploy it. A live, accessible application at a real URL is dramatically more compelling than code sitting in a GitHub repo that nobody has ever run. Deploy your web apps on Vercel, Netlify, Railway, or a free-tier cloud provider. If it's a mobile app, publish it to the App Store or Google Play. If it's a CLI tool or library, publish it on npm or PyPI. A deployed project shows you understand the full software development lifecycle.
Get real users. Share your project with classmates, post it on Reddit or Hacker News, submit it to Product Hunt, or pitch it to student organizations that could benefit from it. Even 20 genuine users transform your project from "something I built for fun" to "something people actually use." User feedback also gives you material for iterating on the project and discussing user-driven development in interviews.
Write a thorough README for every project's GitHub repository. A good README includes: a clear description of what the project does, screenshots or a demo GIF, installation and setup instructions, the tech stack and architecture overview, and your contact information. Many recruiters and engineers will judge your project by its README before they ever look at the code. A polished README signals professionalism and attention to communication—skills that are as important in software engineering as writing clean code. TechnCV can help you translate these projects into polished resume content that showcases your building skills.