What is a portfolio project?

The short definition

A portfolio project is anything you built, designed or substantially contributed to, chosen to show a hiring manager or client what you can do. It is not the same as "a project": the work becomes a portfolio project when you present it with context, meaning what problem it solves, what your part was, and how it turned out.

Code with no explanation is a repository. The same code with a summary, screenshots, your role and a working demo is a portfolio project.

What counts

More than people think:

• side projects and products you run, paid or free
• client or freelance work you are allowed to show
• class projects, capstones and bootcamp finals
• hackathon builds, labeled as such
• open source contributions, including pull requests to other people's projects
• internal tools from a job, described in words and recreated screenshots when the real thing is private

Tutorial follow-alongs count too once you have extended them and can explain what you added. See makerhandle for students.

What makes one strong

• It fits the job. A data role wants data work; a mobile role wants an app.
• Your role is clear. Solo, lead, or one of four, and which part you built.
• It runs, or you can see it. A live demo, an app store link, or screenshots and a short video.
• It has a story. The problem, the decisions, the trade-offs, the result. That story is the case study.

Three to five strong portfolio projects usually beat a long list of thin ones. The full checklist is in what to put in your developer portfolio.

On makerhandle

Each project on a makerhandle page is a card on your main page and its own page at makerhandle.com/yourname/project, with an optional write-up, gallery, stack, role, timeline, highlights and links to the source code and a live demo. Five projects are free. See makerhandle for developers.