Orchestrates end-to-end interview preparation for senior ML/AI engineers targeting Anthropic and peer companies. Use for prep timeline generation, story coherence across rounds, mock scheduling, and debrief analysis. Activate on "interview prep", "interview loop", "Anthropic interview", "prep timeline". NOT for resume writing, career narratives, or individual round-type practice.
npx skills add https://github.com/curiositech/some_claude_skills --skill interview-loop-strategist
End-to-end orchestrator for senior-level AI/ML interview preparation. Coordinates timelines, story coherence across rounds, mock interview cadence, energy management, and post-interview debrief -- routing each round type to its specialist skill.
Use for:
NOT for:
cv-creator)career-biographer)flowchart TD
A[Career Biographer] -->|Extracts narrative| B[CV Creator]
B -->|Resume finalized| C[Interview Loop Strategist]
C --> D{Company Target Selected}
D --> E[Generate Prep Timeline]
E --> F[Story Coherence Matrix]
F --> G[Round-Specific Prep]
G --> G1[Recruiter Screen<br/>Self-prep]
G --> G2[CodeSignal / Coding<br/>senior-coding-interview]
G --> G3[Hiring Manager Screen<br/>hiring-manager-deep-dive]
G --> G4[ML System Design<br/>ml-system-design-interview]
G --> G5[Technical Deep Dive<br/>anthropic-technical-deep-dive]
G --> G6[Tech Presentation<br/>tech-presentation-interview]
G --> G7[Values & Behavioral<br/>values-behavioral-interview]
G1 --> H[Mock Interviews<br/>interview-simulator]
G2 --> H
G3 --> H
G4 --> H
G5 --> H
G6 --> H
G7 --> H
H --> I[Debrief & Adjust]
I -->|Iterate| G
I --> J[Interview Day<br/>Energy Protocol]
J --> K[Post-Loop Debrief]
K --> L{Offer?}
L -->|Yes| M[Negotiation Phase]
L -->|No| N[Gap Analysis & Retry]
N -->|Update plan| E
Each round type maps to a specialist skill. The strategist coordinates -- it does not execute round-specific practice.
| Round Type | Specialist Skill | Key Focus |
|------------|-----------------|-----------|
| Recruiter Screen | Self-prep (no skill needed) | Pitch, motivation, logistics, salary range |
| Online Assessment / Coding | senior-coding-interview | LC hard, system design lite, time management |
| Hiring Manager Screen | hiring-manager-deep-dive | Leadership, team fit, technical judgment |
| ML System Design | ml-system-design-interview | End-to-end ML pipelines, tradeoffs, scale |
| Technical Deep Dive | anthropic-technical-deep-dive | Past work forensics, technical depth, AI safety |
| Tech Presentation | tech-presentation-interview | 45-min talk, audience calibration, Q&A |
| Values / Behavioral | values-behavioral-interview | STAR stories, Anthropic values alignment |
| Mock Execution | interview-simulator | Realistic timed practice with scoring |
Choose based on time until first round:
flowchart LR
T{Time Available?}
T -->|< 2 weeks| P1[Intensive Plan<br/>4-6 hrs/day]
T -->|2-5 weeks| P2[Balanced Plan<br/>2-3 hrs/day]
T -->|6+ weeks| P3[Thorough Plan<br/>1-2 hrs/day]
P1 --> R[See references/<br/>preparation-timeline-templates.md]
P2 --> R
P3 --> R
For detailed daily schedules, consult references/preparation-timeline-templates.md.
A senior candidate has 5-8 strong projects. Each project will surface in multiple rounds but must be tailored to the audience and evaluation criteria of that round.
| Version | Round Type | Emphasis | Length |
|---------|-----------|----------|--------|
| Technical | ML Design, Deep Dive | Architecture decisions, tradeoffs, metrics, what you would change | 8-12 min |
| Impact | Behavioral, HM | Leadership, influence, collaboration, business outcome | 3-5 min (STAR) |
| Narrative | Presentation, Recruiter | Story arc, why it matters to the world, lessons learned | Variable |
Project: Real-Time Object Detection Pipeline (2019-2022)
| Round | Version | Key Points |
|-------|---------|------------|
| ML Design | Technical | YOLOv5 -> custom architecture, 40ms latency constraint, edge deployment, model distillation tradeoffs |
| Deep Dive | Technical | Why ResNet backbone over EfficientNet, quantization strategy, failure mode analysis, production monitoring |
| Behavioral | Impact | Led 4-person team through 3 pivots, managed stakeholder expectations when accuracy targets slipped, mentored junior engineer who became tech lead |
| HM Screen | Impact | Drove 35% revenue increase through automation, navigated org politics to get GPU budget, built cross-functional relationships |
| Presentation | Narrative | "From research prototype to production system serving 10M requests/day -- lessons in making ML real" |
All-day interview loops (4-6 hours) are endurance events. Cognitive fatigue causes more failures than knowledge gaps.
| Break Length | Activity | Avoid |
|-------------|----------|-------|
| 5 min | Stand, stretch, water, deep breaths | Phone, social media, reviewing notes |
| 15 min | Walk, snack (protein > sugar), bathroom | Replaying the previous round |
| 30+ min (lunch) | Eat a real meal, step outside, reset | Studying for next round |
If you can influence round order (sometimes companies ask preference):
Run after every mock AND every real interview round.
| Dimension | Score (1-5) | Evidence | Action Item |
|-----------|-------------|----------|-------------|
| Technical accuracy | | | |
| Communication clarity | | | |
| Time management | | | |
| Story coherence | | | |
| Energy / confidence | | | |
| Question handling | | | |
For scoring rubrics per round type, consult references/mock-interview-rubrics.md.
Novice: Spends equal time on every round type -- 2 hours coding, 2 hours design, 2 hours behavioral, repeat.
Expert: Analyzes personal weaknesses and round weighting. A candidate who aces design but freezes in coding allocates 60% of prep to coding. A candidate whose stories are inconsistent spends dedicated time on the coherence matrix.
Detection: Prep log shows identical hours across all categories despite known weaknesses.
Novice: Prepares each round independently. Tells a behavioral story about leading a team of 6 in one round, then says "I was the sole contributor" for the same project in a technical round.
Expert: Uses the story coherence matrix to thread a consistent narrative across all rounds. Reviews the matrix before every mock. Has a peer check for contradictions.
Detection: Same project described with conflicting details (team size, timeline, your role, metrics) across different round types.
Novice: Reads interview guides, watches YouTube videos, reviews flashcards -- but never actually practices speaking answers aloud under time pressure.
Expert: Runs at minimum 2 full mock interviews per week in the final month. Records mocks. Reviews recordings. Uses interview-simulator for structured scoring. Treats mocks as the primary prep activity, not supplementary.
Detection: Zero mock session recordings in history. Unable to answer questions within time limits despite "knowing the material."
Anthropic's interview process (as of early 2026) emphasizes:
For detailed company-specific loop structures (Anthropic, Google DeepMind, OpenAI, Meta FAIR), consult references/company-specific-loops.md.
| File | Consult When |
|------|-------------|
| references/preparation-timeline-templates.md | Generating a daily prep schedule for 2-week, 1-month, or 2-month timeline |
| references/mock-interview-rubrics.md | Scoring mock interviews, self-evaluation, or identifying failure modes per round type |
| references/company-specific-loops.md | Tailoring prep to a specific company's interview structure (Anthropic, DeepMind, OpenAI, Meta FAIR) |
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Curated collection of high-quality prompts for various use cases. Includes role-based prompts, task-specific templates, and prompt refinement techniques. Use when user needs prompt templates, role-play prompts, or ready-to-use prompt examples for coding, writing, analysis, or creative tasks.
Convert abstract edge concepts into strategy draft variants and optional exportable ticket YAMLs for edge-candidate-agent export/validation.
INVOKE THIS SKILL when writing ANY LangGraph code. Covers StateGraph, state schemas, nodes, edges, Command, Send, invoke, streaming, and error handling.
Analyze the protocol layer between agent harness and LLM model. Use when (1) understanding message wire formats and API contracts, (2) examining tool call encoding/decoding mechanisms, (3) evaluating streaming protocols and partial response handling, (4) identifying agentic chat primitives (system prompts, scratchpads, interrupts), (5) comparing multi-provider abstraction strategies, or (6) understanding how frameworks translate between native LLM APIs and internal representations.
Translate SKILL.md and README.md files into multiple languages for sharing skills internationally
| Shared workflow for editing Langfuse's repo-owned agent setup under `.agents/`. Use when changing AGENTS files, shared skills, `.agents/config.json`, generated shim behavior, provider discovery paths, or install-time agent sync.
>- Summarizes Google Cloud Data Lineage graphs to help users debug data quality issues and understand data provenance for BQ/GCS. Use when summarizing upstream and downstream data flows, and presenting complex lineage data as an intuitive Markdown report. Don't use for generic BigQuery queries, editing lineage relationships, or downstream deprecation. Don't use for downstream blast-radius impact analysis (use datalineage-bigquery-asset-impact-analysis skill instead).
Take curiositech/interview-loop-strategist from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.