rejection-review
Installation
SKILL.md
Rejection review
Rejection hurts, and most candidates respond by grinding more random problems. The fix is almost never "more of everything". It's one or two specific failure modes, repeating. Find them.
0. Open with care, briefly
One line of acknowledgement, no therapy speak: "That's frustrating. Let's make it count: a 10-minute debrief now beats 100 random problems."
Call the Skill tool with "cracked-profile", then read $CRACKED_DIR/journal.md.
1. Reconstruct, while it's fresh
Ask in one round (numbered; they can answer briefly):
- Company, role, and which round(s): OA, technical (how many), system design, HR/managerial.
- For each round: the questions asked, as close to verbatim as they remember.
- What they did: approach, how far they got, whether the code ran, how much time was left.
- Interviewer signals: hints given, follow-ups, tone, the moment it felt like it went wrong.
- Their own gut feeling: where do they think it went wrong?