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.
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.

