The Inversion
The company described the role as strategic, design-led, growing. You sent case studies and references. They sent adjectives.
Formal authority — title, reporting line, posted scope — routinely diverges from real authority, which lives with whoever controls the decision when design and product disagree. McKinsey found 90% of CEOs did not regularly involve design leaders in strategy, even at companies with CDO titles.
Ask in the first call: "When Design believes something should not ship and Product believes the bar is met, who decides?" If the answer names a process, the authority is diffuse. If it names a person and says whether design can delay launch, you have something to evaluate.
Apply the same pressure to scope. "The role will grow" is an option with employer-controlled exercise conditions. Ramp's Director posting says scope "may expand after building trust" — honest, but the trigger is undefined and the decision is theirs. Ask: "Who was the last person whose mandate actually expanded, what changed, and who authorized it?" If nobody can name that person, the growth language is decorative.
Reading Real Authority in the First Conversation
The first conversation with a hiring manager is the highest-value intelligence event in your search, and most of it gets spent on the material you need least: their description of the role. What you came for is everything around it. How they react when you put a concrete artifact in front of them. Whether they can name the machinery between a design decision and a business outcome. How specific the scope promises get when you push. Three probes, applied differently across all four tiers, with the framework for reading mandate quality live.
Testing Whether "This Role Will Grow" Has Real Terms
"Room to take on broader leadership over time." "Scope increases after trust is established." That's an option, not a commitment, and the employer sets the conditions under which it pays out. Five questions, applied to current postings from Ramp, Gusto, Vanta, Midjourney, Render, and Headway, test whether expansion language has terms behind it or just goodwill. Includes a refinement to the scope-expandability score and screen questions that read as interest in the role while surfacing whether the growth is defined.
When Accountability Arrives Before Authority
You get hired to fix design quality. By week three, someone asks why it hasn't improved. You haven't changed the review process because you're still learning which teams use one. You haven't hired because headcount is tied to a fiscal plan you didn't build. The question lands anyway. Every Director+ role has two dates: when you start being evaluated on outcomes, and when you gain power over the inputs. The gap between them varies by company type. This piece maps each version and gives you the questions that surface it before you accept.
Will the Mandate Survive the Next Reorg?
Every company hiring a Head of Design will describe a strong mandate. Budget, headcount, executive sponsorship. What they won't volunteer: whether any of it survives if the person describing it leaves. Twitter's CDO role lasted four days past Dorsey's departure. At Expedia, the VP of Design Practice Management watched his mandate dissolve in a reorg. IBM eliminated its general manager of design entirely. This piece maps the structural signals that were readable before each collapse — and the indicators you can investigate before you reach the offer stage.