We tear down a lot of portfolios on Feedback Friday. The ones stuck between junior and mid-level almost always look good — clean layout, solid UI, a case study template in place. The gap is not aesthetics. It is evidence of judgment.
Here is what we tell candidates when they are trying to make that jump.
Three audiences, one portfolio (pick a primary)
Every case study is read by three people:
- Recruiters — skimming for fit and keywords
- Hiring managers — looking for problem-solving and scope
- Future peers — deciding if they would want to work with you
You cannot optimize equally for all three in every project. Pick the primary audience per case study and let the structure follow.
Recruiters and hiring managers need outcomes. Future peers care about who you are — that is what your about page is for.
Do not hide your process behind accordions
A pattern we see constantly: research and requirements on the surface, architecture and design principles tucked into collapsed sections. The intent is good — keep the story clean for casual visitors. The result is bad — hiring managers skim headings and never discover the work you buried.
Sacrifice the accordions. Show the full arc: how you understood the user, how you scoped the problem, how you prioritized, what you built, and how you knew it worked.
The section most junior portfolios skip
The failure mode for strong junior work: problem statement → ideation → final screens. What is missing is the middle — mapping, prioritization, trade-offs, constraints, alignment with stakeholders. That middle section is what separates “can make nice UI” from “can own a product surface.”
If you are targeting UX or product design, the story should be user-outcome oriented. If you are targeting UI craft, output-heavy case studies are more acceptable — but you still need to show decision-making, not just deliverables.
Output vs. outcome
Output: “Built an AI-powered job-fit tool that analyzes descriptions in 7 seconds.”
Outcome: “Gave recruiters a faster way to validate whether candidates match role requirements.”
Same project. Different story. Mid-level portfolios lead with the outcome and use the output as proof.
Rename sections honestly. If your “Impact” section describes a deliverable you shipped, it is an output section. Rename it or rewrite it.
Metrics when you do not have metrics
Hard numbers are ideal. Most candidates — especially in enterprise or healthcare — do not have access to them.
Use behavior change instead: what do users do differently now? “Analysts no longer export to Excel to share findings” is not a conversion rate, but it is real momentum.
Tease impact near the top of the case study, then go deeper at the bottom. Senior reviewers look for that signal early.
Storytelling titles for skimmers
Hiring managers scroll your case study the same way recruiters scroll your resume — headings only.
Rewrite section titles so each one summarizes the paragraph beneath it:
- Weak: “Design requirements”
- Strong: “Four stakeholder groups needed the same data surfaced differently”
If someone reads only your headings, they should still understand your process.
What to cut as you level up
- Double diamond diagrams as the centerpiece — fine for students and teaching, less convincing as a senior signal
- Gimmick projects without a clear hook — interactive tools are great if they solve a stated problem for a named audience; otherwise they read as novelty
- Gallery layouts masquerading as case studies — label projects, show there is depth behind the thumbnail, or recruiters will assume graphic design when you mean UX
The jump from junior to mid is not more projects. It is more visible thinking in the projects you already have.