Capstone, the interview spine & self-assessment

Everything you've learned compresses into one structure you can run from memory when the room gets hostile, the VP interrupts, or you blank. The spine is not a script — it's a load-bearing skeleton. Seven beats, in order, that turn any messy enterprise conversation into a coherent path from where work waits today to what gates the expansion.

Why a spine and not talking points? Because under pressure you don't lose your facts — you lose your order. You start defending a feature before you've established the risk it must respect, or you quote a metric before anyone agreed on the baseline. The spine fixes sequence so each beat earns the right to the next. Master it and you can be interrupted at beat 4, dragged back to beat 2, and still know exactly where you are.

The recurring closing message rides on top of all seven: the work is to expand autonomy as fast as the evidence allows, and not one ring faster. That single line reframes every objection — speed, security, cost, skepticism — as a question about evidence and guardrails rather than a fight about whether AI is good.

Knowing the seven labels isn't the skill. The skill is knowing what work each beat does, and the single best question that opens it. Here's the operating detail behind each beat, with the named controls and metrics you reach for.

Beat 7 deserves its own disciplineexpansion is earned

Beat 7 — Expand — is where weak reps invent a timeline ('then we roll out org-wide in Q3') and strong reps name a gate. A gate is a condition: 'when the pilot cohort holds DORADORA metrics. Four widely-used delivery measures: deployment frequency, lead time for changes, change failure rate, and time to restore service. change-fail rate flat while lead time drops 20%, we expand to the next two teams.' Conditions are defensible; dates are hostages. Organizations (GA to Enterprise ~June 2026) is the structural answer to 'expand' — one admin plane over many teams, each with its own governance and budget, Groups for cohort-level model access and spend.

These are the ten scenarios you will face, in some form, in a Cursor Field Engineer loop. The bar is 8 of 10 fluent — meaning you can run the spine through each one and name specific controls, features, and metrics, not generic reassurance. Fluent means: no hedging, no 'it depends' without a fork, and at least one named artifact (a control, a feature, a number) per answer.

Before you walk into a loop, score yourself honestly against these ten. Each is a capability — something you can do live, not a fact you can recite. The bar for each is: could you do this in front of a skeptical buyer, right now, without notes?

1. 1Run the full 7-beat spine cold, in order, on a use case you've never seen — and recover when interrupted.
2. 2Open discovery and stay in beats 1–3 without demoing, finding the queue and the controls.
3. 3Name the enterprise control surface from memory: SSOSingle Sign-On. One company login (usually via SAML or OIDC) instead of a separate password per tool./SCIMSystem for Cross-domain Identity Management. A standard for automatically creating and removing user accounts when people join or leave., RBACRole-Based Access Control. Granting permissions by role rather than configuring each person individually., model/MCPModel Context Protocol. A standard that lets an AI agent pull in context from outside the repo, like Jira tickets or internal docs./repo allowlists, hooks, terminal sandboxing, audit logs, AI-code tracking.
4. 4State the security posture precisely: SOC 2 Type II, AES-256 at rest, TLS 1.2+, annual pen test, Privacy ModeCursor's setting that routes requests under zero-data-retention terms so providers don't store or train on your code. + ZDRZero Data Retention. A contractual guarantee that the model provider won't store your code or train on it. (and the own-keys caveat), PrivateLinkAn AWS feature that keeps traffic to a service on your private network instead of the public internet./Cloudflare Tunnel.
5. 5Map a customer's value streamThe end-to-end path a change takes from idea to running in production. to DORADORA metrics. Four widely-used delivery measures: deployment frequency, lead time for changes, change failure rate, and time to restore service.'s four keys and identify which one the pilot will move.
6. 6Design a guardrailed pilot: cohort, allowlists on, sandboxing on, audit on, baseline captured.
7. 7Articulate the autonomy ladder — unattended vs. gated vs. forbidden — and how hooks/SoDSeparation of Duties. No single person can author, approve, and deploy the same change. The core control AI autonomy has to respect. enforce it.
8. 8Convert any objection (hype, free, security, skeptical senior) into an evidence-and-guardrails question.
9. 9Quote proof responsibly: Box (85%+ DAU, 30–50% throughput, 80–90% less migration effort), 64% of Fortune 500 — and flag perishable stats as verify-before-quoting.
10. 10Define expansion as a gate, not a date, and tie it to Organizations/Groups.

Talk is beat 4. The portfolio is beats 5 and 6 made tangible — artifacts that prove you've actually done the work, not just memorized the vocabulary. Seven pieces, mapped to the spine. In a loop, the candidate who opens a real current-state map beats the candidate who describes one.

The spine, the drills, the artifacts — they all rest on one posture: you are not there to sell AI. You're there to expand autonomy as fast as the evidence allows, and not one ring faster. Walk in as the person who makes risk smaller, not the person who makes risk go away by ignoring it.

The strongest Field Engineers in the room sound less like vendors and more like a careful internal champion the customer wishes they already had. They lead with the customer's constraints, not the product's capabilities. They say 'no' to a bad use case faster than they say 'yes' to a good one — because a failed unbounded pilot poisons the whole account, and a small proven one earns the next ring.

Close the loop the way you'd close a customer: not with a feature, but with the recurring message. Find where work waits. Name what must hold. Earn each ring with evidence. You can be interrupted, doubted, and dragged off-script — and still land there. That's what 'fluent' means, and that's what walks you through the door.