Listing what you did ≠ telling your story
Most case studies walk through the process in order: what you did first, what came next, but never explain why each decision was made.
Recruiters don’t need to know what you did. They need to understand how you think.
Using “we” the whole time hides your contribution and personality
Using “we” shows respect for your team. But the recruiter is interviewing you, not your team.
You don’t need to take credit away from anyone, just make it clear what your part was in your case study.
Visually appealing, but still hard to read
Without a clear visual hierarchy, white space, consistent color use and even spacing, the reader’s eye doesn’t know where to go.
Before thinking about “beautiful,” ask: “Can anyone actually read this?”
The project’s done. So what did you actually learn?
Most case studies end at the deliverable. But personal reflection is what separates junior from senior thinking.
What did you learn? If you could redo it, what would you change? What questions are still unanswered?
Missing context and outcomes
Recruiters look at dozens of portfolios a day. If they can’t understand your project within the first 30 seconds, they move on.
And after everything is presented, what was the result? Even if it’s small or qualitative, say it.
Every case study needs:
- Context
- Problem
- Your role
- Process
- Outcome
- Key takeaway
To sum it up
A great portfolio isn’t just beautiful, it’s convincing:
- Guide your reader with intention
- Make your individual contribution visible
- Keep your layout clear and hierarchical
- Always include personal reflection
- Give context and show impact in every case