Drill 01 — Tell Me About Yourself
The opener. Most candidates botch it because they treat it as a résumé read. Good candidates treat it as a 120-second narrative thesis. Strong Hire candidates land it at "and that's why this seat at Apic, now."
The prompt
"Tell me about yourself."
Variants you'll hear: "Walk me through your background." "How did you get to where you are?" "Tell me your story."
Time budget: 90 to 120 seconds. Recruiter screens often want 60–90; HM screens often want 90–120. Default to 120, learn to compress to 60 on demand.
Why this drill matters
It's the first 2 minutes. The interviewer's brain is forming a Strong Hire / Lean No first impression in real time. You don't get to fully recover from a Lean No here — every subsequent answer is read against this opening frame.
The job is not to summarize your résumé. They have your résumé. The job is to give them a narrative thesis: "here's the through-line of my career, here's why it leads to this seat, here's why now."
The Strong Hire structure
Three beats, ~40 seconds each:
Beat 1 — The anchor (~40 sec)
The longest-running thread in your career. Not a chronological start — the thematic start. Pick the one professional thread that's been continuous and that connects to this role. State it as a thesis sentence, then 2–3 specific, recent proofs.
For an Applied AI Architect, the strongest anchors are: - "I've spent the last several years as the customer-embedded technical voice for enterprise AI deployments — the architect customers turn to when they need to translate ambiguous business problems into shippable systems." - "My career has been building the bridge between AI capability and enterprise reality, especially in regulated industries." - "I've operated as the technical advisor enterprises trust to translate AI capability into safely-deployed production systems."
Pick the anchor that's most defensible by your actual work history, not the one that sounds best.
Beat 2 — The arc (~40 sec)
Two or three career chapters that build toward the seat. Not every job — two or three that make the case. Each chapter is one sentence stating the chapter's role + the highest-leverage signal from it.
The signals to optimize for, ranked by Apic relevance: 1. Customer-embedded technical leadership 2. Regulated-industry / safety-first delivery 3. India/APAC enterprise customer fluency 4. Building 0-to-1 (squad, practice, product) 5. Multi-cloud / multi-LLM platform breadth
Beat 3 — The convergence (~40 sec)
The "and that's why this seat, now" close. Two ingredients:
- Why this role specifically (not generic AI passion — specific to the Applied AI Architect shape, with one Apic-specific reference)
- Why now (a forward statement about what the next 2–3 years should look like, that this seat uniquely enables)
The convergence is what differentiates a Strong Hire from a Hire on this drill. Most candidates land Beat 1 and Beat 2 fine; very few stick the convergence.
What gets each grade
Strong No
- Chronological résumé read from college onwards
- Lists every job
- Closes with no convergence — just "and now I'm here"
- Visible nervousness, or filler ("um, so I started in...")
Lean No
- Solid résumé summary, no narrative thesis
- The arc is just job titles, not a through-line
- No mention of why this role or why now
- Closes with a generic interest in AI
Hire
- Has a clear anchor and arc
- Connects to the role at the close
- Missing one of: a specific Apic reference, the "why now" forward statement, principal-level confidence in delivery
Strong Hire
- Anchor is a thesis sentence, not a job description
- Arc selects 2–3 chapters that earn the convergence
- Convergence has both: specific role-fit (this seat, not generic SA) AND a "why now" forward statement
- Delivered in 90–120 seconds, with calm cadence and zero filler
- Lands at "and that's why this seat at Apic, now" without sounding rehearsed
Common Lean No traps
- Starting at college. "I graduated in 2010 from..." is a Lean No before sentence two. Start at the anchor.
- Listing every job. A senior candidate has 5–8 jobs. Mentioning all of them eats your time budget. Pick 2–3.
- Outcome-only sentences. "I led a 15-person team and improved customer satisfaction by 40%." Numbers without context are noise. State the chapter's role, not just the metric.
- Generic close. "And I'm passionate about AI, which is why I want to work at Apic." Lean No, every time. Be specific.
- Defensive close. Mentioning the lateral move unprompted in TMAY is a mistake — it's defensive. Save it for when asked. The TMAY close is forward-looking, not justifying.
- Over-rehearsed delivery. If it sounds like you memorized it word-for-word, you sound like a politician. Memorize the structure and the key phrases; let the connecting tissue be live.
Practice protocol
- Write the 120-second version in full. Don't bullet-point it. Write it as you'd say it.
- Read it aloud once. Time it. Adjust to fit ≤120 sec.
- Bullet-point the structure. Anchor → arc (chapter 1, chapter 2, chapter 3) → convergence (role-fit, why now).
- Speak from the bullet points — never the full text again.
- Compress to 60 seconds. Same structure, fewer words. The recruiter screen often wants this version.
- Record yourself doing both versions. Listen back for cadence dips, filler, defensive notes.
- Iterate until the convergence sentence lands every time without feeling rehearsed.
Personal anchor
Suggested anchor (your strongest, by evidence weight)
"I've spent the last several years as the customer-embedded technical voice for enterprise AI deployments — the person customers turn to when they need to translate ambiguous business problems into shippable production systems, especially under regulatory constraint."
This anchor is defensible by your actual work history (the healthcare AI consultancy, the GenAI services firm FDE squad, the global investment bank FSI, the US financial services firm NLP, the global SI customer-embedded delivery). It also lands the load-bearing words for this role: customer-embedded, technical voice, enterprise, production, regulatory constraint.
Suggested 2–3 chapter arc (the strongest signal-to-time selection)
- the healthcare AI consultancy (current) — Solutions Architect, AI & Analytics Practice — "Most recently, architecting Claude- and LLM-powered multi-agent platforms in healthcare, with HIPAA-aligned data sovereignty as the design constraint."
- Signal: regulated-industry, safety-first, Claude-aware (this matters for credibility)
- the GenAI services firm — Lead, AI Forward Deployed Engineering — "Built and led a 15-person GenAI Forward Deployed practice from zero — embedded with enterprise customers across BFSI, healthcare, retail, and energy, delivering agentic and RAG systems in production. The motion that mattered: the squad coded alongside customer engineers, not from slide decks."
- Signal: 0-to-1 build, FDE motion, multi-vertical, production-grade, principal-level operational scale
- (Optional 3rd) the global investment bank + the US financial services firm + the venture builder — "Before that, production AI in regulated FSI — surveillance at the global investment bank, NLP at the US financial services firm — and a year as the venture builder EIR embedded with India/APAC AI/SaaS founders, which is where I built my view of how this market actually adopts AI."
- Signal: India/APAC ecosystem fluency, FSI depth (closes the BFSI loop without saying "BFSI" explicitly)
Pick chapters 1 and 2 always; chapter 3 only if you have time budget. Prioritize completing the convergence.
Suggested convergence (the close that lands)
"What I want to be doing for the next two to three years is being the trusted technical advisor for Indian and APAC enterprise customers — especially regulated ones — adopting Claude. The Applied AI Architect seat at Apic India is the right shape: pre-sales depth, evals as a first-class deliverable, voice-of-customer back to Product. Apic's safety properties — Constitutional AI, the Responsible Scaling Policy — are what makes Claude the right tool for the customers I want to serve. That's why this seat, now."
Notice: this convergence preempts the lateral-move risk implicitly (by leading with what you want to do, not justifying what you're stepping away from), names two Apic-specific artifacts, and ties the seat to a customer thesis rather than personal aspiration.
60-second compression for the recruiter screen
"I've spent the last several years as the customer-embedded technical voice for enterprise AI — most recently architecting Claude-powered multi-agent platforms in healthcare under HIPAA-aligned governance, and before that building and leading a 15-person GenAI Forward Deployed Engineering practice at the GenAI services firm from zero, embedded with enterprise customers across BFSI, healthcare, and retail. What I want for the next two to three years is being the trusted technical advisor for Indian and APAC enterprise customers — especially regulated ones — adopting Claude. The Applied AI Architect seat at Apic India is the right shape, and Apic's safety properties make Claude the right tool for those customers. That's why this seat, now."
~60 seconds at a normal speaking pace. Test it.
What to watch for in your delivery
- Cadence dip on the lateral implication. When you reach "the right shape: pre-sales depth, evals as a first-class deliverable" — make sure your tone is steady, not apologetic. Pre-Sales IC is a choice in this narrative, not a confession.
- Confidence on the Apic-specific reference. "Constitutional AI, the Responsible Scaling Policy" — say these like you mean them. If you don't yet feel confident on what each one means at one level of abstraction, re-read Notes/01-Mission-Values-Constitutional-AI.md and re-rehearse.
- Don't say "BFSI" without context. In the recruiter screen, "Indian and APAC enterprise customers, especially regulated ones" is clearer than insider acronyms.
Your turn
When you're ready, write your raw 120-second TMAY answer below — or speak it into a voice memo and transcribe it. Don't polish it first; we want the raw version so I can grade what would actually come out of your mouth in the recruiter screen.
I'll grade on the rubric above, write the upgraded version, and log the result in Drill Tracker.