Role
Product designer
Design hiring is moving away from the polished case study, because the polish is now free. What survives is the reasoning — and reasoning is a sentence with a date, not a Dribbble shot.
A product designer decides how a thing works, not only how it looks, and is accountable for whether people can use it. The best evidence is usually about something removed.
What most listings require
End-to-end product work
What it screens for: Whether you have taken something from problem to shipped and watched it be used.
A sentence that proves it"I designed our onboarding from the first interview to the shipped flow, and watched twelve people use it before we called it finished."
Research
What it screens for: Whether your decisions have evidence behind them.
A sentence that proves it"I ran the usability sessions that showed nobody understood our pricing table; three of five people chose the wrong plan."
Interaction and systems
What it screens for: Whether your work holds together past one screen.
A sentence that proves it"I built the component library and the rules for it; the one about never setting a component’s own margin is why our pages stopped drifting."
Accessibility
What it screens for: Increasingly a legal requirement and still rare in portfolios.
A sentence that proves it"I took our forms to AA contrast and keyboard parity; the audit list and the fixes are both in the design file."
Working with engineers
What it screens for: Whether what you design gets built as designed.
A sentence that proves it"I sit in the engineering stand-up; our handoff is a shared file and a conversation, not a spec thrown over a wall."
What counts as a bonus
Writing
What it screens for: Interface copy is design, and most designers avoid it.
A sentence that proves it"I rewrote our error messages so each says what happened and what to do; support tickets about the upload error went to zero."
Prototyping in code
What it screens for: Whether you can test an interaction rather than describe it.
A sentence that proves it"I prototype in HTML when motion matters, because a Figma prototype cannot show what a 300ms delay feels like."
The requirement nobody writes down
Whether you have changed your own design after watching somebody fail to use it. That single story separates designers who test from designers who present.
Where candidates come up short
- What was removed. A design improved by deletion is the strongest story and the least told.
- Accessibility with a concrete audit attached.
- What happened after it shipped — most portfolios stop at launch.
Related roles
Product designer: questions
- What is the one thing product designer listings screen for without writing it down?
- Whether you have changed your own design after watching somebody fail to use it. That single story separates designers who test from designers who present.
- What do candidates for product designer roles most often fail to evidence?
- What was removed. A design improved by deletion is the strongest story and the least told. Accessibility with a concrete audit attached. What happened after it shipped — most portfolios stop at launch.
- How do I turn this into something a company can check?
- Tell the agent what you actually did, in sentences like the examples on this page. Each becomes a claim carrying that sentence and the date it holds for, and a company matching you against a listing sees the requirement, the claim, and your own words behind it.
Prove it, requirement by requirement.
Write sentences like the ones on this page and each becomes a claim with a date. Then match yourself against a real product designer listing and read what is still unmet — that list is the plan.