On Deck | Signal Watch

Priority Action Queue

Priority Action Queue — Week of July 10, 2026

By Reva Sandoval— July 10, 2026

Feature image for article: Priority Action Queue — Week of July 10, 2026

Three postings, all aging past day 30. Freshness can't separate them, so mandate integrity is the filter: which role carries real design authority, and which one hangs a leadership title over a production seat? Ramp's recruiting cluster is the cleanest signal. A dedicated design VP, a coordinated function-build, and AI-native mandate language that maps directly to your trust essay. Headway's provider-workflow scope is strong but the buyer is a product leader, and the authority structure needs reading. Kiddom's "rebuild quality" language is genuinely ambiguous. Each entry includes a sendable outreach message, the diagnostic question that tests whether the role is worth your time, and the one thing not to say.

Priority Action Queue

Priority Action Queue — Week of July 10, 2026

By Reva Sandoval— July 10, 2026

Three postings, all aging past day 30. Freshness can't separate them, so mandate integrity is the filter: which role carries real design authority, and which one hangs a leadership title over a production seat? Ramp's recruiting cluster is the cleanest signal. A dedicated design VP, a coordinated function-build, and AI-native mandate language that maps directly to your trust essay. Headway's provider-workflow scope is strong but the buyer is a product leader, and the authority structure needs reading. Kiddom's "rebuild quality" language is genuinely ambiguous. Each entry includes a sendable outreach message, the diagnostic question that tests whether the role is worth your time, and the one thing not to say.

The 100 List

The 100 List — Your Detection Grid for Design Leadership Hiring Moments

By Reva Sandoval— July 10, 2026

Feature image for article: The 100 List — Your Detection Grid for Design Leadership Hiring Moments

One hundred companies sourced from a16z, Sequoia, and Greylock portfolio boards, all plausibly under $100M in valuation with over $10M in revenue, scored by how likely their next design leadership hire would be visible from public signal before it fills through someone's group chat. Only one company in the entire pool has an active Director+ design posting right now — and it's 111 days old. The real value is in the precursors: IC design clusters, founding designer searches, and executive arrivals that predict a leadership role 4–12 weeks out. Ten clusters. Fifteen live postings. Five to act on this week.

The 100 List

The 100 List — Your Detection Grid for Design Leadership Hiring Moments

By Reva Sandoval— July 10, 2026

One hundred companies sourced from a16z, Sequoia, and Greylock portfolio boards, all plausibly under $100M in valuation with over $10M in revenue, scored by how likely their next design leadership hire would be visible from public signal before it fills through someone's group chat. Only one company in the entire pool has an active Director+ design posting right now — and it's 111 days old. The real value is in the precursors: IC design clusters, founding designer searches, and executive arrivals that predict a leadership role 4–12 weeks out. Ten clusters. Fifteen live postings. Five to act on this week.

Not This Week

Five targets from your list generated signal this week. None warrant outreach investment right now. You've got a posting that quietly expired, an ATS path behaving unreliably, two companies where the roles sit below your level, and an executive departure that blew up a product org overnight.

None of these are dead. Each one has a specific trigger that would flip it back to active. The value here is protecting your prep time. Spending three hours tailoring materials for a role that stopped existing six weeks ago is the most expensive mistake in a senior search, and it's invisible until you've already made it. Below: the company, the hold reason, and what changes the call.

Not This Week

Five targets from your list generated signal this week. None warrant outreach investment right now. You've got a posting that quietly expired, an ATS path behaving unreliably, two companies where the roles sit below your level, and an executive departure that blew up a product org overnight.

None of these are dead. Each one has a specific trigger that would flip it back to active. The value here is protecting your prep time. Spending three hours tailoring materials for a role that stopped existing six weeks ago is the most expensive mistake in a senior search, and it's invisible until you've already made it. Below: the company, the hold reason, and what changes the call.

Stale Posting

Suno Design Lead Posting Dies at Eighty Days

Head of Product Design went up April 21. No repost, no hiring-manager activity, nothing. Meanwhile, Spark incubator's perpetual identity-rights terms and non-disparagement clauses have drawn fire from creators and labels alike. Check back when: a fresh design leadership posting surfaces, or governance around creator rights gets meaningfully clearer.

Mixed Visibility

Capital One AI Design Director Needs Verification

R243245 (posted May 28) loads via direct URL but won't surface reliably across Capital One's search and category pages. Daniela Jorge's CDO transformation agenda remains credible. The source path just needs to confirm clean before you invest outreach hours. Check back when: stable ATS discoverability returns, or a new transformation-oriented design leadership req drops.

Language Harvest

Gusto Has AI Trust Vocabulary, Not a Role

No Director+ design role posted. But the Senior Product Design Manager, Payroll listing is worth reading for its AI-native vocabulary alone: user agency, uncertainty design, graceful error handling, automation trust. Steal that language for outreach at regulated-workflow targets like Headway. Check back when: a senior design leadership req appears.

Watch Only

Anthropic Shows No Design Leadership Opening Yet

Two design-adjacent roles validate your AI trust and human-capability themes (Design Engineer, Education Labs; Policy Design Manager, Age-Appropriate Design). Both sit well below your target level and neither hints at a leadership search forming behind them. Check back when: a Director+, VP, or Head of Design req appears.

Org Flux

OpenAI Product Org Scrambles After Simo Exits

Fidji Simo left her No. 2 role yesterday. Brockman and Friar are absorbing product and business responsibilities. No fresh Director+ design posting on the Ashby board, and there's no identifiable design buyer until the dust settles. Check back when: the org structure firms up or a design leadership req goes live.

The Kiddom Question

The One Question That Tells You Whether Kiddom's Director of Design Owns Anything

Ask this early: "When design's quality standard conflicts with product's timeline, who decides?"

The posting says you'll have "full latitude to rebuild how we think about design quality." That phrase is doing heavy lifting. It could mean you set and enforce quality gates that product cannot override. It could also mean you raise concerns that product weighs against the schedule and overrules when convenient. You need to know which one before you invest preparation time in this role.

Kiddom's own signals cut against the aspiration. The Sr. PM posting says product leaders "sit at the center" of the operating model. AI trust and safety ownership lives in PM, not design. The Director qualifications ask for a "track record of influencing roadmap." Influencing, not owning. And there are zero IC design postings on the board alongside this role, which means either you inherit a small team with no growth budget or IC hiring is gated on your arrival. Both of those require budget authority and structural backing to navigate, and the posting doesn't confirm either.

If the answer names a process or a person, keep talking. If the answer is "we figure it out collaboratively," that's your signal.

The Kiddom Question

The One Question That Tells You Whether Kiddom's Director of Design Owns Anything

Ask this early: "When design's quality standard conflicts with product's timeline, who decides?"

The posting says you'll have "full latitude to rebuild how we think about design quality." That phrase is doing heavy lifting. It could mean you set and enforce quality gates that product cannot override. It could also mean you raise concerns that product weighs against the schedule and overrules when convenient. You need to know which one before you invest preparation time in this role.

Kiddom's own signals cut against the aspiration. The Sr. PM posting says product leaders "sit at the center" of the operating model. AI trust and safety ownership lives in PM, not design. The Director qualifications ask for a "track record of influencing roadmap." Influencing, not owning. And there are zero IC design postings on the board alongside this role, which means either you inherit a small team with no growth budget or IC hiring is gated on your arrival. Both of those require budget authority and structural backing to navigate, and the posting doesn't confirm either.

If the answer names a process or a person, keep talking. If the answer is "we figure it out collaboratively," that's your signal.

TAKE NOTE

Real authority sounds like:

"The Director can block handoff to engineering on quality grounds"
"Design enters before product requirements are written"
"You'll own headcount planning for the design team"
"Design system changes require Director sign-off — engineering can't route around it"
"The Director runs designer performance reviews independently"

Soft mandate sounds like:

"Design owns execution once product defines the what"
"The VP of Product really respects good design"
"We're still figuring out how design and product share decisions"
"You'll influence through relationships and great work"
"Final call sits with the PM on their area"

Follow-up probes if the first answer is vague:

How many IC designers are on the team today, and what's the 12-month headcount plan?
Does the Director have a blocking vote at any stage of the product development process?
Who owns design system governance when engineering wants to diverge?

Kiddom-specific context: Glassdoor management responses acknowledge product teams "weren't sufficiently involved in decisions" under the prior structure. The VP of Product is a recent hire building out the org. You'd be their first design leadership appointment, which means the authority lines haven't been drawn yet. You want to know whether you're being hired to draw them or to operate inside ones already set.

Suno's Governance Test

Suno Spark and the authority gap you'd inherit

Suno's Spark incubator launched with a perpetual non-disparagement clause, a 60-day competitor exclusivity lock, binding arbitration, and a class-action waiver. The terms were co-authored by Suno's Chief Music Officer and Head of Creative Economy. Not design. Not product. The Head of Product Design posting describes "simple, joyful, and intuitive user experiences" and design system ownership. Trust & Safety reports through engineering. No policy design role exists on the Ashby board.

The Spark controversy created trust debt that a design leader would visibly own in the market. Creators, press, and the music industry now associate Suno's brand with extractive terms. But every public signal says the decisions that generated that debt sit in Legal, Music, and Business leadership. Design gets to style the page after the language is already locked.

If a warm path opens, spend your first conversation on decision rights. You need to know whether this role can shape creator-facing policy or only present it.

Suno's Governance Test

Suno Spark and the authority gap you'd inherit

Suno's Spark incubator launched with a perpetual non-disparagement clause, a 60-day competitor exclusivity lock, binding arbitration, and a class-action waiver. The terms were co-authored by Suno's Chief Music Officer and Head of Creative Economy. Not design. Not product. The Head of Product Design posting describes "simple, joyful, and intuitive user experiences" and design system ownership. Trust & Safety reports through engineering. No policy design role exists on the Ashby board.

The Spark controversy created trust debt that a design leader would visibly own in the market. Creators, press, and the music industry now associate Suno's brand with extractive terms. But every public signal says the decisions that generated that debt sit in Legal, Music, and Business leadership. Design gets to style the page after the language is already locked.

If a warm path opens, spend your first conversation on decision rights. You need to know whether this role can shape creator-facing policy or only present it.

Five questions that surface whether design holds authority or just accountability:

Who drafted Spark's terms? Legal, Music, or Business? Did design review, gate, or veto any creator-facing language?

Who owns trust repair? If Suno softens the "Good Vibes Only" clause, does that come from Legal, the CMO's team, or the design org?

Does this role have decision rights over creator-facing terms? Not styling. Can the Head of Product Design change what a disclosure says, or only how it looks?

Where does creator experience sit? The PM, Artists & Creators role owns discovery and monetization. What does design own end-to-end?

Is there a design voice in incident learning? When a creator-trust failure hits press, who runs the response? Engineering T&S? Legal? Or does design have a seat?

If every answer routes to "we'd love your input" and nobody names a decision gate, you have your answer.