How to describe projects on a student resume (with bullet examples)

When you have no job history, projects are your experience. But most student projects on resumes read like a title and nothing else: "Library Management System" or "Marketing Research Project". A reader learns nothing from that. This guide shows how to turn a project into two or three bullets that say what you can do.

The formula: action, method, evidence

Each bullet answers three questions:

1. Action: what did you do? Start with a verb: built, designed, surveyed, tested, wrote, analysed.
2. Method: how, or with what? A tool, a technique, a process.
3. Evidence: what came out of it? A number, a file, a link, a decision, feedback.

You do not need all three in every bullet, but across the project's bullets all three should appear.

A weak bullet and a stronger version:

Weak:   Worked on a survey project for marketing class.
Strong: Surveyed 60 classmates with a Google Form and summarised the results in 5 slides for the class.

The second bullet has a verb (surveyed), a method (Google Form) and evidence (60 responses, 5 slides). Every part of it can be checked.

Where evidence comes from when you have no big results

Students often think they have nothing to measure. Look at these:

• Size: how many people, rows, pages, items, hours.
• Output: a report, a model, a poster, a prototype, a working app, a video.
• Feedback: a teacher's grade, a classmate's comment, a user test with five people.
• Time: finished in three weeks, ran for a semester.
• A link: GitHub, a portfolio page, a shared file, a published post.

If you cannot find a real number, leave the number out and describe the output. A true bullet with no number is better than one with an invented number.

Examples by field

Replace every detail with your own. These show the structure, and the numbers are examples only.

Computer science and IT

Weather Dashboard (JavaScript, public weather API) | github.com/yourname/weather
- Built a page that shows a 5-day forecast for any city a user types.
- Handled errors such as a wrong city name and a failed request with clear messages.
- Wrote a README with screenshots and setup steps.

Commerce and business

Customer Survey for a Local Bakery (Google Forms, Excel)
- Collected 70 responses on buying habits and summarised them in pivot tables.
- Found that most buyers came on weekends and suggested a weekday offer in a 6-slide report.
- Presented the report to the bakery owner.

Design and media

Poster Series for College Fest (Canva, Photoshop)
- Designed 8 posters in one colour system for Instagram and print.
- Tested two headline versions with 30 classmates and used the one most chose.

Science and engineering

Soil Moisture Sensor (Arduino, C++)
- Built a sensor that turns on a pump when the soil is dry.
- Calibrated the readings against three soil samples and recorded the results in a table.
- Documented the circuit and code in a 10-page report.

Group projects: say which part was yours

Many college projects are done in teams, and that is fine to list. Be clear about your part:

• Say "Team of 4" in the title line.
• Describe your work: "Wrote the login module" or "Collected and cleaned the data".
• Do not claim the whole result. Interviewers often ask, "What did you do?" and your answer should match the bullet.

Tutorial and course projects

You may list a project you started from a tutorial or a course, if you add something and are honest about it:

• State what you changed: "Added a search filter and saved favourites" or "Used our own dataset of 2,000 rows".
• Leave out projects that are exactly the tutorial's.
• Be ready to explain every part in an interview.

How many projects, and in what order

• Two or three is enough for a one-page resume. Four thin projects look worse than two good ones.
• Order by relevance to the job, not by date. Put the project closest to the job post first.
• Two to three bullets each. More than that and the reader stops.
• A title line: project name, tools in brackets, and a link if you have one.

To see which tools and words a job post expects, use how to match your resume to a job description.

Where projects go on the page

For a fresher or student, put Projects right after Education, above Skills. If you have an internship, put that above Projects. The Fresher template in the free resume builder is laid out this way, and you can drag sections into your own order.

For the full page layout see the resume format for freshers. If you have no projects yet, read a resume for students with no experience for ideas on what to build in a week.

Mistakes to avoid

• Only a title. "E-commerce Website" tells nothing. Add what you built and the stack.
• Invented numbers. "Increased sales by 40%" on a class project is not believable unless you really measured it. Interviewers ask how.
• Passive wording. "Was responsible for the testing" is weaker than "Tested the app on 3 phones and fixed 5 layout bugs".
• A paragraph. Use bullets of one or two lines.
• Too much jargon. If a non-expert recruiter reads first, they should still understand what the project did.

Frequently asked questions