Projects on a Resume: How to Write Graduation and Personal Projects

Projects on a Resume: Proof of What You Can Do

The Projects section is not filler, especially for students, recent graduates, and career changers. It is where you show work you actually applied: a problem you addressed, a role you performed, tools you used, and an outcome you can discuss.

Build your resume for free with Astr, then select only two or three projects that support the role you want. Next, match your resume to the job description to check whether the skills and outcomes you present are relevant to the employer.

Core rule: Do not list a project name or tools alone. Explain what you did, why it mattered, and what evidence supports it.

When Should You Add Projects to a Resume?

Add projects when they are stronger evidence than a generic Skills line or when they naturally fill a gap in formal experience. They are especially useful when you are:

A student or recent graduate demonstrating applied ability.
Changing fields and have completed relevant work in the new field.
A developer, designer, or analyst with a GitHub repository, portfolio, or working prototype.
An experienced candidate who wants to show an internal initiative that their job title does not make obvious.

You do not need every class assignment. Choose the work that demonstrates a requested skill or a clear outcome. Two to four strong projects are usually enough. If you have substantial relevant experience, include only the most relevant project or keep the rest in a portfolio.

Where Should the Projects Section Go?

Place it where your strongest evidence appears early:

Your situation	Best placement
Student or recent graduate with limited experience	Directly after Education
Relevant internship or part-time work	After Experience
Technical or design role	Near Skills, or before Skills when projects are the clearest proof
Several years of experience	After Experience or as a concise Portfolio section

Use a clear heading such as Selected Projects or Technical Projects. Do not label a project as work experience unless it was genuinely employment or paid client work. Clear labels build trust.

A Strong Formula for Writing Resume Projects

Use three or four lines for each project:

Project name | Type or context | Date Your role + problem or goal + what you built or did + relevant tools + verifiable output or outcome

Weak example:

Graduation project about a delivery app using Flutter and Firebase.

Stronger example:

Order-management app for small retailers | Graduation project | 2026

Built the customer-facing flow and order-status dashboard as one of four team members, connecting Firebase authentication and live status updates. Delivered a working prototype that covered the core order scenarios for the graduation presentation.

The difference is not buzzwords. It is a specific role and output. Add a truthful number when you have one, such as a test sample size or time saved. Never invent a metric to make a bullet sound stronger.

What Should Every Project Description Include?

Not every entry needs every detail, but your reader should be able to answer:

What is the project called, and was it graduation work, personal work, a course, volunteering, or open source?
What problem or goal did it address?
What was your individual contribution?
Which tools or methods matter to the target role?
What was the output: prototype, dashboard, design, report, test, or improvement?
Is there a safe, complete link to GitHub, a portfolio, or a demo?

Order details around the job description. For a data-analyst role, foreground SQL, data cleaning, and Power BI before UI details. For engineering roles, foreground requirements, validation, technical constraints, and testing.

Graduation and Personal Project Examples

Adapt these patterns to your own facts rather than copying them word-for-word.

Data analysis

Sales insights dashboard | Personal project | 2026

Cleaned a public sales dataset with Excel and SQL, then built a Power BI dashboard showing trends by product and region. Documented the cleaning steps and assumptions in the project notes.

Software development

Clinic appointment platform | Graduation project | 2026

Implemented booking screens and appointment-management APIs within a team, testing the core booking and cancellation flows. Used Next.js and PostgreSQL; the repository is available on request because of project data.

Cybersecurity

Web-vulnerability assessment lab | Course project | 2025

Configured an isolated training environment, assessed a deliberately vulnerable practice app, and wrote a report that explained risks and remediation steps without targeting real systems or exposing sensitive data.

Product and UX design

E-commerce sign-up flow redesign | Personal project | 2026

Conducted short user interviews, mapped the sign-up journey, and created an interactive Figma prototype. Published a concise case study explaining design decisions and testing feedback.

Engineering

Prototype smart-irrigation system | Graduation project | 2026

Designed the sensing component, collected soil-moisture readings, and tested pump-control logic across defined conditions. Documented limitations and results in the final report.

Marketing and business

Local-product launch plan | University project | 2025

Analyzed customer segments and competitors, produced a content calendar and hypothetical budget, and presented actionable recommendations to the course team.

How to Describe Your Role in a Team Project

Employers evaluate your contribution, not the team name alone. Do not write “we built the app” when you owned a specific part. Use a clear individual verb: analyzed, designed, implemented, tested, coordinated, documented, or presented.

Instead of:

We created an inventory-management system.

Write:

Analyzed inventory requirements, designed the database schema, and tested product-addition and stock-update scenarios with teammates who owned the interface.

If you led the team, describe that responsibility without implying you did everything: “Coordinated the work plan, assigned tasks, and reviewed the integration before the presentation.” Be ready to explain every line in an interview, including a technical decision that changed during the project.

Is a Personal Project Worth Listing Without Users or a Link?

Yes, if it is real and complete enough to demonstrate a skill. It does not need to be a popular app or a startup. A prototype, public-data analysis, case study, or small tool solving a defined problem can be valuable evidence.

Do not claim business impact that never happened. Write “built a prototype” or “tested the idea with public data,” not “increased sales.” If confidentiality prevents publishing a link, say “brief demonstration available on request” and never add a broken link or an empty site.

What Makes a Graduation Project Different?

A graduation project may deserve slightly more space when it aligns with the target role because it often combines research, planning, implementation, and presentation. State the problem, your individual scope, and the method or final output. Keep the full academic detail for a portfolio or interview rather than turning the resume into a thesis abstract.

Useful format:

Graduation-project title | Major | Date

Analyzed [problem], owned [your role], and applied [tools or method] to produce [output]. Tested [what was tested] and delivered [presentation, prototype, or report].

Mistakes That Weaken a Projects Section

Listing ten small projects instead of the strongest, most relevant work.
Naming tools without actions or outcomes: “Python, SQL, Figma.”
Taking credit for the entire team’s work.
Using metrics you cannot explain or source.
Including broken links or links that expose client, university, or team data.
Repeating the same project word-for-word in Education, Experience, and Projects.
Sending the same ordering and wording to every important opportunity.

Before applying, review the description with the resume grader, then compare each project with the vacancy through resume matching. The goal is for the reader to see the right evidence quickly, not to read every project you have ever completed.

FAQ: Resume Projects

How many projects should I put on a resume?

Two to four is usually enough. Choose projects that prove target-role skills, then keep other work in an organized portfolio or GitHub profile.

Should I include a group graduation project?

Yes, as long as you describe your individual role honestly. A team name is not a substitute for explaining the feature, analysis, decision, or delivery you owned.

Should every project have a GitHub link?

Only include it when the repository is organized, works, and does not expose secrets or sensitive data. One strong portfolio link can be better than several repeated links.

Is a personal project more valuable than a graduation project?

Not automatically. The stronger project is the one that is most relevant and clearest about your role and result. A graduation project can be excellent when it aligns with the role; a complete, documented personal project can be stronger in another application.

Should I include old projects?

Keep one when it still proves a relevant skill and you do not have a newer, stronger example. In fast-moving fields, prioritize current work or clearly show how you updated an older project.

Useful Resources

Final Takeaway

A good resume project is not a polished title. It is concise evidence of how you think and execute. Build your resume for free, select the work most relevant to the role, describe your contribution and output honestly, and tailor the order for every important application.