UI, UX, Product, and Principal aren’t four jobs, and they aren’t nested boxes where each title contains the last. They’re four altitudes — and what separates them isn’t how much you know, it’s where your hours go. Every curve below holds the same area, because everyone has the same hours. Moving right trades depth for reach.
UI
Is it right?
Craft that survives close inspection.
Starts at
A screen to improve
Ends at
The final comp
What hiring managers look for
Typography, spacing, and grid discipline
Every component state — hover, focus, disabled, error, loading, empty
Responsive behavior and dark mode reasoning
Design system fluency: tokens, variants, when to extend vs. comply
Motion and interaction detail — timing, easing, choreography
Evidence: close crops, before/afters, spec-level annotation
Red flags
Hero shots only, no states
Beautiful screens with no system underneath
Accessibility as an afterthought
The tell
A weak UI case study says “I made it beautiful.” A strong one says “I made it legible under this specific constraint.”
UX
Does it work?
Evidence that changed the design.
Starts at
A user problem
Ends at
Validation that it works
What hiring managers look for
Problem framing grounded in real user data
A research method, and what it overturned
Information architecture and flows
Edge cases, error paths, recovery
Iterations that visibly killed an earlier idea
A behavioral metric: task success, time on task, error rate, drop-off
Red flags
Research theater — five interviews the final design ignores
Personas with no consequences
A happy path with no branches
No evidence that anything was ever wrong
The tell
It shows you changing your mind because of evidence. If you were right the whole way through, it reads as a story, not a process.
Product
Was it worth it?
Judgment under constraint.
Starts at
Ambiguity — no defined problem yet
Ends at
Shipped and measured
What hiring managers look for
Why this problem and not the other three on the list
The constraints that shaped it — eng cost, timeline, legal, platform, existing customers
What you cut, and what it cost you to cut it
How you worked with PM and engineering, and where you disagreed
How it shipped, what it moved, and what happened after launch
A product metric — activation, retention, conversion — with a baseline and a timeframe
Red flags
You were handed a defined brief and executed it well — that’s UX
A redesign that never shipped
“Increased engagement 40%” with no denominator
Nothing was ever cut: no constraints, or no ownership
The tell
You made a call under uncertainty where the wrong call had a real cost. Scoping is the signature move — the v1/v2 decision is the most Product-Design thing in any case study.
Principal
Should we do this at all?
Design that changed what the company decided, not just what it built — reached as an IC, not a manager.
Starts at
A bet the company is making
Ends at
A change in company direction
What hiring managers look for
Fluency in how the company actually makes money
Competitive positioning; pricing and packaging awareness
Portfolio-level thinking — which bets, in what order
Capability building: systems, process, team
Outcomes in revenue, cost, retention economics, or market position
The strongest version: you framed a problem the exec team then funded — or you killed something
Red flags
Business vocabulary sprayed on a Product case study with no decision attached
ROI figures with no attribution story
Strategy narrated in hindsight, with no sign you shaped the call while it was live
The tell
It explains why the company should care, and the answer isn’t “because users liked it.”
Titles, arcs, and red flags describe how case studies tend to read at each altitude, not a rulebook — the point is to read the arc, not the label.
