# What to Put in a Portfolio: A Role-by-Role Breakdown (With Examples)
Not sure what belongs in your portfolio? Here is what to include if you are a developer, designer, writer, marketer, or freelancer -- with real examples and the mistakes that make hiring managers click away.
- Author: FolioX Team
- Published: 2026-04-03
- Category: Portfolio Tips
- Reading time: 12 minutes
You know you need a portfolio. But staring at a blank page and thinking "what do I even put in here?" is where most people get stuck -- and either throw everything in or never finish it.

The answer depends on what you do. A developer portfolio looks nothing like a content writer's. A UX designer needs different proof than a data analyst. And if you are freelancing, your portfolio is doing the job of a sales team.

This guide breaks down exactly what to include for each role, what to leave out, and why some portfolios convert and others collect dust.

## The Pieces Every Portfolio Needs (Regardless of Role)

Before the role-specific stuff, get these right:

- **A clear one-liner.** "I am a frontend developer who builds fast, accessible web apps" beats "Welcome to my portfolio" every time. Visitors decide in 3 seconds whether to keep scrolling.
- **3-6 selected projects.** Not everything you have ever made -- your best work, curated. Each project should have context (the problem), your role, the tools you used, and the outcome.
- **Contact info that works.** Email, LinkedIn, and whatever channel is standard in your field. No contact forms that go to a dead inbox.
- **A current resume or professional summary.** Even a short "About" section grounds the portfolio. Hiring managers want to know where you have worked and what you are looking for.

What you do NOT need: a blog you will never update, a wall of logos for every tool you have touched, or a "testimonials" section with quotes from college friends.

## Developer Portfolio: What to Include

Developers get judged on what they have built. Not what they say they know.

**Must-have sections:**

- **3-5 projects with live demos or screenshots.** Each one should answer: What does it do? What was the hard part? What tech did you use? Link to the live app and the repo.
- **Tech stack, presented honestly.** List what you actually use day-to-day. If you did one tutorial in Rust, it does not belong here.
- **A brief "About" with your focus.** "Full-stack developer focused on React and Node" is more useful than three paragraphs of life story.
- **GitHub or GitLab link.** Hiring managers will look at your commit history. Make sure your pinned repos are current and the READMEs are written for humans.

**What separates good from forgettable:**

- Show a project where something went wrong and how you fixed it. Debugging stories prove you can ship, not just start.
- Include at least one project that solves a real problem -- not just a to-do app or weather widget. Even a tool you built for yourself (a budgeting app, a CLI for your workflow) shows initiative.
- Performance metrics: "Reduced load time from 4s to 800ms" or "Handles 10K concurrent users" gives a hiring manager something concrete.

**Common mistakes:**

- Listing 15 projects with no context. Three strong ones beat fifteen weak ones.
- Broken live links. Test every URL before you share the portfolio.
- No README in the repo. If someone lands on your GitHub and cannot tell what the project does in 10 seconds, they leave.

## Designer Portfolio: What to Include

Designers sell through visual proof and process. If a developer portfolio is "show the output," a designer portfolio is "show the journey."

**Must-have sections:**

- **4-6 case studies** (not just screenshots). For each one: the brief or problem, your research, your process (wireframes, iterations), the final design, and measurable results if you have them.
- **Visuals that load fast.** Optimized images, not 15MB PNGs. If your portfolio is slow, you are already losing points on craft.
- **Your design tools.** Figma, Sketch, Adobe CC -- whatever you use. Keep it honest.
- **A short bio that positions you.** "Product designer specializing in B2B SaaS" or "Brand designer for early-stage startups."

**What separates good from forgettable:**

- Show the messy middle. Early wireframes, user feedback that changed your direction, before-and-after comparisons. This proves you think, not just decorate.
- Include one project where you had constraints -- tight deadline, limited budget, difficult stakeholder. Constraint stories signal maturity.
- If you have results, lead with them: "Redesigned onboarding flow; signups increased 35%."

**Common mistakes:**

- Screenshots with no context. A beautiful screen does not tell hiring managers what problem it solves.
- Only showing personal or concept work. Client and team projects carry more weight because they prove you can collaborate and handle feedback.
- Dark mode portfolio with light mode screenshots (or vice versa) -- it looks accidental, not intentional.

## Writer & Content Creator Portfolio: What to Include

Writers need to prove two things: you can write well, and your writing gets results.

**Must-have sections:**

- **6-10 published pieces.** Link to live articles, landing pages, email campaigns, or social posts. If the content has been taken down, use screenshots or PDFs.
- **Range of formats.** Blog posts, case studies, landing page copy, email sequences, social -- show you can adapt your voice to the medium.
- **Results where possible.** "This blog post ranks #3 for [keyword]" or "Email sequence had a 42% open rate." Even one data point makes your portfolio more credible than most.
- **A short writing sample on your portfolio itself.** Your About section and project descriptions ARE writing samples. If they are bland, the portfolio hurts you.

**What separates good from forgettable:**

- Including the brief or strategy behind each piece. "Client wanted to increase organic traffic to their pricing page" gives context that a bare URL cannot.
- One piece that shows your personal voice -- a newsletter issue, a LinkedIn post, a short essay. Hiring managers want to see that you have opinions, not just that you can follow a content calendar.

**Common mistakes:**

- A Google Drive folder instead of a real portfolio. It signals "I do not care about presentation," which is bad when presentation is part of your job.
- Only including work from one industry. Show breadth, especially early in your career.
- No way to tell what YOU wrote versus what an editor or AI rewrote. Be explicit about your contribution.

## Freelancer Portfolio: What to Include

For freelancers, the portfolio is your storefront. It needs to answer one question a potential client is thinking: "Can this person solve my specific problem?"

**Must-have sections:**

- **Niche-specific projects.** If you do web development for e-commerce brands, show e-commerce projects. Generic portfolios lose to specialists.
- **Client outcomes.** Revenue generated, traffic increased, time saved -- whatever matters in your niche. Even rough numbers ("helped launch in 2 weeks instead of 6") work.
- **Your process.** A short "How I Work" section -- discovery, proposal, execution, delivery. Clients want to know what hiring you looks like.
- **Social proof.** Testimonials, logos of companies you have worked with, or a link to your Upwork/Contra profile if the ratings are strong.
- **Clear call to action.** "Book a call" or "Send me a project brief" -- not a generic contact form. Make the next step obvious.

**What separates good from forgettable:**

- Pricing transparency (even a range). "Projects start at $X" filters tire-kickers and signals professionalism.
- A "Who this is for" statement. "I work with early-stage SaaS companies that need a marketing site shipped fast" is more compelling than "I do web development."

**Common mistakes:**

- Showing work you did at a full-time job without permission. Only show freelance or personal projects unless you have explicit approval.
- No testimonials. Even one quote from a real client makes a huge difference.
- An outdated portfolio. If your most recent project is from 2024, clients wonder if you are still active.

## Data Analyst / Scientist Portfolio: What to Include

Data roles are harder to portfolio-fy, but hiring managers still want to see how you think with data.

**Must-have sections:**

- **2-4 analysis projects.** Each with: the question you investigated, the data source, your approach (cleaning, analysis, modeling), the visualization or output, and what you concluded.
- **Tools and languages.** Python, R, SQL, Tableau, Power BI -- whatever you use. Link to notebooks or dashboards when possible.
- **One end-to-end project.** From raw data to insight to recommendation. This proves you can do more than run queries -- you can tell a story with data.

**What separates good from forgettable:**

- Clean, well-commented notebooks. If someone opens your Jupyter notebook and it is a wall of uncommented code, it does not help you.
- A project that uses real (or realistic) data, not just Kaggle competition datasets. Scrape something, use a public API, analyze a real business question.

## Marketing Portfolio: What to Include

Marketers need to show strategy AND execution.

**Must-have sections:**

- **Campaign case studies.** The goal, audience, channels, creative, and results. Include screenshots of ads, landing pages, email sequences.
- **Metrics.** CTR, conversion rate, ROAS, traffic growth -- whatever is relevant. Marketers who cannot show numbers are at a disadvantage.
- **Channel expertise.** Be specific: "Paid social (Meta, LinkedIn)" or "SEO content strategy" or "Email automation in Klaviyo."

**What separates good from forgettable:**

- Showing the thinking behind the numbers. "We tested 4 ad variations; this one won because..." is worth more than "CTR was 3.2%."
- Including a failed campaign and what you learned. It shows self-awareness and analytical skill.

## How to Present It All

Regardless of role, presentation matters:

- **One page, not a sprawling website.** A single-page portfolio with sections (or a clean multi-page site with 4-5 pages max) works better than 20 pages nobody will visit.
- **Fast load time.** Compress images, skip heavy animations. If your portfolio takes more than 3 seconds to load, many visitors bounce.
- **Mobile-friendly.** Recruiters and clients check portfolios on their phones. Test it.
- **Custom domain.** yourname.com looks more professional than a free subdomain. [FolioX](https://foliox.me) gives you a custom domain with your portfolio and resume in one place -- so you share one professional profile in applications and on LinkedIn.

## The Bottom Line

A portfolio is not a gallery of everything you have done. It is a curated argument for why someone should hire you. Pick your strongest work, give it context, show the outcome, and make it dead simple to contact you. The people who get hired are not always the most skilled -- they are the ones whose portfolio made it easy to say yes.

**Ready to build yours?** [FolioX](https://foliox.me) lets you create a portfolio and ATS resume in one place -- no code, custom domain, free to start.

---

## Related Resources

- [Photographer Resume Examples & Template (2026)](/blog/photographer-resume-examples-template-2026) -- 15+ bullets, ATS keywords, and resume format for photographers
- [Portfolio for Photographers](/portfolio-for/photographers) -- what to include and how to present your work
- [Photographer Resume Guide](/resume-templates/photographers) -- section-by-section structure with bullet examples
- [Portfolio for Freelancers](/portfolio-for/freelancers) -- client work and testimonials
- [How to Format a Resume](/guides/how-to-format-a-resume) -- pair your portfolio with an ATS-friendly resume
---

Canonical URL: https://foliox.me/blog/what-to-put-in-a-portfolio-by-role
Markdown twin: https://foliox.me/blog/what-to-put-in-a-portfolio-by-role.md