Principal leadership — org design and decision rights

Expected question

"How would you organize AI platform vs product teams — and who gets decision rights when they conflict?"

Variant forms

• "Design the operating model for AI across six product lines."
• "Central platform vs embedded AI engineers — what do you choose and why?"
• "Who can override a safety/eval gate under deadline pressure?"
• "How do you keep Principals from becoming a bottleneck for every design review?"
• "What decisions do you refuse to federate?"

Executive summary

30-second thesis

I'd centralize the irreversible controls — identity, side-effect gateway, eval gates, tenancy — and federate prompts, UX, and domain workflows. Decision rights without expiry become politics; politics without a written veto become incidents.

2-minute answer

I'd draw two columns on the whiteboard: invariants and local choices. Invariants (authZ before retrieve, gateway before tools, golden evals before promote) have a named owner and a hard veto. Local choices (tone of prompts, which workflow ships first) stay with product.

Conflict path: product wants bypass → timeboxed exception with owner + expiry → if they need permanent bypass, that's an architecture change with security/eval in the room, not a Slack thumbs-up.

What I'd refuse: a Principal who reviews every PR, or a "center of excellence" that writes strategy decks and owns no runtime control plane. Leverage is standards other teams inherit — not hero reviews.

Framework

Skeptical follow-ups

• "Won't central gates slow us down?" Slow is relative — one unreviewed refund tool is slower than a week of process.
• "What if the central team is the bottleneck?" Publish SLAs for reviews; auto-approve low-risk changes; hire until the invariant plane has on-call, don't delete the gate.
• "How do you know it's working?" Exception rate, mean time to revoke, % of side effects with audit — not number of ADRs written.

Staff+/Principal signal rubric

• Senior: names central vs federated.
• Staff+: names veto owners and exception expiry.
• Principal: designs the conflict path and measures that the org uses the control plane without you in every thread.

Related

• 03 centralize vs federate
• 01 what Staff+ signals