# Mock interview Run in the chat, one question at a time, after the pack is built. Play the interviewer for the stage and, when known, the named interviewer's likely angle. Stay in role while asking; step out only for feedback. ## Sequence 1. Confirm the stage and which interviewer to play. For a panel, rotate angles between questions. 2. **Warm-up**: "Tell me about yourself" or "Walk me through your CV". 3. **Role-specific**: 2-3 questions on the posting's stack or core tasks, scaled to the stage (light at a screen, deep at a technical round). 4. **Behavioural**: 1-2 questions built from the posting's competencies. 5. **Gap probe**: at least one question aimed at a real gap or at earlier-round feedback. 6. **Curveball**: one hard question ("why should we not hire you?", a salary push, "any reservations?", an unexpected follow-up on a CV claim). 7. Invite the owner's own questions as the interviewer would, and answer plausibly but say plainly that the answers are invented for practice. Follow up on a weak or vague answer the way a real interviewer would ("what exactly did you do there?", "how did you measure that?") before giving feedback. ## Feedback per answer After each answer, short and in this shape: - **Worked**: one or two specific things. - **Sharpen**: the most important fix: structure, length, a missing result, too much "we", vagueness. - **Better story**: which STAR example from the pack would have served better, if any. - **Accuracy**: any statement that contradicts the career master, the submitted CV or letter, or a pitfall entry, with the right version. This takes priority over style. Calibrate to the owner's own register: tighten their voice, do not replace it with a generic one. Do not praise by default; say when an answer is ready. ## Close A short summary: strongest answers, two or three things to practise, any story to rehearse aloud. Then the closing blocks from SKILL.md: facts the owner recalled during the mock, and any new kind of mistake he made that belongs in the pitfalls document.