Roadmap · Life skills
Handling rejection and setbacks
FreeFor students and early-career people who have failed an exam, been rejected for an internship or job, watched a project or startup fail, or received feedback that hurt. By the end you can get through the first days without making things worse, learn from what happened without blaming yourself, and start again with a written plan.
If you are struggling right now
This roadmap helps you build skills and habits. It is not therapy or a medical service. If you are in danger or thinking about harming yourself, contact local emergency services now, or talk to a crisis line: Find a helpline (any country), Umang (Pakistan), Tele-MANAS, 14416 (India). If low mood, worry or stress has lasted weeks and gets in the way of daily life, please see a doctor or counsellor.
By the end, you will be able to
- Explain why rejection hurts and separate what happened from what it says about your worth
- Get through the first 48 hours after a bad result with a simple plan instead of a spiral
- Recover from a failed exam or a low CGPA with a study fix and an honest way to talk about it
- Treat internship and job applications as a pipeline, find where you drop out and fix that stage
- Close a failed project or startup properly and keep the skills and story it gave you
- Take stinging feedback, find the useful part and act on it
- Write a post-mortem without self-blame and turn it into a dated plan to start again
The path
7 stages, in the order to learn them. Open one to start.
1Why rejection hurtsRejection hurts for real reasons, and the hurt is not a sign of weakness. Understand what is going on, how the story you tell yourself shapes the pain, and where the line is between a bad week and something that needs more help.6 topics · ~1 week
- 1Rejection is a real kind of painHumans survived in groups, so being pushed out of one was dangerous.
- 2The event is not your worthA rejection is a decision someone made about one application, one exam paper or one piece of work, on one day, with the information they had.
- 3The three stories that make it worsePsychologist Martin Seligman studied how people explain bad events to themselves.
- 4The CV nobody shows youEvery CV and LinkedIn profile is a highlight reel.
- 5Skills grow, so results can changeCarol Dweck's research describes two beliefs about ability.
- 6When it is more than a bad weekSadness, anger and disappointment after a setback are normal and usually ease over days or a couple of weeks.
6 in this stageOpen this stage2The first 48 hoursThe days right after a bad result are when people make the choices they regret: angry messages, quitting, deciding they are finished. Get through them with your body looked after, one or two people around you and no big decisions.7 topics · ~1 week
- 1Let yourself feel it, for a whileThe first reaction to a rejection is often shock, then sadness, anger or embarrassment.
- 2Look after your body firstStress hits the body: you sleep badly, skip meals, sit in one place scrolling.
- 3No big decisions for nowRight after a rejection, your brain is in threat mode and tends to see everything as all or nothing.
- 4Tell one or two peopleShame grows when you keep a setback secret.
- 5Pause the feedThe day you get a rejection is often the day your feed is full of other people's offer announcements, toppers and launches.
- 6Replaying it versus learning from itGoing over a setback can help or hurt.
- 7One small next stepAfter the first day or two, do one small thing that moves you forward, however minor.
7 in this stageOpen this stage3Failed exams and a low CGPAA failed paper or a low CGPA feels permanent, especially when family and classmates are watching. Find out what really happened, fix the way you study, use the options your university gives you, and learn to talk about grades honestly.7 topics · ~2 weeks
- 1Find out what actually happenedA failed exam usually has a mix of causes.
- 2Fix how you study, not only how muchAfter a failed exam, most students promise to study harder.
- 3Know your options: resits, repeats and helpMost universities have rules for what happens after a failed course: a supplementary or resit exam, repeating the course, improving the grade, or taking a…
- 4Telling your family about resultsFor many students the hardest part of a bad result is telling parents, especially when they have paid fees or told relatives about your plans.
- 5What a low CGPA does and does not closeBe honest about the real effect.
- 6Talking about your grades honestlyIf someone asks about your grades, a short, honest answer works better than excuses or hiding.
- 7When the subject might be the wrong fitSometimes repeated failure in a subject is a signal, not just bad luck.
7 in this stageOpen this stage4Internship and job rejectionsApplying for internships and jobs means hearing no far more often than yes, and often hearing nothing at all. Treat it as a numbers game with stages you can measure and improve, not a series of judgements on you.7 topics · ~2 weeks
- 1Why most applications end in noA single opening can attract hundreds of applicants, and only one person gets it.
- 2Track every applicationKeep a simple table in Notion, a spreadsheet or on paper: company, role, date applied, how you applied (portal, referral, recruiter), stage reached and outcome.
- 3Find the stage where you drop outAn application goes through stages: applied, first reply, first call or test, later rounds, offer.
- 4When they never replyBeing ghosted, hearing nothing after applying or even after a call, is common and it hurts in its own way because there is no closure.
- 5Asking why, and what to do with silenceAfter a later-stage rejection, it is fine to ask once for feedback: "Thank you for letting me know.
- 6Getting used to no on purposeJia Jiang, an entrepreneur, spent 100 days deliberately asking strangers for things he expected to be refused, and found that rejection hurt less with…
- 7Keep applying while you waitOne of the most common mistakes is stopping all applications because one company looks promising, then starting from zero when it says no.
7 in this stageOpen this stage5Failed projects and startupsA final year project that collapsed, a side project nobody used, a startup that ran out of money. Decide whether to stop or change course, close it properly with the people involved, and keep everything it taught you.6 topics · ~1 week
- 1Why projects usually failStudent and side projects most often fail for ordinary reasons: the scope was too big, the team split the work badly, nobody owned the deadline, or the hard…
- 2Stop, change course or keep goingWhen a project is going badly, you have three choices: stop, change course, or keep going.
- 3Closing it properlyHow you end a project matters as much as how you start it.
- 4Money, debt and family after a failed ventureSome setbacks come with real money problems: savings spent on a startup, a family loan, unpaid salaries.
- 5What a failed project gives youA failed project still leaves you with real things: skills you learned, code you can reuse or show, people you worked with, and the judgement that only comes…
- 6Telling the story on your CV and in personA failed startup or project can be a strong part of your story if you tell it honestly.
6 in this stageOpen this stage6Feedback that stingsA harsh code review, a teacher's red pen, a manager's comment in a meeting. Learn why feedback stings, how to separate the message from the delivery, and how to find and act on the useful part.6 topics · ~1 week
- 1Why feedback stingsIn their book on receiving feedback, Douglas Stone and Sheila Heen describe three triggers that make people reject it.
- 2Understand it before you judge itFeedback often arrives as a vague label: "your presentation was weak", "this code is messy", "you need more ownership".
- 3Find the useful partEven unfair or badly delivered feedback usually contains something useful.
- 4Harsh code review commentsCode review is where many engineers first meet blunt written feedback.
- 5When feedback is unfair or unkindNot all feedback is fair.
- 6Ask for feedback before it is forced on youFeedback stings most when it comes as a surprise at the end: a grade, a performance review, a rejection.
6 in this stageOpen this stage7Resilience, a post-mortem and starting againBring it together. Handle comparison, build habits that make setbacks easier to absorb, write a post-mortem without blaming yourself, and turn it into a dated plan to try again.6 topics · ~2 weeks
- 1Comparison after a setbackLeon Festinger's social comparison theory describes how people judge themselves against others, and after a setback almost everyone compares upwards: the…
- 2Self-compassion, not self-pityKristin Neff's research describes self-compassion as three things: treating yourself with the kindness you would show a friend, remembering that failure is…
- 3Habits that make setbacks easier to carryResilience is less a personality trait and more a set of things you keep doing in ordinary weeks, so that a bad week does not knock you over.
- 4Write a post-mortem without blameGood software teams write a blameless post-mortem after an outage: what happened, when, why, and what will change, without hunting for someone to punish.
- 5Turn it into a plan with datesA post-mortem only matters if it changes what you do next.
- 6Trying again, and knowing when not toStarting again does not always mean trying the same thing.
6 in this stageOpen this stage
Related on Sefism
Picked from the other libraries by shared topics.
Checklists
See allCareer questions
See all- I just got my first developer job and feel like a fraud. How do I overcome imposter syndrome?Feeling like a fraud in your first developer job is normal and usually a sign you have moved into a room where learning is expected. Separate feelings from evidence, keep a record of what you ship, ask better questions early, and give yourself a realistic ramp-up of three to six months before judging yourself.
- How do I deal with rejection after applying to so many software jobs?Rejection in a tech job search is mostly a numbers and fit problem, not a verdict on your worth. Track your pipeline so you can see where it leaks, limit how much each rejection costs you emotionally, fix one stage at a time, and protect a daily routine that does not depend on replies.
- Why do I feel stupid when I start working with engineers who are much better than me?Because you are comparing your inside, full of confusion, with their outside, which only shows the finished answer. Feeling slow next to stronger engineers is what learning quickly feels like. Treat the gap as information, not a verdict, and use it: watch how they think, ask better questions, and measure yourself against last month rather than against them.
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.
- 1:1 Mentorship
- Fresh Graduate Mentorship
- Career Guidance
Brand deals, promos and partnerships: tauseeffayyaz@gmail.com