How do I describe a project on my resume?
Name the project and its context, state your contribution, and explain what someone could inspect or verify. A useful bullet describes an action, its scope and an outcome or deliverable. You do not need a percentage improvement if you did not measure one. Label coursework, volunteering and supervised placements so the reader can distinguish them from employment.
The examples below are fictional writing exercises by Nodesify, not customer results or independently reviewed career advice. Adapt their structure only when it accurately describes your work.
For a related framework, the UK's National Careers Service explains the STAR method: situation, task, action and result. It describes using the method for CVs and applications as well as interviews. You can use those prompts to gather evidence, then condense the relevant action and result into a bullet; you do not need four labeled sections in every bullet.
Coursework: explain the deliverable
Evidence available: A course assignment, a schema diagram, SQL queries and a short report. The project was not deployed to real users.
| Before | Revised bullet | Why it is clearer |
|---|---|---|
| “Completed a database project.” | “Designed a relational schema for a course-scheduling assignment and documented queries for timetable conflicts and room availability.” | Names the deliverable and purpose; makes no claim of production use. |
This version identifies what was built and why. It does not claim production scale, customer adoption or an improvement the student never measured. In a Projects section, label the entry “Course scheduling database — coursework,” then list the relevant dates and tools actually used.
If you wrote queries but did not design the schema, change the verb: “Wrote and documented scheduling queries against a supplied course database.” Your contribution is still useful without taking credit for the whole assignment.
Team project: separate your work from the team's result
Evidence available: A shared repository, your contributions to the booking form, validation rules and setup documentation. Other team members built authentication and deployment.
| Before | Revised bullet | Why it is clearer |
|---|---|---|
| “Built an application with a team.” | “Implemented the booking form and date-validation rules for a team capstone; documented local setup so teammates could reproduce the submission workflow.” | Separates the applicant’s implementation and documentation from the broader team result. |
Use the project description to name the broader team deliverable. Use your bullets to describe your own contribution. Link to a public demonstration or repository only if you have permission and it is useful to the reader. A private repository link does not provide accessible evidence.
The graduate software engineer example shows how to place a capstone alongside internships. The student example combines coursework with part-time responsibilities.
Supervised placement: keep supervision and status clear
Evidence available: A supervised student placement and permitted duties recorded in a placement log. There is no evidence of independent professional practice.
| Before | Revised bullet | Why it is clearer |
|---|---|---|
| “Provided patient care.” | “Assisted with observations and documented assigned findings under the supervising nurse's direction during a student placement.” | Preserves student status, supervision and the boundary of the assigned work. |
Use this wording only if those were your actual duties. Do not publish patient details or confidential placement records. State your actual credential status separately rather than letting a placement title imply an active professional license. The graduate nurse example illustrates the distinction between student placements and employment.
What if I have no numbers?
Describe the deliverable, the task boundary or the process you improved. Specificity can come from a named workflow, a documented decision or the responsibility you held. A number is useful only when you can explain its source and scope.
| Evidence you have | A defensible way to describe it | What to avoid |
|---|---|---|
| A completed report | Name the question, analysis and recommendation | Inventing savings from a recommendation that was never implemented |
| A prototype | Explain the implemented behavior and its limits | Calling a classroom demo a production system |
| A team deliverable | Name your contribution and the team context | Claiming sole ownership |
| A before-and-after measurement | State the metric and comparable conditions | Treating a local measurement as a customer outcome |
Before you publish the bullet
Read it aloud and ask: could I explain the work, show appropriate evidence and distinguish my role from everyone else's? Remove claims you cannot support. Keep confidential information out of portfolio links and downloadable files.
Place the strongest relevant examples early in your first resume. Then inspect the actual exported document. The free checker can flag content omissions, but it cannot verify whether an accomplishment happened.