Got an actual specific rejection email for once instead of the copy-paste. Sharing what they said.
After maybe 30 rejections that were all 'we've decided to move forward with other candidates,' one recruiter actually wrote back with real notes: my code worked but I never explained tradeoffs, and I went quiet whenever I got stuck instead of thinking out loud.
Stung for a day. But it's the single most useful thing anyone's told me in this whole search. Now I narrate everything, even the dead ends. Save your rejection emails, and it's worth politely asking for feedback — occasionally someone's kind enough to actually give it.
2 comments
- 0
AnonymousAnon An actual specific rejection is a gift, weird as that sounds. Ninety-nine percent are copy-paste, so someone taking the time to tell you the real reason handed you something you can act on. I'd almost send a short thank-you, it's rare enough that they'll remember you next time a role opens.
- 0
AnonymousAnon The 'went quiet when stuck' one is so common. What fixed it for me was literally saying 'okay, I'm stuck — here's what I've ruled out and what I'd try next.' Turns a dead silence into a signal that you're systematic. And thanks for actually posting the notes; most people just say 'ask for feedback' and never show what useful feedback looks like.