How to write a project description that impresses recruiters
project description formula, problem statement, solution summary, tech stack mention, impact metrics, avoiding generic language, recruiter reading patterns
Project Descriptions Are Mini Pitches
Most project descriptions on portfolios say what a project does. The ones that get callbacks say why it was built, how it works, and what it proved.
The Four-Part Formula
Write every project description with these four components in order:
Problem: What was broken or missing? One sentence. Be specific.
Solution: What did you build to fix it? One sentence. Name the approach, not just the category.
Stack: What technologies did you use and why? Keep this to 3–4 words. Do not list everything.
Impact: What result did it produce? A number is always better than an adjective.
Example in Practice
Bad: "A full-stack task management app built with React and Node.js."
Good: "A real-time task manager built for remote teams who were losing work in scattered Slack threads. Built with React, Socket.IO, and PostgreSQL. Reduced team check-in meetings from daily to twice weekly for the 3-person team I piloted it with."
The good version is 2.5 times longer but ten times more credible. It shows problem-awareness, architectural decision-making, and real-world impact.
If You Have No Metrics
Make a reasonable claim based on what you can observe: page load time, test coverage percentage, or lines of code removed by your refactor. Even "reduced render time from 2.1s to 0.4s measured in Lighthouse" is a real metric from a real test.