Staff+ Portfolio Checklist
Scope & Ownership
Your role in a cross-functional decision is explicit
Why recruiters check this: vague "we" language is the single most common reason a Staff+-level case study reads as Senior work.
At least one case study spans more than one team or product area
Why recruiters check this: single-feature scope is expected at Senior; Staff+ requires evidence of broader influence.
You describe a decision you made against pushback
Why recruiters check this: this is the clearest signal of design judgment, not just execution.
Narrative & Language
"I" appears in every key decision, not just "we"
Why recruiters check this: recruiters skim the first two paragraphs specifically for this pattern.
The problem statement includes the business or user stakes, not just the design brief
Why recruiters check this: shows you understood why the work mattered, not just what was asked.
You name at least one thing you'd do differently now
Why recruiters check this: retrospective judgment is a stronger Staff+ signal than a clean, conflict-free story.
Metrics & Outcomes
At least one metric is a shipped result, not a projection
Why recruiters check this: "projected to increase conversion" reads very differently from an actual measured outcome.
The outcome is tied to a business or user metric, not just a design metric
Why recruiters check this: "cleaner UI" isn't an outcome; retention, conversion, or time-to-task are.
You can explain how the metric was measured if asked live
Why recruiters check this: interview follow-up questions expose unverified or borrowed metrics quickly.
Cross-Functional Influence
At least one case study mentions influencing a PM or engineering decision
Why recruiters check this: Staff+ scope is defined by influence beyond your own team.
You describe how you handled disagreement with a stakeholder
Why recruiters check this: conflict-navigation is a core Staff+ competency interviewers probe for directly.
You can name who you mentored or unblocked on the project
Why recruiters check this: even in an IC track, Staff+ roles expect some multiplier effect on others.
Frequently asked questions
Generic checklists focus on presentation — layout, spelling, visual polish. This one is scoped specifically to Staff+ level criteria: scope, ambiguity, cross-functional influence, and outcome quality, sourced from actual hiring-panel and Toptal-vetting experience.
No — most strong candidates pass 10-12 of the 16 on their first self-audit. The value is in identifying which specific gaps to address before an interview, not achieving a perfect score.
Yes. The scope-and-judgment criteria apply to Staff+ hiring at any company; FAANG-level companies typically apply the bar more strictly, not differently — see theStaff Product Designer guide →for that distinction.
Partially. The Narrative and Metrics categories apply at any seniority; the Scope and Cross-Functional Influence categories are specifically what separates Senior from Staff+.