How to Write a Project Description in a Resume

The project description formula

Each project bullet should answer: what did you build, what did you use, and what was the result? Lead with a strong action verb and add a number or outcome wherever possible.

• What: 'Built an e-commerce REST API…'
• How: '…using Spring Boot, MySQL, and JWT authentication…'
• Result: '…supporting product, cart, and order flows with 15 endpoints.'

Before and after examples

• Before: 'Made a website using React.' → After: 'Built a responsive React storefront with cart and checkout, deployed on Vercel.'
• Before: 'Did a Python project.' → After: 'Automated a daily report with a Python script, cutting 2 hours of manual work per day.'
• Before: 'Tested an app.' → After: 'Wrote 40+ manual test cases and automated 15 with Selenium, cutting regression time by 40%.'

Use bullet points, not paragraphs

Two to three short bullets per project read far better than a paragraph. Our builder lets you add each line as a bullet so it renders cleanly in every template.

Start every line with a strong action verb

The first word of each bullet sets the tone. Weak openers like 'worked on' or 'was responsible for' make you sound like a bystander; action verbs make you sound like the person who built the thing.

• Building: Built, Developed, Designed, Implemented, Engineered
• Improving: Optimised, Automated, Reduced, Improved, Streamlined
• Analysing: Analysed, Modelled, Tested, Validated, Debugged

Weak vs strong project lines

A full worked example

Here is how one project looks when you apply the what–how–result formula across two or three bullets:

• Library Management System (Java, Spring Boot, MySQL)
• Built a full-stack app to issue, return, and track 2,000+ book records, with role-based access for admins and students.
• Designed 12 REST endpoints, added JWT authentication, and documented the API with Swagger.

No major project? Use academic and mini-projects

You do not need an internship or a huge project to fill this section. A semester assignment, a hackathon build, a course capstone, or even a small automation script all count — as long as you describe them with the same what–how–result structure. What matters is that the reader can see a real skill being applied to a real problem.

FAQs