How much to talk — Principal timebox and altitude
Expected question
"You're interviewing for Principal AI Architect. How do you spend a 45-minute design round — and how is that different from Staff?"
Variant forms
- "What should a Principal say in the first two minutes of a vague 'design an agent platform' prompt?"
- "How much architecture is too much in a coding round?"
- "When do you stop optimizing and declare the design good enough?"
- "How do you show org blast radius without a catalog of demos?"
- "What's the difference between a 30-second thesis and a 15-minute walkthrough?"
- "How do you run the last ten minutes with a skeptical principal on the other side of the table?"
- "What would make us downlevel you to Senior in the same loop?"
- "How do you talk about open-source proof vs employer production without blending them?"
The question, as it might actually be asked
"Walk me through how you'd use 45 minutes on an AI platform design. What do you cover, what do you skip, and how would I know you were Principal and not Staff?"
Executive summary
30-second thesis
I'd spend the clock on a default under constraints, one deny path, and one hard NFR — not a component tour. Principal is reusable mechanism plus blast radius. Staff is a strong design. Senior is a working design. I'd rather lock isolation and HITL than name every box.
2-minute answer
First three minutes are questions that change the design: who the tenant is, which tools write to the real world, the SLO that actually hurts, residency, what already exists. Then a 30-second default: access before ranking, gateway or HITL on irreversible writes, an eval that can fail a build. Eight to twelve minutes walking one path through the system including the fail-closed path. Ten minutes on the NFR that would kill this product — noisy neighbor, cache bleed, or resume-after-crash — not all three.
What I'd refuse: Kafka before requirements, a menu of vendors with no pick, and turning a coding round into a platform. Recap in thirty seconds: decision, discarded alternative, success metric.
Staff often has the same boxes. Principal says who inherits the standard, what we'd reverse on, and what we will not boil this quarter. If every story ends at "my team shipped," I'm Staff-shaped. If another team reused the gate, I'm closer.
The framework
Full clock and altitude tables: PRINCIPAL_DELIVERY.md.
Design round — agenda I'd say out loud
I'd like two minutes to lock constraints, then a default, then isolation/deny, then one deep dive. If we have leftover time, cache bleed or FinOps — you pick.
Saying the agenda is itself a Principal signal. Interviewers are grading whether you can run a room, not whether you can fill a whiteboard.
Coding round — stop line
Lock the contract. Correct version. Complexity once. Two tests. One production extension in a sentence ("I'd mutex this; I will not design Redis Cluster unless you open that door"). Then stop.
Behavioral — 90 seconds, not a memoir
Situation + your task. Decision and what you rejected. Conflict. Result with a window and a definition. Mechanism left behind. One thing you'd do differently. If there is no mid-course correction, it sounds inflated.
Honesty clause (required on AI Principal loops)
Open proof is inspectable. Employer production is a different class. Demos may be labeled Demo vs Strict. I would rather name a cold start than click a broken tab.
What to talk about (high leverage)
| Topic | Why it lands at Principal |
|---|---|
| 3–5 clarifying questions that change the design | Ambiguity is the job |
| A chosen default + reversal evidence | Owns the decision |
| Deny path / fail-closed | Production, not demo theater |
| Who inherits the standard | Org blast radius |
| Week-1 ship vs explicit non-goals | Multi-horizon, not a rewrite |
| Demo vs Strict / O vs P | Trust |
What is unnecessary (or harmful)
| Anti-pattern | Why it hurts |
|---|---|
| Drawing every microservice | Clock death; looks Senior-busy |
| Portfolio tour | Sounds like a catalog, not a peer |
| Invented SLOs | One follow-up ends you |
| Title talk | "I'm a Principal" without a reused standard |
| Gold-plating coding | Wrong round |
Interview-ready summary
Principal delivery is timeboxed judgment: default, deny, one deep dive, recap. The document is backup. The panel hears whether other teams could run this without you.
What's expected at each level
- Mid-level: Completes the asked task; needs prompting for trade-offs.
- Senior: Solid design in 45 minutes; skips deny path unless asked.
- Staff+: Unprompted constraints, blast radius, stop line in coding.
- Principal: Runs the agenda; reusable mechanism; multi-horizon; honesty about Demo vs Strict; invites the interviewer to pick the leftover deep dive.