How to Present Projects and Portfolios on a Resume
Luc Resume · Editorial team
A project section allows you to demonstrate relevant ability even when the work was not part of a full-time job. University coursework, open-source contributions, design exercises, research activities and independently built tools can be valuable if you accurately explain your role and the output. A portfolio link can deepen that evidence—but it does not replace a readable description in the resume.
When projects deserve their own section
Use a Projects section if your best job-related evidence is missing from formal employment, if the vacancy expects a technical or creative portfolio, or if a substantial academic project demonstrates methods the reader cares about. For an experienced specialist, major projects may instead sit under the relevant employer. Avoid repeating the same project in full under both Work Experience and Projects.
UPenn's resume guidance recognizes projects as useful evidence, especially for technical applications; NUS also encourages using relevant learning, community and project experiences. Neither implies that every side project is employment or that a portfolio guarantees an interview.
A reliable project entry
| Component | What the reader needs | Example |
|---|---|---|
| Project name | Identifiable work, not a marketing slogan | Clinic Appointment Prototype |
| Context | Coursework, open source, volunteer or client assignment | University design course |
| Dates | When work happened | Mar–May 2026 |
| Role | Your precise contribution | Interface designer and tester |
| Methods/tools | Relevant, genuinely used approaches | Figma; usability task notes |
| Output | What was produced | Clickable booking prototype |
| Evidence link | Where the work can be examined | Public demo or portfolio case study |
Do not use a company name in a way that makes a classroom simulation look like an actual client engagement. Mark fictional examples clearly, and label real personal projects accurately.
Step-by-step: turn an activity into a convincing project
Step 1 — Find the problem. What question or user need were you trying to address? “Built a website” is too broad; “created a booking interface for students scheduling volunteer shifts” gives context.
Step 2 — Define your contribution. A group project should distinguish your work from shared decisions. If you performed testing but did not build the backend, write testing rather than claiming sole development.
Step 3 — Name the method. Describe tools and procedures in relation to work performed, such as spreadsheet validation, interface prototyping, interviews, unit tests or research coding.
Step 4 — Identify a deliverable. A working prototype, code repository, analysis report, exhibition, instructional guide or documented experiment is a legitimate output. Do not invent adoption statistics.
Step 5 — Link evidence responsibly. Check that the URL is publicly accessible, that screenshots do not expose personal data, and that you have permission to share code, customer materials or photographs.
Fully written fictional project examples
All projects, people, users and organizations below are fictional teaching examples.
Shift Scheduling Dashboard — Coursework Project · Feb–Apr 2026
Role: Data analysis and interface documentation
- Structured a sample volunteer-shift dataset, checking duplicate entries and inconsistent dates with spreadsheet formulas.
- Built a simple dashboard showing open and assigned shifts; documented the limitations of the classroom dataset.
- Prepared a handover guide explaining data fields and refresh steps for the course assessor.
Community Workshop Registration — Volunteer Project · Aug–Oct 2025
Role: Registration coordinator
- Designed a shared participant sign-up form and a weekly attendance checklist for a neighborhood workshop.
- Coordinated edits with two volunteer organizers and summarized recurring registration questions.
- Delivered the final checklist and non-sensitive registration process notes to the team.
The first example demonstrates analysis, validation and documentation. The second demonstrates coordination and process design. Neither claims users, revenues or effects outside the fictional case.
A portfolio is not merely a picture gallery
For a design or software role, consider a short portfolio case study that explains the starting problem, constraints, alternatives, your decisions, work samples, validation and retrospective. A GitHub repository should have a readable README, clear project purpose and instructions if its usefulness depends on running code. In collaborative work, identify which portions you authored or maintained.
Good portfolio link label: “Appointment prototype — interaction design and usability notes.”
Unhelpful label: “My amazing award-winning app,” when no award or usage evidence exists.
If the work is confidential, substitute a sanitized description of your responsibility and skills; do not upload employer data merely to appear impressive.
Common mistakes and corrections
- Listing only tools: “Python, Figma, SQL.” Add what the tools helped you produce.
- Presenting a simulation as paid client work: Label it coursework or a personal project.
- Claiming group outcomes alone: State your role and collaboration.
- Inventing impact: Replace unsupported growth with actual deliverables or observed testing.
- Broken evidence links: Test them from a signed-out browser.
- Overlong project lists: Prefer two or three relevant examples over ten thin ones.
Project-section checklist
- Each entry says what problem was addressed.
- The project's nature, dates and my role are accurate.
- Tools and methods are tied to real work.
- Deliverables and outcomes are defensible.
- I have permission to share linked material.
- The most relevant project is easy to find.
- The portfolio adds useful evidence rather than duplicating empty promotional claims.
A project is valuable when it demonstrates work—not because it has a sophisticated title.
References and further reading
- University of Pennsylvania — Write a Resume/CV
- National University of Singapore — Create an Impressive Resume
- University of Michigan — Resume Resources
- Princeton University — Basic Principles of Resume Writing
These sources offer university career guidance, not evidence of a universal hiring algorithm.
Put this guidance into your resume
Organize your actual experience, preview templates, and inspect the final PDF in the resume workspace.
Open the free resume workspace