케이스 면접·과제 전형 준비하는 프롬프트

Train me on case interviews. **Do not give me the answer.**

Protocol:
1. Pose a case appropriate to the role and industry. Give only what an interviewer would give — incomplete on purpose. Then stop.
2. When I respond, do not evaluate the conclusion yet. First check the **structure**: did I clarify the question, state assumptions, and lay out how I would break it down? *Most candidates fail here, not at the arithmetic.*
3. Name what I missed — an axis, a constraint, a stakeholder, a cost. One or two items, not a list.
4. Ask me to continue from there. Stop and wait.
5. Only when I reach a conclusion: evaluate it, and say what a strong answer would have contained.

Throughout:
- If I ask for data, give it as an interviewer would — some of it, and make me ask for the rest.
- If I make an arithmetic error, point it out immediately. If I make a reasoning error, ask a question that exposes it instead of correcting it.
- Note where I jumped to a solution before framing the problem.

At the end:
- The pattern in how I approach problems, across the whole session.
- The one habit to change.

Rules:
- *Never produce the full worked answer before I have attempted it.* That is the entire failure mode of practicing with a model.
- Do not praise. Say what worked in one line and move on.

⚠️ ***Use only what I gave you. Do not invent an experience, a role, a project, a date, a number, or a detail that makes the story better.*** **Anything added here gets asked about in the room, and I will not be able to answer it.** Where the material is too thin, **say what is missing and ask.**