How to Build a Portfolio When You Are Not a Designer

When a job posting says "please include work samples," it is not only asking designers and copywriters. Sales reps, customer success managers, project managers, data analysts, and operations leads get the same request, and most of them freeze, because their work lives inside private company systems they cannot share.

The good news: nobody expects a polished web portfolio from a program manager. They expect three short case studies that prove you have solved problems like theirs before.

What the hiring manager is actually checking

Three things. First, have you done this job before, or something close to it. Second, do you think in outcomes rather than tasks. Third, can you explain your own work clearly to someone who was not there.

A task list answers none of those. "Managed stakeholder communication" says nothing. "Cut weekly status meetings from 90 minutes to 25 by moving updates to a shared doc, which freed six hours a month across a 14-person team" answers all three.

Pick three projects, and make one of them boring

Choose three: your strongest measurable win, one project that shows how you work with other teams, and one that failed or went sideways. The failure case is the one candidates want to skip and the one interviewers find most convincing, because it proves you can evaluate your own decisions. And include at least one unglamorous project. If every case study is a company-saving turnaround, the reader stops believing you were there when the work happened.

The case study format that works

• Context (two lines). Company type and size, your role, the timeframe. "B2B SaaS, about 200 employees, I owned a $2.4M book of mid-market accounts, six months in 2025."
• The problem. Lead with the number that was bad. "Monthly churn on my book was 2.1%, roughly double the team average."
• What you did. Three to five decisions in order, each with the reasoning. Interviewers care more about the reasoning than the outcome.
• The result. Real numbers if you can share them, a defensible range or percentage if you cannot.
• What you would do differently. One or two lines. This section does more work than anything else on the page.

Keep each case study to one screen. If it needs scrolling, it is an essay, and nobody reads it.

Handling confidential work

You do not need to leak anything to show your work. Redact client names, replace them with descriptions like "a regional grocery chain in the Midwest." Convert dollar figures to percentages or ranges and say so plainly: "figures changed slightly to protect client confidentiality." Never upload internal decks, dashboards, or customer lists verbatim, and check your employee handbook and any non-disclosure agreement before you publish a single screenshot. If you are unsure, use the description-only version and be ready to talk through the details in the interview instead.

Where to host it

Any of these work, and none of them require a website:

• Notion page with a public link, the fastest option for most people.
• Google Drive folder set to "anyone with the link can view." Put a one-page index first.
• A single PDF titled "Work Samples - Your Name," which is often the best choice for applications that ask for one file.
• GitHub README or a personal site if your role is technical, since it shows how you document things.

No login walls, no downloads required, no "request access" buttons. Test the link in a private browser window and open it on your phone. A portfolio that fails on mobile is a portfolio nobody finishes.

What to cut

• Certificate walls. Three relevant certifications at most, and only if the posting asks for them.
• Unpaid spec work for companies that never hired you.
• Dashboard screenshots you cannot explain when asked how the metric was calculated.
• A twelve-project dump. Three strong case studies beat twelve thin ones.

A two-weekend plan

Saturday one: list six candidate projects, pick three, and write the problem and result for each in bullet form. Sunday one: draft the full case studies. Saturday two: build the Notion page or PDF and write a two-sentence intro explaining what you do and for whom. Sunday two: send it to two people who do the job you want, and ask them what is unclear. Then send it to a recruiter in the same week, before the file starts collecting dust.