The Senior Designer Test Nobody Puts In A Job Description

A portfolio with ten polished wins is a weaker hiring signal than one with a single documented failure the candidate would still defend. Ask ten hiring managers what makes a designer senior, though, and most will still describe volume: more screens shipped, more systems built, a heavier portfolio.

Nielsen Norman Group surveyed 204 user experience (UX) hiring professionals about what they actually look for when reviewing a portfolio, and found a specific, repeated mismatch: candidates build case studies around polished final screens, while the reviewers surveyed report wanting the process behind the decisions instead. That is a sourced finding about reviewer preference, not a claim about who gets an offer. It means the part most portfolios cut, the moment a plan changed, a constraint forced a worse version to ship, an assumption turned out wrong, is exactly the material reviewers say they are checking for.

A second, older body of evidence explains why that material outweighs polish. Schmidt and Hunter's meta-analysis of roughly 85 years of personnel-selection research found that structured interviews built around specific past behavior predict job performance nearly as well as work-sample tests, and considerably better than years of experience or unstructured interviews (Schmidt & Hunter, 1998). Their data spans a huge range of occupations, not design specifically. But the underlying mechanism, that evidence of how someone behaved under real conditions outpredicts credentials, is not occupation-specific by construction; it is what the aggregated data show holds across the roles the meta-analysis pooled.

Schmidt and Hunter's analysis also found that combining a structured interview with another valid method, such as a work-sample test, produced higher predictive validity than either method used alone. Applied to design hiring, that detail argues against treating a strong portfolio and a strong interview as substitutes for each other. They appear to be more informative combined than either is by itself, which is a reason to weight both rather than letting a polished portfolio stand in for the interview or the reverse.

What that evidence looks like in practice is visible in this portfolio's own ThoughtSpot Mobile case study, which documents a trade-off instead of a clean win. More than thirty iterations went into the voice-input states, a feature a minority of sessions actually used, and the write-up states plainly that the attention for it came out of the budget meant for flows people touch every day, then affirms the states were worth getting right without claiming the ratio was. That is not a headline metric. It is the kind of falsifiable, behavioral account both findings above point toward, documented on one project, not proof any hiring panel would weigh it the same way.

Nielsen Norman Group's 2026 State of UX report describes this mismatch getting more consequential rather than less: it frames competitive roles as increasingly rewarding breadth of judgment over interface output, arguing that user interface (UI) production itself is becoming cheaper and less differentiating as tooling absorbs more first-draft execution, while contextual research, critical thinking, and discernment remain the comparatively durable signal (Nielsen Norman Group, State of UX 2026). That is the report's characterization of the current hiring landscape in 2026, not a claim this piece is testing directly, and it describes exactly the shift from artifact volume to judgment the older personnel-selection data above already predicted on separate grounds.

The strongest case against this argument is a real confound, not a minor caveat. Narrating a messy decision well is its own skill, correlated with confidence, coaching access, and verbal fluency, not only with design judgment. A candidate who has never been taught how to package ambiguity into a tidy story can hold exactly the judgment Schmidt and Hunter's data predicts and still read as junior on a storytelling axis that has nothing to do with it. Rewarding the performance of reflection risks trading one shallow signal, visual polish, for another, narrative polish, instead of reaching the behavior underneath either one. The boundary of this argument follows from that confound: it holds for a candidate who can narrate a trade-off, and says nothing about one who can defend it clearly under direct questioning but was never coached to package it into a story.

• If you are leveling up, rewrite one project around the moment the direction changed, not the final screens, and name a trade-off you would still defend.
• If you are hiring, ask for the project that did not go cleanly, then probe a stated trade-off with a direct why and listen for a specific answer.
• Score the specific decision under ambiguity, separately from how comfortable the candidate is describing it.