# Portfolio
A portfolio is a curated collection of your best work--projects, designs, writing, or code--presented so others can see what you do and how you think. Unlike a resume, which lists experience, a portfolio shows outcomes in context: the problem, your role, and the result. Designers, developers, writers, and product professionals often rely on portfolios as much as resumes.
## Deeper Context

Strong portfolios usually feature 3-5 recent projects with brief case-study framing (problem, role, tools, outcome) and links to live work or repositories when possible. Quality and recency beat volume. For developers, GitHub can supplement but rarely replaces narrative; for designers, Behance or a custom site is common. A single URL that combines portfolio and resume simplifies applications and keeps your story consistent.

## Related Terms

- [resume](https://foliox.me/glossary/resume)
- [personal-brand](https://foliox.me/glossary/personal-brand)
- [developer-portfolio](https://foliox.me/glossary/developer-portfolio)


## FAQ

### Do I need a portfolio?

It depends on your field. Roles where hiring managers evaluate tangible work--design, development, writing, product--benefit most. For others, a strong resume and LinkedIn may be enough.

### How is a portfolio different from a resume?

A resume summarizes experience and skills in text; a portfolio shows actual work. They work together: the resume gets you considered; the portfolio can earn the interview.

---

Canonical URL: https://foliox.me/glossary/portfolio
Markdown twin: https://foliox.me/glossary/portfolio.md