SELF 129 words
Reframe a rejected job application as useful information, not a verdict
The email said no, and now your brain has quietly decided that means no to everything, forever. This pulls the rejection apart: what it can actually tell you about this one application, and what it has no business telling you about anything else. You get one honest thing to maybe adjust, and permission to stop carrying the rest. For the evening after the email lands.
You applied for a role, got turned down, and now the rejection is sitting in your head as proof of something bigger than one hiring decision. Describe {REJECTION_CONTEXT}, meaning the role, what stage you got to, and any feedback given or not given, then work through the situation without minimising it or pretending it did not sting. Separate what this rejection can actually tell you (something about this application, this role, this panel, at this moment) from what it cannot tell you (your overall worth, your entire career trajectory, every future application). Name one thing, if anything, worth adjusting for next time, and one thing that was outside your control regardless of what you did. End with a short, plain statement of where things actually stand, not false positivity. ⚠ human-in-the-loop: you are responsible for the results of using this prompt, not us.