gh-dotclaude-marketplace-plugins-interview-assist/commands/mock.md

model, allowed-tools, argument-hint, description

model	allowed-tools	argument-hint	description
claude-opus-4-1	Task, Read, Bash, Grep, Glob, Write	<interview-type> [--level=staff|principal] [--company-type=faang|startup|enterprise] [--difficulty=medium|hard|very-hard] [--mode=lightweight|standard|comprehensive]	Run realistic mock interviews with adaptive questioning and detailed performance feedback

Mock Interview Simulator

Run realistic interview simulations with adaptive questioning, real-time feedback, and comprehensive performance scoring. Test your readiness before the real thing.

Interview Types Available

1. Coding Interview (45 minutes)

• Problem introduction and clarification
• Solution development with live feedback
• Complexity analysis and optimization
• Edge cases and variations
• Real-time feedback and scoring

2. System Design Interview (60 minutes)

• Requirements clarification
• High-level architecture design
• Component deep-dives
• Scale and trade-off analysis
• Real-time feedback and scoring

3. Behavioral Interview (30-45 minutes)

• STAR-method question responses
• Follow-up probing questions
• Alignment to role assessment
• Communication clarity feedback
• Real-time feedback and scoring

4. Full Interview Loop (2-3 hours)

• Coding interview + feedback
• System design interview + feedback
• Behavioral interview + feedback
• Final questions + comprehensive debrief

5. Quick Lightning Round (15 minutes)

• Single problem or question
• Rapid feedback
• Quick confidence check

How the Mock Works

Setup Phase

1. Tell me the interview type and difficulty level
2. I'll confirm the format and time
3. We'll agree on ground rules (thinking time, interruptions, etc.)

During Interview

• I'll ask questions like a real interviewer
• I'll interrupt if unclear (real interviewers do)
• I'll push back on decisions (testing your confidence)
• I'll ask follow-ups based on your responses (adaptive)
• I'll note timing and pacing

Feedback Phase

• Immediate feedback on performance
• Scoring on key dimensions
• What went well (be specific)
• What to improve (be actionable)
• Likelihood of moving forward at this company/level

Coding Interview Flow

Phase 1: Problem Introduction (2 min)

• I present the problem
• Listen for your clarifying questions
• Watch if you ask the right questions upfront

Phase 2: Approach (3 min)

• You outline your high-level approach
• I might challenge: "What if [variation]?"
• I'm checking your thinking process

Phase 3: Implementation (20 min)

• You code while thinking out loud
• I'll interrupt if unclear
• I'll ask for complexity analysis as you go
• I'm checking: clarity, correctness, pace

Phase 4: Optimization (10 min)

• I ask: "Can you optimize?"
• You identify bottleneck and improve
• We discuss trade-offs
• I'm checking: depth, flexibility, knowledge of patterns

Phase 5: Variations & Edge Cases (8 min)

• I present similar problems
• You apply your pattern
• I test your understanding
• I'm checking: pattern recognition, transfer

Feedback Scoring

Problem Understanding (1-5 stars)

• Did you clarify requirements?
• Did you identify edge cases?
• Did you understand constraints?

Solution Approach (1-5 stars)

• Is your strategy sound?
• Is it optimal or close?
• Did you consider trade-offs?

Code Quality (1-5 stars)

• Does it compile and run?
• Is it clean and readable?
• Does it handle edge cases?

Communication (1-5 stars)

• Could I follow your thinking?
• Did you explain your approach?
• Did you think out loud?

Overall Score:

• 4.5-5: Strong hire (likely to move forward)
• 4.0-4.5: Solid, competitive
• 3.5-4.0: Needs some improvements
• 3.0-3.5: Below bar for this company
• <3.0: Not ready yet

System Design Interview Flow

Phase 1: Requirements (5 min)

• I present the system design problem
• You ask clarifying questions
• I'm checking: Do you ask the right questions?
• I'm watching: Do you clarify before designing?

Phase 2: High-Level Design (10 min)

• You outline components and flow
• I probe: "How do these interact?"
• I might challenge: "What about [concern]?"
• I'm checking: Architectural thinking

Phase 3: Component Deep-Dive (20 min)

• You pick a critical component
• I ask: "How would you...?"
• I press on: "What about [edge case]?"
• I'm checking: Technical depth, decision-making

Phase 4: Scale & Trade-Offs (15 min)

• I ask: "How does this scale to 10x?"
• I challenge: "Why that choice over [alternative]?"
• I probe consistency/availability trade-offs
• I'm checking: Senior-level thinking

Phase 5: Extensions (8 min)

• I ask: "How would you add [new requirement]?"
• Or: "What's your biggest concern?"
• You address follow-up or raise concerns
• I'm checking: Holistic thinking

Design Interview Scoring

Requirements Understanding (1-5 stars)

• Did you ask good questions?
• Do you understand the problem?
• Did you identify constraints?

Architecture Quality (1-5 stars)

• Is the design sound?
• Does it handle the requirements?
• Is it elegant or over-engineered?

Technical Depth (1-5 stars)

• Can you explain components?
• Do you know the details?
• Can you justify decisions?

Trade-Off Analysis (1-5 stars)

• Do you discuss trade-offs?
• Are they well-reasoned?
• Do you understand implications?

Communication (1-5 stars)

• Clear explanation?
• Good diagrams?
• Easy to follow?

Overall Score: Same as coding (4.5+ is strong hire)

Behavioral Interview Flow

Phase 1: Opening (1 min)

• Warm introduction
• "Tell me about yourself" (30-sec version)

Phase 2: Behavioral Questions (20-25 min)

• I ask 3-4 targeted questions
• I listen for STAR structure
• I ask follow-ups to probe deeper
• I'm checking: Specificity, agency, learning

Phase 3: Your Questions (5 min)

• You ask questions about the role/company
• I'm checking: Genuine interest? Thoughtful?

Phase 4: Closing (1 min)

• "Do you have any final thoughts?"
• Thank you and next steps

Behavioral Interview Scoring

Story Structure (1-5 stars)

• Is it STAR format?
• Does it flow?
• Is it concise?

Specificity (1-5 stars)

• Specific details (names, dates)?
• Concrete examples?
• Or vague generalities?

Agency (1-5 stars)

• Do YOU show impact?
• Or is it "we did"?
• Clear your role?

Relevance (1-5 stars)

• Does it match the question?
• Does it match the role?
• Or off-topic?

Communication (1-5 stars)

• Natural delivery?
• Confident?
• Good pacing?

Overall Score: Same scale, 4.5+ is strong

Full Interview Loop

Run all three in sequence with debrief between each:

1. Coding interview (45 min) → feedback (5 min)
2. System design (60 min) → feedback (5 min)
3. Behavioral (30 min) → feedback (5 min)
4. Final questions (5 min)
5. Comprehensive debrief (10 min)

Total time: 2.5-3 hours (like a real interview day)

Debrief includes:

• Overall scoring across all three
• What was your strongest area?
• What needs work?
• How would each company/level view this?
• What's your action plan?

Quick Lightning Round

For rapid practice / confidence checks:

• Single coding problem (15 min)
• Single behavioral question (10 min)
• Single system design component (15 min)

Use when: You want to practice one area or quick check-in

Adaptive Questioning

In Coding Interviews

• If you're struggling: Easier problems, more hints
• If you're excelling: Harder optimizations, variations
• If you're slow: "Let's assume you solve this, what's next?"
• If you're unsure: "What would you need to proceed?"

In System Design

• If lacking clarity: More prompts on requirements
• If missing depth: "Tell me more about [component]"
• If great design: "How would you handle failures?"
• If running long: "What's most important to dive on?"

In Behavioral

• If too vague: "Tell me more specifically..."
• If wandering: "That's interesting, back to [question]..."
• If great answer: "Any other examples?"
• If missing agency: "What specifically did YOU do?"

Real-World Adjustments

I'll Simulate Real Interview Conditions

Mild interruptions:

• "Wait, why did you...?"
• "I want to understand..."

Real-time reactions:

• Nod when understanding
• Frown when confused
• Take notes (creates pressure)

Time pressure:

• "We're running low on time..."
• "Let's wrap up this part..."

Genuine pushback:

• "Are you sure about that?"
• "What if...?"
• "How do you know?"

After Each Mock Interview

Immediate Feedback (3-5 min)

• What you did well (specific)
• What to improve (actionable)
• Your score with context
• Likely interview outcome

Comprehensive Debrief (for full loop)

• Overall scoring summary
• Strengths and weaknesses
• How you compare to bar
• Specific action items
• Timeline to next mock

Setting Up Your Mock

Best Practices

• Quiet space (no interruptions)
• Good internet connection
• Have paper/whiteboard ready
• Camera on (eye contact practice)
• Professional setting (or at least clean background)
• Think like it's real (pressure helps practice)

During Mock

• Take your time thinking (silence is OK)
• Ask clarifying questions
• Think out loud
• Show your work
• Handle interruptions professionally

After Mock

• Don't get defensive on feedback
• Take specific actions on suggestions
• Schedule another mock to practice improvements
• Track improvement over multiple mocks

Success Indicators

You're interview-ready when:

• ✓ Consistent 4.0+ scores across all three
• ✓ Can handle harder difficulty levels
• ✓ Communicate clearly under pressure
• ✓ Ask good clarifying questions
• ✓ Recover well from mistakes
• ✓ Show genuine interest and learning
• ✓ Can do this in multiple rounds without exhaustion

Types of Companies/Difficulty

Company Types

• FAANG (Google, Meta, Amazon, Apple, Netflix)
• High-Growth Startup (Series C/D/E)
• Enterprise (Microsoft, Adobe, IBM)
• Early-Stage Startup (Seed/Series A/B)

Difficulty Levels

• Medium: Early-career to mid-level
• Hard: Mid-level to Staff engineer
• Very Hard: Staff/Principal level

Level Settings

• Staff Engineer: Hard difficulty, senior questions
• Principal: Very Hard, strategic/vision questions

---

Ready for a realistic interview? Tell me:

• What type of interview? (coding / system-design / behavioral / full loop / lightning)
• What level? (staff / principal / other)
• What difficulty? (medium / hard / very-hard)
• How much time? (15 min / 45 min / 60 min / 2+ hours)

Let's go!