Every career site tells you the same thing about rejection: “don’t take it personally,” “it’s about fit, not worth,” “use it as motivation.” What none of them tell you is what rejection actually sounds like in the room — the specific words, the specific moments, the difference between a rejection that teaches you something and one that just stings. That gap between generic advice and lived experience is exactly what most people are left navigating alone, without ever hearing what it’s really like from someone who’s been through it.
I’ve had both kinds. Here’s what they actually sounded like.
Why Generic Rejection Advice Falls Short
Most career advice about handling rejection is written from a distance — a coach or writer describing rejection in the abstract, offering coping frameworks without ever describing an actual conversation. That distance is exactly the problem. When you’re sitting across from an HR representative and hearing “no” for the first time, generic advice about mindset doesn’t prepare you for the specific, sometimes disorienting way it actually plays out. What helps more, I think, is hearing what real rejection conversations actually sound like, so you recognize the pattern when you’re living through it yourself.
The One That Hurt Most: Supricav Security
This rejection didn’t come after a two-minute conversation. It came after a full interview, which made it hurt more than a quick, impersonal no ever could.
The HR sat me down and asked my age — I answered him in Creole, since I’d picked up enough for basic exchanges by then. Then he asked how long I’d been in the country. That question, I couldn’t answer in Creole. I didn’t have the vocabulary for it yet, and the gap in my language ability became obvious in that exact moment, in front of him.
So he asked which other languages I spoke. I told him English. He mentioned French, and pointed out that a lot of foreigners in Cape Verde speak French — the implication being that if I’d spoken French, they might have worked something out despite the Creole gap. That comment has stayed with me, because it wasn’t dismissive. It felt like he was genuinely trying to find a way to make it work, and simply couldn’t.
Here’s what made this rejection different from the others, and part of why it hit harder: I’d already filled out the full details form before the interview even started. The receptionist had already gone to bring my uniform. Everything about the process signaled I was moving forward, step by step, toward an actual job. Then, after all of that, I was rejected.
I was not happy. Not because the rejection itself was unfair — Creole genuinely mattered for the role, and I understand that now more than I did then — but because of how far the process went before it happened. Being measured for a uniform and then told no is a specific, unusual kind of disappointment that “don’t take it personally” doesn’t really prepare you for. It’s one thing to be rejected on paper. It’s another to feel the physical motions of being hired, only to have that reversed in the same sitting.
The One That Actually Helped: Sonasa, After I Got the Job
Rejection isn’t the only feedback moment that sticks with you. Getting affirmed for the right reasons matters just as much, and it taught me something rejection never could — that the small, unofficial moments often carry more honest signal than anything formal.
After I took over my friend’s position at Sonasa, I made a point of putting more energy into the work than I probably needed to — partly gratitude toward my friend for making the opportunity possible, partly wanting to prove to myself that the switch had been the right decision.
Within the first week, one of the bank’s cleaning staff told me that a bank employee had mentioned I seemed cheerful and caring. That comment wasn’t part of any scheduled review. Nobody was grading me in that moment. It was just someone noticing how I showed up, day to day, and passing it along informally.
That single secondhand comment meant more to me than most formal feedback I’ve received before or since. A month later, I was given my contract — and I’ve always connected that early feedback to how deliberately I approached those first weeks on the job.
What These Two Moments Taught Me About Feedback
Formal, official feedback — the kind career coaches tell you to request in a polite follow-up email — is useful, and I’m not dismissing it. But it’s not the only feedback that shapes your job search or your early days in a new role. Some of the most honest signals come from moments nobody labels as “feedback” at all: a receptionist bringing your uniform before the rejection call comes, or a cleaner passing along a compliment that wasn’t even originally meant for your ears.
If you’re navigating rejections or settling into new roles yourself, a few things worth holding onto from my own experience:
- A process moving forward isn’t a guarantee. Uniform fittings, forms, even verbal encouragement during an interview can all still end in “no.” It’s disappointing, but it’s not a reflection of your overall worth — it’s usually a reflection of one specific, often narrow requirement, like language, that simply didn’t line up on that occasion.
- Language gaps will show up in real time, not just on paper. Being asked a question you can’t answer, live, in an interview, is a very different experience than failing a language requirement listed abstractly in a job posting beforehand. Prepare mentally for that specific moment, not just the general expectation that language might matter somewhere.
- The best feedback sometimes isn’t feedback at all. Notice how people treat you day to day, not just what’s said in formal reviews or interviews. It often tells you more, honestly, about how you’re actually doing than any official conversation will.
- Some rejections come with genuine care, even when they still hurt. The Supricav HR’s comment about French wasn’t cruel — it read as someone trying to find a path forward and coming up short. Recognizing that distinction helped me process the rejection without carrying resentment toward the person delivering it.
Frequently Asked Questions
How do you tell the difference between a rejection worth learning from and one that’s just discouraging? For me, it came down to specificity. The Supricav rejection told me exactly why — language — which gave me something concrete to work on. A vague rejection, without a clear reason, is harder to learn from and easier to just feel discouraged by.
Should you ask an interviewer directly why you were rejected? In my experience, sometimes you don’t even need to ask — it’s stated plainly, as it was with the language issue at Supricav. If it isn’t offered, asking respectfully rarely hurts, and it may give you something useful to act on.
Does informal feedback, like a comment passed along by a coworker, actually matter? Yes, more than I expected. The comment relayed to me by the bank’s cleaner ended up meaning more than most formal reviews I’ve had, because it was unprompted and genuine.
Is it normal to feel worse after a rejection that went further in the process, compared to a quick one? In my experience, yes. The Supricav rejection, which came after a full interview and uniform fitting, affected me more than quicker, earlier rejections did. It’s a reasonable reaction, not an overreaction, and it’s worth naming rather than suppressing.
Why This Matters Beyond My Own Story
If you’re currently in the middle of a job search, especially in a smaller market where language or local knowledge plays a real role, know that a rejection which goes further into the process — like mine at Supricav — isn’t necessarily a worse sign about you as a candidate. Sometimes it just means you were genuinely close, and one specific, fixable gap got in the way. For more on turning setbacks like this into your next move, our job search strategies guide covers how to keep momentum after a string of no’s.
What I’d Tell Someone Facing Their Own Hard Rejection
If you’re reading this after your own version of the Supricav interview — the one that went far enough to feel real before it ended in no — I want to say plainly: that specific kind of disappointment is valid, and it’s different from a quick, impersonal rejection. Give yourself permission to feel it fully rather than rushing straight to “don’t take it personally.” Then, once you’ve sat with it, look for the specific, fixable reason behind it, the way I eventually did with Creole. A rejection with a clear cause is, in an odd way, more useful than one that leaves you guessing.
Have you had a rejection or a piece of offhand feedback that taught you more than any formal review ever did? I’d love to hear it.
