Job search
Product Design Portfolio for Job Applications: Choose Cases That Prove Your Contribution
Choose product design portfolio cases that match the role, show your contribution clearly, and give reviewers a concise, accessible way to assess your work.
If you are applying for product design jobs, choose portfolio cases that prove the craft and scope named in each role—not simply the projects with the most polished screens. Lead with the strongest relevant case, then show the problem, your own decisions, the people you worked with, the constraints, and an outcome you can support. There is no universal required case count or portfolio format; employer instructions and role expectations vary.
Read the job description, then compare its requirements with evidence you can show. If you are still comparing openings, browse recent roles on LandOffer.ai and note the craft each one emphasizes before rearranging your work. LandOffer publishes this guide, so treat the link as a job-search starting point, not a portfolio assessment or hiring promise.

Choose cases against the work in the role
Think of a portfolio as a short argument: “Here is the kind of design work I can do, and here is evidence from projects where I did it.” Examples include a shipped flow, prototype, research synthesis, service blueprint, design-system contribution, or school project; choose evidence that lets a reviewer assess this opening’s skills.
Read the posting for its specific craft. A role focused on mobile onboarding may call for a case that shows interaction states, content clarity, and how you handled uncertainty on a phone screen. A design-systems role needs evidence about component behavior, governance, documentation, or cross-team adoption. A generalist role at an early-stage company may value a broader mix. Do not infer all of that from “Product Designer” in the title: responsibilities vary by company and level.
Figma’s early-career guide favors work that shows skills, process, impact, a clear problem, milestones, and learning. A Figma recruiter also advises tailoring projects and labeling the medium and your role. These are employer perspectives, not a universal rubric; both point to the value of making relevant evidence easy to find.
When several projects look equally polished, a clear case order helps a reviewer see where your judgment is strongest. The scorecard below turns the job description into a practical selection decision. It is a sorting aid, not a score that predicts an interview.
| Target opening | Case that leads | What the case can prove | What it cannot prove by itself |
|---|---|---|---|
| Consumer mobile product designer | Appointment-booking flow | Mobile interaction design, error recovery, and a decision about rescheduling | That the candidate owned research, engineering, or business results performed by teammates |
| Design-systems product designer | Component-library contribution | Variant logic, documentation, accessibility states, and collaboration with engineers | That every product team adopted the system or that it reduced defects without measured evidence |
| Early-stage generalist designer | A compact set: booking flow, internal operations tool, and a research-to-prototype exercise | Breadth across customer-facing and internal work, plus the ability to explain trade-offs | Deep specialist expertise in every area represented |
For each candidate project, ask four questions: Does it show a requirement from this posting? Can I explain my part precisely? Is the evidence safe to share? Can a reviewer understand the result without a private tour? A project that fails the safety check should not be published in its current form, however impressive it looks.
A completed role-to-case example
The following designer and projects are fictional. This is a teaching example, not a report about a real candidate or employer.
Maya is applying to two roles. Opening A emphasizes mobile customer journeys, interaction details, and accessible patterns. Opening B is a small-company generalist role asking for customer-facing product work, internal tools, and close collaboration with engineering. Maya has three projects:
| Project | Evidence Maya can show | Her contribution | Sharing status | Opening A fit | Opening B fit |
|---|---|---|---|---|---|
| Appointment rescheduling | Annotated flow, prototype states, and a before/after copy decision | Led the rescheduling flow; partnered with a researcher and two engineers | Sanitized screenshots approved for public use | Lead | Include second |
| Internal dispatch tool | Task map, table layout, and handoff notes | Designed the operator workflow; PM owned prioritization | Can share recreated diagrams without customer or company data | Omit unless space | Lead or second |
| Student food-pantry finder | Research notes, responsive prototype, and a short test summary | Solo class project, from interviews through prototype | Self-created work; no employer data | Supporting case | Include third if the role values broad ownership |
Maya should put rescheduling first for Opening A and the dispatch tool first for Opening B. The school project is not automatically weaker because it was not shipped; it is useful when it provides relevant evidence that the work portfolio lacks. At the same time, Maya must label it as a class project and avoid implying a launch or production result. If she cannot explain a decision or substantiate a result, she should narrow the claim or choose another case.
That is a better use of tailoring than swapping a few keywords on the landing page. Keep the underlying project record consistent. Change the order, short descriptions, and depth so the most relevant evidence appears first, and make sure each version still identifies the project accurately.
Tell a case story that makes your contribution visible
A strong case study does not need to document every workshop, wireframe, or meeting. It should help a reader follow the decisions that connect the problem to the work you show. A useful sequence is:
- Context: What product or service was involved, who used it, and what situation prompted the work?
- Problem and constraint: What needed to improve, and what limited the possible solutions—time, technical behavior, policy, research access, or existing patterns?
- Team and role: Who else contributed? What did you lead, decide, make, test, or hand off?
- Evidence and alternatives: What did you learn, what options did you consider, and why did you choose this direction?
- The work: Show a few annotated artifacts at the point where they explain a decision. Include important states, not only a pristine final screen.
- Outcome and reflection: State what changed and how you know. Separate a prototype finding, a shipped change, a measured result, and a lesson for next time.
This structure is flexible. Atlassian’s current design interview guide, for example, describes its own 45-minute portfolio review and asks candidates to present a 10-minute case followed by questions. Its guidance values recent work, relevant craft, problem-solving approach, collaboration, success measures, and learning. That is a concrete reason to practice a concise walkthrough—but the timing belongs to Atlassian’s process. Follow the instructions for the role you are applying to; another company may request a different format or no presentation at all.
Make collaboration legible without shrinking your own role. “I designed the search filters” is clearer than “we revamped discovery” if filters were your contribution. Then name the PM, researcher, engineer, content designer, or other partner and explain the decision they shaped. If you led one part of a shared system, identify the boundary: the components you owned, the states you documented, or the handoff you coordinated. Credit is not a footnote; it helps a reviewer understand how you work with a team.
Be equally precise with outcomes. If you have an approved launch metric, name the measure, comparison period, and your relationship to it so the reader can judge what changed. If you only have a prototype observation, call it that. If the work shipped but you cannot access later data, say so. A project can still show sound judgment when the outcome is mixed or the original solution was revised. Figma’s early-career guide explicitly treats learning and what you would change as useful parts of the story; you do not need to manufacture a success statistic to make the case worthwhile.
A completed case-study excerpt
This fictional excerpt shows one way to describe a team project. All project details below are invented for instruction; they are not a real employer case or a performance claim.
Appointment rescheduling | Product designer on a four-person team
Problem. In a prototype review, participants could find an appointment but were unsure whether choosing a new time would preserve the existing booking until confirmation. The exercise did not establish how often this happened in a live product.
My part. I mapped the rescheduling path, designed the time-selection and confirmation states, and wrote the explanatory labels. A researcher planned the sessions; an engineer explained which appointment states the service could return; the PM set the release scope.
Decision. One option replaced the original booking as soon as a new slot was tapped. Another kept the old booking visible until the user confirmed the new time. I chose the second for the prototype because the service could not guarantee a new slot before confirmation. The design made the existing booking and pending choice visible together.
Outcome. The prototype review surfaced confusion around whether the original appointment remained active. We revised the confirmation copy and state labels. The project account has no production conversion data, so I do not claim a measured reduction in missed appointments.
The excerpt names the design work, the team's contributions, the decision and the limits of the evidence. In an actual portfolio, Maya would replace the fictional details with facts she is allowed to share, show only approved artifacts, and link the claim to an available source such as a project readout or documented launch note. If no source can support a number, she should leave the number out.

Handle unreleased, confidential, or collaborative work carefully
A project is not automatically safe to publish because you worked on it or because a screenshot appeared in an internal presentation. Review the rules that apply to the work and ask the former or current employer for permission when needed. Do not include customer names, private data, unreleased screens, internal roadmaps, or restricted metrics without authorization. This is practical portfolio guidance, not a legal interpretation of a contract.
You can often show the reasoning without reproducing the original interface. Remove identifying data, use a clearly labeled reconstruction, simplify a flow into abstract states, or describe the decision and constraint in text. Do not present a recreated screen as a real production screenshot. If you cannot safely share even a redacted artifact, explain the work at a higher level or choose a different project. A reviewer needs enough evidence to understand your contribution; they do not need confidential material.
School, volunteer, and personal projects can fill a gap if you identify their context and limits. Name the audience as prospective or represented users when no real research participants were involved. Distinguish a prototype from a shipped product and a class critique from a customer test. For an unsuccessful or abandoned project, explain what changed, what you learned, and what evidence you had at the time. Honest boundaries make the case easier to discuss under follow-up questions.
Make the portfolio easy to review
The case itself is only useful if the reviewer can reach it. Before you apply, open the portfolio link in a private browser window or on a device where you are signed out. Confirm that the landing page tells the viewer what kind of work you do, project links open, images load, and any embedded prototype does not require an invitation or paid account. If the portfolio is behind a password, provide it through the employer's requested channel. Keep a PDF or concise slide deck ready if the application system only accepts files or a recruiter asks for an alternate format.
Check the site with a keyboard and at a narrow viewport. Give informative images text alternatives, keep headings descriptive, make links understandable out of context, and avoid conveying a state only through color. The W3C’s Web Content Accessibility Guidelines 2.2 include requirements for text alternatives and keyboard operability. A quick personal check does not certify conformance, but it can catch obvious barriers that would keep someone from reviewing your work.
Finally, proofread labels and captions as carefully as the interface. Figma’s portfolio guidance calls out spelling and usability; a busy reviewer should not have to decode custom navigation or guess where a case begins. Put the role, product context, and your contribution near the start. Use a short caption to orient each image, then explain only the design choice it helps prove. Keep detailed process material available as a secondary link when it adds value.
Your final portfolio check
Before applying, confirm that the first case matches the role’s main craft, project roles and collaborators are labeled, and outcomes are supported. Check sharing permission, remove sensitive details, test the link while signed out, and follow employer instructions. Explain why older work remains relevant; do not lead with weaker evidence solely because it is newer.
For each opening, reorder cases and tighten their previews so relevant proof is easy to find. Keep a stable master portfolio and record what you sent to prepare for follow-up questions. To find suitable openings before you tailor the portfolio, browse recent tech roles on LandOffer.ai.
Sources and Further Reading
- Product design portfolio tips from a Figma recruiter — recruiter-authored advice published in 2019; useful perspective, not a universal standard.
- Breaking In: A Guide To Landing Your First Product Design Role — Figma's early-career guide to portfolio storytelling and showing design decisions.
- Atlassian Design Interview Guide — Atlassian-specific portfolio review format and criteria.
- Web Content Accessibility Guidelines (WCAG) 2.2 — W3C Recommendation for web-content accessibility.




