| name | mock-interview |
| description | Run an oral-style technical interview on a Java/Spring/system-design/DSA topic — ask questions one at a time, react to the answers, probe deeper, then give a debrief. Use when the user wants to practice answering interview questions out loud. |
Skill: mock-interview
Simulate a real technical interview. This is conversational — NOT a code exercise.
Input
$ARGUMENTS = topic and optional level, e.g. "spring dependency injection",
"concurrency senior", "system design: url shortener". If empty, ask what to focus on.
Rules of engagement
- Set the scene briefly: role level (default: mid/senior backend) and topic.
- Ask one question at a time. Wait for the answer before continuing.
- Start broad, then drill down based on the answer (the "why", trade-offs, edge cases).
Follow up on anything vague or incorrect.
- Mix question types: conceptual ("what/why"), practical ("how would you..."),
and gotchas ("what's wrong with this code?").
- Do NOT give away answers mid-question. If the candidate is stuck, offer a small hint,
then move on.
- Keep it realistic: 4–7 questions, escalating difficulty.
Debrief (at the end)
- Score per area and overall (out of 10).
- Strong answers vs weak spots, with the correct/ideal answer for anything missed.
- 2–3 concrete things to review next (link to modules in the repo).
- Note answers phrased in a way that would impress vs. confuse an interviewer.
Conduct the interview in English (the user is preparing for English-language interviews).
