What changes from mid to senior
The transition from mid-level to senior portfolio is the most diagnostic shift in a UX career. Junior portfolios show production capability. Mid-level portfolios add judgement on contained projects. Senior portfolios show judgement on the surrounding system — the stakeholder management, the strategic context, the team direction, the business constraint, the work that wasn't shipped and why.
Hiring committees for senior roles aren't asking "can this person make screens?". They've assumed that since the recruiter screen. What they're testing is whether the candidate operates above the screen: setting direction, navigating ambiguity, influencing peers, owning outcomes that include both product and process.
For the pillar reference on what hiring managers look for at every level, see UX portfolio examples. The mid-to-senior pivot specifically is covered in senior vs junior UX designer. The full career-side context is in how to become a UX designer in 2026.
Leadership evidence
Leadership evidence in a senior portfolio doesn't require a formal management title. The signals hiring committees look for: mentoring teammates, leading critique, setting direction on ambiguous projects, building working rituals that improved the team, influencing roadmap decisions from a design perspective.
Strong leadership signals usually appear as part of a case study rather than as a separate page. "I led the project with two mid-level designers and ran twice-weekly critique sessions where we'd review each other's work against the brief" demonstrates leadership without claiming it as a title. The pattern that works: name the leadership move, name the impact on the team, keep it specific.
Senior portfolios that lack leadership evidence often lose the round at the executive interview stage. Even when the candidate has done leadership work, failing to write about it in the portfolio means the hiring committee can't credit it.
Strategic thinking
Strategic thinking is the senior portfolio signal that's hardest to fake and disproportionately rewarded. Hiring committees recognise it in three patterns.
Framing decisions before execution. The candidate writes about the moment they reframed a project brief. "The PM came to me with a request for a new screen; I argued that the underlying problem was different and we should redirect the project." Reframing moves are senior moves and they read as senior in the writing.
Naming what wasn't built and why. Senior case studies frequently include "the things we considered and didn't ship". The discipline of cutting scope intelligently is a senior skill that junior portfolios rarely demonstrate. Hiring committees read this as evidence of judgement under constraint.
Linking design decisions to business outcomes. "The redesign supported the team's quarterly goal of reducing the cost-per-acquisition by 15%" frames design as accountable to business in a way that's instantly recognisable as senior.
Business outcomes
Senior portfolios are expected to carry business outcomes, not just user outcomes. The framing isn't crude (no portfolio should be ROI-only) but it should make clear that the candidate understands design's role in the business.
Three outcome types work consistently:
Revenue-linked outcomes. "The flow change accounted for 14pp of the 19pp drop-off reduction quarter-on-quarter. Net new signups +14% against a baseline trend of +6%." Specific, attributed honestly, anchored to baseline.
Cost-linked outcomes. "The redesigned support flow reduced support ticket volume in the category by 38% across two quarters, which the team valued at ~£280k annualised." Cost reduction is sometimes easier to attribute cleanly than revenue and hiring managers credit it readily.
Risk-linked outcomes. For senior candidates in regulated industries (fintech, health, public sector), risk reduction is often the strongest available outcome framing. "The redesigned consent flow reduced regulatory escalations from 4 per quarter to 0 across the two quarters following launch."
For the deeper view of outcome writing, including how to handle confounders honestly, see case study examples. The before-and-after deep-dive in case study before and after covers the specific shifts in outcome framing that move a case study from mid to senior signal.
Stakeholder influence
Stakeholder influence is the senior signal hiring committees are explicitly trying to assess in the panel and executive rounds. Senior portfolios that surface stakeholder-influence evidence in the case studies pre-empt these rounds and convert better.
Three stakeholder patterns work:
The disagreement case study. A project where the candidate disagreed with a PM, engineering lead, or executive and navigated to a productive outcome. The strongest version names the tension specifically, includes the candidate's role in escalating productively (or in pulling back when they were wrong), and reflects on what they'd do differently. This case study consistently outperforms 'win' case studies at senior level.
The cross-functional partnership case study. A project where the candidate's primary value-add was bringing engineering, research, content, or brand into a design decision they'd otherwise have made alone. Demonstrates the cross-discipline operating system senior designers are expected to run.
The executive escalation case study. A project where the candidate had to take a design decision (or design risk) to an executive audience. Slide-deck artefacts from this case study often appear in portfolios and earn disproportionate attention.
The senior portfolios I've credited fastest in panel review were the ones with at least one case study where the candidate explicitly named a disagreement with a stakeholder and how they navigated it. The candidates who only show 'we aligned on the direction' lose this signal entirely. Disagreement isn't a weakness in a senior portfolio. It's the evidence of judgement.
Decision evidence
The decisions section is the heart of any portfolio case study, but it does different work at senior level. Junior decisions sections name the choice and the reasoning. Senior decisions sections name the choice, the reasoning, the alternatives considered, the trade-off accepted, the constraint the decision operated under, and the validation strategy applied (or not applied, with reasoning).
The pattern that works: three significant decisions per case study, each treated to a quarter to half a page of writing. Hiring committees spend most of their attention here, and the depth of decision writing is consistently the strongest single predictor of senior offer rates in our portfolio review work.
The full diagnostic on weak vs strong decisions sections is in case study examples and case study before and after. The portfolio mistakes piece covers the diagnostic failures that suggest missing decision evidence.
Systems thinking
Systems-level case studies are one of the strongest senior portfolio signals. The hiring committee question they answer: does this candidate think only about products, or do they think about the patterns that span products?
Systems case studies take several forms:
- Design system contribution. A specific component, pattern, or principle the candidate contributed to a design system, with the rationale and the adoption evidence.
- Accessibility framework. A WCAG 2.2 compliance project across a portfolio of products, with the audit methodology, prioritisation framework, and rollout pattern.
- Research operations. A research panel, repository, or synthesis ritual the candidate built, with evidence of adoption and impact on decision velocity.
- Cross-team design rituals. Critique cadences, design review processes, or operational patterns the candidate introduced. Particularly strong if the candidate names what they tried that didn't work.
One systems case study in a three-case-study portfolio signals seniority reliably. Three product case studies without systems work often reads as mid-level depth without senior breadth.
Portfolio expectations by level
What each level should surface
Junior (0–2 years). Production capability, problem framing, early signs of decision-making. 2–3 case studies, polish present but not the differentiator. Junior portfolio examples covers this depth.
Mid-level (3–6 years). Judgement under constraint on contained projects, stakeholder navigation, evidence of owning meaningful design decisions rather than just executing on briefs. 3–4 case studies.
Senior (6–10 years). Strategic thinking, leadership evidence, business outcomes, stakeholder influence, at least one systems case study, at least one honest failure case study. 3 case studies.
Lead and principal (10+ years). All of the above plus team direction, hiring philosophy, design strategy, executive stakeholder management. Portfolio often deprioritises case studies in favour of strategic artefacts. The systems and operating model become the primary content.
Failure case studies
The single highest-leverage move in a senior portfolio is including at least one case study on a project that didn't fully succeed. Three reasons.
First, hiring committees know the candidate has failed. Every senior practitioner has. Pretending otherwise damages credibility.
Second, failure case studies are the most predictive demonstrations of judgement. The framing — what the candidate could and couldn't control, what they'd do differently, what they learned — is where senior thinking is most visible.
Third, failure case studies disarm the interview round. Candidates who've already named a failure in writing handle the inevitable "tell me about a time you failed" question with significantly more credibility than candidates who present only wins.
The frame that works: name the situation honestly, describe what you and the team did and didn't control, describe the outcome with the same honesty you'd apply to a win, reflect specifically on what you'd do differently. Avoid two failure patterns: the disguised win ("we failed in that we didn't ship, but the team learned so much") and the blame story ("we failed because the PM was unreasonable").
For the broader interview preparation that picks up where the senior portfolio leaves off, see interview preparation guide and interview questions. For the salary and negotiation context that senior portfolios feed into, see UX designer salary UK and salary negotiation guide. The case study template covers the reusable structure that supports all levels.
If you want a senior-level portfolio review before submitting to a senior or lead role, independent reviewers on Fiverr with senior UX backgrounds typically charge £60 to £200 for a deeper written review.
Frequently asked questions
What does a senior UX portfolio show that a junior portfolio doesn't?
Decision evidence, strategic context, stakeholder influence, business outcomes, and at least one honest failure. Junior portfolios show production capability; senior portfolios show judgement on the surrounding system.
How many case studies should a senior UX portfolio have?
Three. Sometimes four. The strongest senior portfolios show three deeper case studies rather than five shallower ones.
Should senior UX portfolios include failed projects?
Yes. At least one case study on a project that didn't fully succeed builds significant credibility. The reflection layer matters more than the outcome.
Do senior UX portfolios need design system or systems thinking case studies?
Strongly recommended. One systems case study in a three-case-study portfolio signals seniority reliably. Three product case studies without systems work often reads as mid-level depth.