UX case studies that actually get you hired
Hiring managers skim. A case study has a few seconds to show how you think. Here is the structure we teach, and the mistakes we see most.

Most junior portfolios show beautiful final screens and almost nothing else. They look impressive for two seconds, and then the reviewer moves on, because the screens don't answer the only question that matters: how does this person think?
Hiring managers often have dozens of portfolios to review. A case study gets a few seconds to earn a closer look. The good news is that a clear structure does most of the work for you.
A structure that works
- The problem, in one sentence a stranger understands.
- What you learned from real users, with one surprising finding.
- Two options you explored and rejected, and why.
- The final design, shown in context rather than floating mockups.
- The result, with a number if you have one.
Lead with the problem
Start with the problem, not the app. "Students missed class changes because announcements were buried in a group chat" is far more compelling than "A mobile app for a training centre".
Show your thinking, not just your pixels.
Show what you threw away
Rejected options are the strongest evidence of judgement. A sketch of a layout you abandoned, with one line on why, tells a reviewer more than another polished screen ever could.
Mistakes we see most
- Walls of text with no headings to skim.
- Process diagrams copied from articles, unrelated to the project.
- No mention of what users actually said or did.
- Ten case studies of medium quality instead of three strong ones.
Rewrite, then rewrite again
In the UI/UX path, trainees rebuild their case studies at least twice, with feedback from the trainer and from developers in the other paths. Every rewrite gets shorter and clearer. By the end, a reviewer can understand the whole story from the headings alone, and that is exactly the test we use.






