Resume · 4 min read
How to add projects to your resume as a college student
Which projects to include, how to describe them in three lines, and how to turn class and group projects into proof that recruiters trust.
When you have no job history, your projects are your experience. Recruiters of fresher roles know that, and they read this section more closely than almost any other. The trouble is that most students list projects as a title and a tool, such as "Library Management System (Java)". That tells the reader you did a typical assignment, but not whether you can do the job. This guide shows how to choose projects and describe them so they count.
Which projects to include
Pick three at most, and choose by relevance to the job, not by how large the project felt in college. A short project that matches the role beats a long one that does not. Ask of each candidate:
- Does it use skills the job post asks for?
- Can I explain every part of it for five minutes without notes?
- Is there something to point to: a working demo, a repository, a report, a screenshot, a result?
If the answer to the second question is no, leave it out. Interviewers pick a project and ask "why did you do it this way?". A project you cannot explain does more damage than no project.
The three-line pattern
Write each project as a heading plus two or three lines:
- Line 1, the heading: project name, the main tools in brackets, and a link if you have one.
- Line 2, the problem and your part: what it was meant to do and what you personally built.
- Line 3, the result or scale: a number, a user, a test, or an outcome.
Example:
Bus pass renewal tracker (Python, Flask, SQLite) · github.com/yourname/bus-tracker
Built a web tool that lets the college transport office record pass renewals and send reminders, replacing a paper register. Used by 3 staff members to track 800 students; cut the weekly checking time from about two hours to about fifteen minutes.
That entry shows the tools, the real-world problem, the size, and the result in about forty words.
Start bullets with action verbs
Begin each line with a verb that says what you did: built, designed, analysed, tested, automated, organised, wrote, configured. Avoid "worked on" and "was responsible for", because they do not show what you actually did. If the project was a group effort, write "Built the login and database parts of a four-person project" rather than claiming everything.
Be honest about group and tutorial projects
Many college projects are done in groups or follow a tutorial. That is fine, but do not hide it. State your part clearly: "Wrote the payment module in a team of four". If you followed a tutorial, change something before you list it: add a feature, use your own data, or fix a problem. Then describe the change. Interviewers can tell the difference within two questions, and being caught overclaiming loses the offer.
Projects for non-tech fields
You do not need to code to have projects. These all count:
- Commerce: a mock audit or bookkeeping exercise, a market survey, a budget model in Excel.
- Marketing: a content calendar, a campaign for a college fest, a page you grew, an ad creative test.
- Design: a case study with the problem, process, screens and what you learned.
- Engineering: a design with drawings, a prototype, test data, a lab report with results.
- Writing and media: articles, a blog, a newsletter, a short video, with links.
The same pattern applies: what the problem was, what you did, what happened.
Where to put the section and how long
With no job history, put Projects directly after Skills and before Education. Three projects with three lines each is about a quarter of your page. If you have a strong internship, list that first and cut projects to two.
Make your project easy to check
A link makes a claim believable. For software, a GitHub repository with a short README that explains what it does and how to run it. For design, a portfolio page. For analysis, a short write-up or a public dashboard. Before you add a link, open it in a private browser window to confirm anyone can view it, and tidy the README: remove old test files and add a screenshot.
Checklist before you finalise
- No more than three projects, all relevant to the role.
- Each has the tools, your part, and a result or scale.
- You can explain each one in five minutes, including what you would change.
- Links open for a stranger.
- No claims you cannot back up.
Want to see which skills from your projects match a job post? Paste both into the tailor tool and see which skills it finds in your resume and which it does not.