Building a Portfolio That Gets You Hired in the US

For roles where a portfolio is expected — design, product, writing, engineering with public code, marketing, video — the portfolio frequently outweighs the résumé in the hiring decision. The reason is straightforward: the résumé describes work in your words; the portfolio shows it in your output. A weak résumé with a strong portfolio passes more often than the reverse.

Most US-market portfolios fail in the same predictable ways: too many pieces, no narrative, no problem statement, and a hosting choice that fights the reader. This guide is about the choices that get a hiring manager to spend 5 deliberate minutes instead of 30 distracted seconds.

Why portfolios decide more than résumés

Hiring managers in creative and technical disciplines are looking for two signals a résumé cannot give them: actual quality of output, and the ability to explain a decision. The portfolio answers both at once. A case study that walks through a real problem, a real constraint, a real trade-off, and a real result — in your voice — is something a résumé bullet cannot replicate.

This is also why portfolios that look good but say nothing under-perform. A polished collection of screenshots with no narrative tells the reviewer that you can produce visuals but cannot reason about them. The reasoning is the part that matters at hire time.

Format choices by discipline

The right format depends on what you do:

• Product designers: a personal site with 3–5 case studies. Behance and Dribbble are fine for sourcing inspiration but rarely the primary portfolio for senior US roles, where reviewers expect a custom site.
• UX/research: 2–3 deep case studies, often as PDFs or Notion pages, prioritizing the research process over the final UI.
• Software engineers: a clean GitHub profile with 3–5 pinned, well-documented repos. A README that explains the problem, decisions, and limitations matters more than star count.
• Writers and content strategists: a portfolio site with bylines or PDF clips, organized by category. For B2B writers, including a sample of work for similar companies converts.
• Marketers and growth: case studies with measurable results — campaigns, channels, attributed lift — clearly anonymized where required.
• Data and analytics: a mix of GitHub (notebooks, dashboards) and written narrative explaining the question, dataset, method, and finding.

The case-study structure that works

A US-market case study that holds attention follows a tight structure:

1. Context (3–4 sentences): Where did this work happen? What was the company, the team, your role? Anonymize what you must.
2. The problem (2–3 sentences): What specific decision or constraint was on the table? Be concrete: "Conversion on the checkout flow had dropped 12% in Q2 and the team had two weeks to ship a fix."
3. What you tried (1 paragraph): The two or three approaches you considered, and why you picked the one you picked. This is where you show judgment.
4. What you shipped (with artifacts): Screenshots, code links, designs, the document, the campaign. Caption every artifact with one sentence explaining what it is and why it matters.
5. Result (1 paragraph): What happened? Numbers if you have them. Qualitative outcome if you do not. Honest about what did not work.
6. What you would do differently (2–3 sentences): The reflection. Reviewers in the US disproportionately value candidates who can name a limitation in their own work without prompting.

The reflection step is the one most portfolios skip. It is also the one experienced hiring managers explicitly look for — not because they want self-criticism, but because it signals a candidate who learns from work rather than just produces it.

Choosing 3 pieces, not 12

The default instinct is to show everything. The right move is the opposite. A portfolio with three strong, recent, varied case studies outperforms one with twelve average ones. The reviewer will spend 5 minutes either way; deciding which 5 minutes you control is the entire game.

Pick pieces along three axes: recency (one in the last 12 months ideally), relevance (matches the role you want, not the role you had), and range (showing different problem types, not three flavors of the same project). Cut anything older than 5 years unless it is genuinely your strongest work, and even then explain why you chose it.

Showing work under NDA

Most US portfolios run into NDA constraints. Three approaches handle this without losing the case:

• Anonymize: blur or rename, keep the structure. "A B2B SaaS company in healthcare" works. Reviewers respect this.
• Password-protect: publish a public summary, share the password to the full case study only with the hiring team after a first conversation.
• Recreate: for design and writing, build a version with public-domain content that demonstrates the same skills without breaching NDA. Label it clearly as a recreation.

What does not work: showing screenshots with company logos and metrics if your contract prohibited it. Hiring managers in the US take this seriously, especially in regulated industries — your willingness to bend the rule reads as how you will treat their NDA next year.

Where to host without distractions

The hosting choice should disappear. Three options work consistently:

• A custom site on a clean domain (yourname.com), built with a fast static generator. Carrd, Astro, Hugo, or even a one-page handwritten HTML/CSS site loads instantly and stays maintainable.
• Notion or Read.cv for design and product roles where the format is now common.
• GitHub Pages for engineers — your code is already there.

Avoid: heavy single-page apps that load a 2MB JavaScript bundle before showing the first case study, slideshow autoplay, music, hover-to-reveal patterns, and dark patterns that hide navigation. Reviewers leave.

Walking through it live

The portfolio review interview is its own format in the US — common in design, increasingly common in product. Treat it as a planned 30-minute talk: 5 minutes intro, 20 minutes on one case study (not three), 5 minutes for questions. Pre-screen-share. Open the case study before joining the call. Have one anecdote per slide ready.

The strongest portfolio walkthroughs feel like a conversation, not a presentation: pause for questions, surface trade-offs proactively, and admit limitations before the reviewer asks. The candidates who get offers are usually the ones who could be running the meeting on the other side.

Questions readers ask

Do I need a portfolio for non-creative roles in the US?

For most non-creative US roles, no — but supporting artifacts help. A clean LinkedIn, a few public posts, or a one-pager describing a project you led can serve the same purpose without calling it a 'portfolio'. The expectation rises fast in product, design, engineering, and content.

How recent should portfolio pieces be?

Aim for at least one piece from the last 12 months. Anything older than 5 years should appear only if it remains genuinely your strongest work and you can explain why. Stale portfolios signal that the work happened, not that the candidate has continued growing.

Should I include personal projects?

Yes, when they fill a gap your professional work cannot — different industry, different scale, different toolchain. Personal projects should be labeled clearly as personal and treated with the same case-study rigor as paid work, not dropped in as evidence of effort.