The structure of a great project entry
Project Name — One-line description (Stack, Live link, GitHub)
• What problem it solves and for whom (1 line)
• What you specifically built (1-2 lines, technical)
• Outcome — users, engagement, or scale (1 line)
Example
ExpenseSplit — Group-expense tracker for college trips (React, Node.js, PostgreSQL · Live · GitHub)
- Solved the friction of tracking shared expenses on multi-day trips for 4-10 people.
- Built the settlement algorithm that minimizes the number of transactions; designed the React UI and the Node API.
- 200+ active users in the first 3 months, 1.2k GitHub stars.
How many projects to list
- Fresher: 3-4 strong projects > 10 weak ones.
- Mid-level: 1-2 standout side projects, only if directly relevant.
- Senior: Usually drop side projects entirely; replace with talks, blogs, or open-source.
What to cut
- Tutorials you followed (Todo apps, basic CRUD clones).
- "Coming soon" projects with no live link.
- Hackathon submissions you didn't finish.