A job interview portfolio is a small, organized set of work evidence. It can be a PDF, a private web page, or a few printed pages. Its job is to help an interviewer understand what you did, why it mattered, and how you think. Designers often show finished visuals, but a project coordinator, analyst, writer, operations specialist, or career changer can also show process, decisions, and outcomes when sharing is permitted.
Choose the role before choosing the samples
Read the job description and circle three capabilities the employer will likely evaluate. Then select at most three examples that demonstrate them. A good set may include one project you completed, one problem you improved, and one collaboration where your contribution is clear. More examples are not automatically better; a long archive can hide the evidence that matters.
Do not include a sample because it looks impressive but has no connection to the role. If the new job requires stakeholder communication, a simple process memo may be more useful than a polished graphic. The resume skills guide can help you identify the evidence behind a claim.
Turn each sample into a case-study card
Give each example a one-page structure: the context, the challenge, your responsibility, the actions you took, the result, and what you learned. Use plain language. If you worked on a team, state who did what. For example: “I organized weekly customer reports and designed the issue-tracking sheet; the product lead prioritized the fixes.” This avoids taking credit for a team's entire result.
Quantify outcomes only if you can verify the number and share it. If the project had no measured result, describe the observable change: a new checklist was adopted, a handoff became documented, or a decision became easier to make. An honest account of a mixed result can also show judgment. Explain what you would change next time rather than pretending every project was a success.
A complete example card for an operations role
Context: A small team handed new customer requests between two shared inboxes. This fictional example illustrates the format; it is not a claim about a real employer. Challenge: Owners were sometimes unclear, so a request could sit in either inbox. My responsibility: As the coordinator, I documented the handoff; the team lead retained responsibility for staffing and priorities. Actions: I mapped the existing steps with the team, drafted a one-page ownership checklist, tested it on sample requests, and revised the language after feedback. Result: The team adopted the checklist for its weekly handoff. I would only report a faster response time if the team had measured and approved that number for sharing. What I learned: A simple ownership rule can be more useful than a larger tool when the main problem is ambiguity. A permitted sample card could show the reconstructed checklist, labeled clearly as an illustration.
Protect confidential and personal information
Review employer agreements and permission rules before sharing any work. Remove customer names, private metrics, internal screenshots, unpublished strategy, personal data, and proprietary code unless you have clear authorization. Redaction must be real: covering text visually in a PDF may leave the underlying text selectable. When in doubt, create a fresh, generic reconstruction that demonstrates your approach without reproducing restricted material, and label it as a reconstruction.
For public-sector or regulated work, check the organization's specific rules. A hiring manager's interest does not override an obligation to protect information. If you cannot share a document, tell the story verbally and describe the type of artifact you created. A portfolio should strengthen trust, not create a concern about what you might reveal from the next employer.
Make it easy to scan
Put your name, target role, and a short contents list at the start. Use readable type and descriptive headings. Each case-study card should make sense without your live explanation. Add a short caption to every image or chart that says what it shows and whether data is illustrative. A digital portfolio should be accessible without a login for the intended reviewer, unless privacy demands a controlled share.
Test the PDF or web page on a phone and a laptop. Confirm the links work, the file is reasonably sized, and the text is selectable where possible. Do not assume the interviewer will open a complex interactive site during a call. Have a simple offline or printable version available if the meeting format supports it.
Practice using the portfolio in conversation
Choose one page for each likely question. If asked about collaboration, open the relevant card and explain the decision your team faced. Avoid reading the entire portfolio aloud; use it as evidence for a concise answer. The behavioral interview guide can help you structure the spoken story around your actual contribution.
Ask whether the interviewer would like to see a sample before screen sharing. If they prefer a normal conversation, answer the question and offer to send the portfolio afterward. If you do send it, provide only the role-relevant version. A portfolio is a supporting tool, not a requirement for every job or a substitute for strong interview answers.
A final five-minute check
Can you explain why each sample belongs? Is every claim true and attributable? Have you removed restricted details? Can someone understand each page in under a minute? Does the file open from the link you plan to send? If the answer to any of these is no, simplify before adding more work. A compact, trustworthy portfolio beats a decorative one that leaves your role unclear.