Portfolio & Hiring Signalswhat the evidence looks like

The two archetypes leave different evidence. A portfolio, an interview, and a first impression all read differently depending on which archetype the practitioner represents, and hiring or evaluating against the wrong one is among the most common mistakes in senior design hiring.

A Design Strategist portfolio is less a collection of screens than a collection of case studies that argue from user truth through business consequence, each showing the Strategist’s upstream work leading to a specific decision the organisation made differently as a result. The core artefacts are framing documents, research outputs, strategic frameworks, and written arguments. Supporting artefacts (workshop outcomes, stakeholder-facing presentations, decision records) show how the strategic work travelled through an organisation. Each case study is diagnostic in shape: the brief as received, the brief as diagnosed, the evidence behind the reframe, the decision that followed, the outcome. A Strategist portfolio without case studies in this shape shows upstream familiarity at best.

An Experience Engineer portfolio is a collection of shipped artefacts at production fidelity, with systems-level evidence of the governance and architecture behind them. The core artefacts are running code, production-quality motion, governed design systems, and specific craft decisions shown at the level they were made, often with links to live products, design-system documentation sites, and motion reels where the craft can be experienced rather than described. Each case study is diagnostic here too: the production problem, the architectural decision, the trade-off it protected, the specific craft move that solved it at fidelity. An Engineer portfolio full of static Dribbble screens is showing mid-spectrum craft at best, well short of the archetype.