When a posting says "room to take on broader leadership over time," or a recruiter tells you scope increases once trust is established, you are being offered an option rather than a commitment. It might be worth something later. The conditions under which it pays out are set by the employer, and usually not written down anywhere.
So find out whether those conditions exist before you spend positioning energy on scope that may never arrive.
This sits next to The Gate Test without overlapping it. That piece tests whether the authority you're given on day one survives the next reorg. This one tests the growth trajectory itself: whether the expansion being pitched has terms anyone could point to.
Five dimensions of a verifiable scope promise
Run any expansion language against these five questions. Most promises clear none of them. Clearing all five is rare.
1. What specific result or milestone triggers expansion?
The trigger converts the option from potential to actual. "After trust is established" is not a trigger. A trigger is something you could point at: a shipped product, a revenue number, a team performance threshold, a date.
Ramp's Director posting contains the clearest expansion language in the current set. The Director will "start by owning a product area and team to build trust," with "room to take on broader leadership over time." Initial scope is named. Future scope is not. Building trust is a condition the employer assesses privately, with no external definition, and no stated result that converts "room to" into "you now own."
Gusto's Head of Design posting gets closer. It ties a specific change, reducing your hands-on design time, to a specific condition, team growth. That's closer to a trigger, though it still doesn't say what team size activates the change or who funds the growth.
Test it this way: Can you describe the trigger to someone outside the company in concrete terms? If you can't, the company hasn't defined one either.
2. Who holds the decision to grant it?
Scope doesn't accumulate. Someone approves it. Their identity, their incentives, and their actual authority to move territory to you determine whether the promise is worth anything.
At Director+ level, expansion almost always means taking something out of someone else's mandate. A VP who controls adjacent product areas can make that transfer. A peer-level design director cannot. If the person promising you growth doesn't control the territory you'd grow into, the promise is aspirational no matter how sincerely it's offered.
The postings give partial clues, though none names a grantor. Gusto describes the Head of Design as one voice in a Product–Engineering–Data quartet co-leading product direction. Expansion beyond the Unified Service Platform would therefore need buy-in from peers who own the adjacent territory, which puts the grantor above that quartet rather than inside it. Midjourney names a direct partnership with the Chief Design Officer, which at least identifies who controls the design mandate. Ramp's posting reveals neither the reporting line nor who owns adjacent product areas. Treat that absence as information. If public materials can't tell you who would approve your expansion, surface it in the first conversation.
Test it this way: "If the scope did broaden, who would that decision sit with?" A named person with a described relationship to the territory means the promise has a mechanism. A named process ("leadership would evaluate") means it doesn't.
3. What authority, headcount, or ownership actually transfers?
"Broader leadership" could mean three more direct reports and a second product area. It could mean a standing invitation to a meeting you weren't in before.
Gusto names one transfer plainly: as the team grows, your hands-on time drops and your hiring involvement rises. That is a real change in how you spend a week. It doesn't name additional product surfaces, budget authority, or reach beyond the Unified Service Platform. The expansion happens inside the current mandate.
Midjourney's Design Lead posting references a "growing portfolio of products" without specifying which products, what team supports them, or what authority the Design Lead would hold over new surfaces. The growth is implied by the company's trajectory rather than defined by the role.
Test it this way: If the expansion happened tomorrow, what changes on your calendar next week? If neither of you can answer, nothing has been defined.
4. Has anyone at the company received comparable expansion under similar terms?
Precedent is the strongest available evidence that expansion is structurally real. "Someone got promoted" is weaker evidence than "someone in a comparable role received the specific expansion being described to you."
Three companies in the current set have visible precedent worth probing.
Ramp. Diego Zaks moved from Head of Design to VP of Design between 2022 and 2025. What the public record does not show is what triggered the change, what authority came with it, or whether the path from Director, which is the current opening, follows the same terms. His trajectory being public is still useful to you. Asking what his path looked like, and how the Director role relates to it, reads as interest in the company's design leadership history while testing whether the expansion has a repeatable structure.
Headway. Ellen Dong went from founding designer to Head of Design as the team grew from 1 to 15. That's substantial, but a founding designer growing with a company from zero is a different trajectory from a mid-stage hire being promised future scope. It tells you less about your case than it appears to.
Vanta. Deb Kawamoto went from Head of Design to VP of Design and grew the team from 5 to 45 over roughly two and a half years. Real, visible, documented. She has since departed, and the current Head of Design posting opens at the title she started with, not the one she reached. Whether the incoming hire gets the same path is open, and it leads straight into the fifth dimension.
Test it this way: Can the company name a specific person in a comparable role who received the specific expansion under discussion, and say what triggered it?
5. What happens to the promise if priorities shift before the trigger is met?
This one almost never surfaces in postings or recruiter calls, and it matters most at companies where strategy moves quickly.
An expansion promise made during a growth phase can evaporate during a contraction. A promise attached to a product area disappears when that area is deprioritized. A promise contingent on "trust" can be deferred indefinitely by a new manager who never made the original commitment.
Vanta shows the structural version of this. Kawamoto's expansion happened: Head to VP, 5 to 45 people, a rebuilt leadership layer. The current posting resets to Head of Design. The organizational capacity she built is still there, since the posting describes roughly 40 designers, but the title progression didn't attach to the seat. It attached to her. If you're evaluating Vanta, the question worth asking is whether the terms of that expansion belong to the role or belonged to one leader at one moment in the company's growth.
No posting in the current set says what happens to a scope promise when conditions change, which is normal. It means the question has to come from you, and the quality of the answer tells you whether the company has treated expansion as a structural commitment or an intention.
Test it this way: Ask what would happen to the trajectory if priorities shifted before you reached the expansion point. A good answer references a process or a principle. A bad answer reassures you that priorities won't shift.
Two postings that sidestep the problem
Two postings in this set avoid the expansion-promise trap by attaching broad scope at entry.
Render's Staff Product Designer posting puts agent interfaces, human-agent handoffs, and trust/safety/governance in scope from day one. There is no future promise because the scope is present tense. What you verify changes accordingly: not whether it will expand, but whether that scope is real and resourced right now, which is a much easier thing to check in a screen.
Headway's Senior/Staff posting separates Senior and Staff scope explicitly. At Staff, roadmap influence, mentoring, and practice-shaping are in the job description rather than held out as a reward.
Both are better structural bets than a narrower role carrying a growth promise.
Refining the rubric
The scope-expandability score (1–3) has been operating on two defined endpoints with an underspecified middle. The diagnostic makes the distinction more precise.
Score 3 — Expansion is structural or already present. Scope is broad at entry, or expansion travels through mechanisms that already exist in the org (cross-team systems, platform layers, reusable infrastructure) without needing fresh executive permission each time. Render and Headway at Staff earn this on present scope. Vanta earns it on breadth of mandate, roughly 40 designers across five product areas from day one, with the title question still open.
Score 2 — Expansion is referenced with partial specificity. A condition, a change, or a direction is named, but key terms are missing. Ramp names an initial scope and gestures at broader leadership without defining trigger, grantor, or transfer. Gusto names a work-allocation change tied to team growth without saying what funds that growth or what exists beyond the current platform. You can ask about the missing terms. What you get back moves the score: structural backing pulls it to 3, a discovered ceiling drops it to 1.
Score 1 — Ceiling is structural. Surface-bound, advisory, or permanently dependent on a sponsor's discretion for any change in scope. Getting more would require a different role, not growth in this one.
Questions that surface real terms
For recruiter screens and hiring manager conversations. Each one reads as interest in the role while testing whether the expansion has structure.
For the trigger: "You mentioned the role could expand over time. Can you walk me through what that would look like, and what would need to happen for it to be on the table?"
For the decision owner: "If the scope did broaden, who would that decision sit with? Is that something my direct manager would own, or does it go through a broader leadership review?"
For the transfer: "When you say broader scope, are we talking about additional product areas, more headcount, a different reporting relationship? What would actually change?"
For precedent: "Has anyone in a similar role here had that kind of scope expansion? I'd love to understand what that path looked like for them."
For priority shifts: "One thing I've learned from past roles is that company priorities can shift. If the business moved in a different direction before that expansion happened, how would that affect the trajectory we're discussing?"
Specific, concrete answers to three or more of these mean the expansion promise has terms worth evaluating. Warmth and generality across all five mean the person offering it means it and the company has no mechanism to deliver it. Score accordingly.
- Formal vs. real authority: Aghion and Tirole's distinction between the right to decide and effective control over decisions applies directly to scope promises — their framework explains why a title expansion can leave operative leverage unchanged.
- Org structure isn't destiny: McKinsey's analysis of three million designers across 100,000+ departments found no single organizational structure associated with better design-team integration, which means reporting-line promises deserve the same verification pressure as scope promises.
- Design management needs executive backing: A 2024 study of 200 respondents found that design-management maturity didn't directly improve product-innovation performance — top managers' design-management expertise mediated that relationship, suggesting expansion without senior sponsorship may not deliver the influence it implies.
- Atlassian's portfolio expectations: Their published interview handbook asks candidates to show specific contribution, collaboration, success measures, and learnings — a useful template for how to present scope-expansion evidence from past roles where your mandate did grow.