How to List "Side Projects" on a Resume (When You Have No Experience)

The catch-22 of entry-level software engineering: You need experience to get a job, but you need a job to get experience.

If you are a fresh grad, a self-taught dev, or coming out of a bootcamp, your "Experience" section is likely empty. This is where your "Side Projects" section needs to do heavy lifting.

But simply listing a link to your GitHub repo isn't enough. Recruiters are too busy to browse your code. You need to sell the project exactly like a previous job.

The Mistake: Treating Projects Like Tutorials

Don't list a project like this:

• Weather App: Used React and OpenWeather API to show the temperature.

This screams "I followed a YouTube tutorial." It shows you can copy-paste code, but not that you can engineer a solution.

The Solution: Treat Projects Like Products

To make a side project impressive, you need to describe the engineering challenges you solved. Use the STAR method (Situation, Task, Action, Result), even for code you wrote alone in your bedroom.

Here is that same Weather App, rewritten for a resume:

Global Weather Dashboard (React / Node.js / Redis)

• Architected a responsive front-end using React Hooks and Context API to manage global application state.
• Built a Node.js express proxy server to hide API keys and rate-limit requests to third-party services.
• Implemented Redis caching layer on the backend, reducing external API calls by 60% and speeding up repeat data loads to under 100ms.
• Deployed via Docker containers on an AWS EC2 instance with CI/CD pipelines set up through GitHub Actions.

See the difference? The second version shows you understand backend, performance, and deployment. It reads like "work experience."

Where to put them?

If you have absolutely zero professional experience, put your "Projects" section right under your "Skills" section, before your education. They are the most valuable thing you have to show.