Nahda is nineteen, in Year 2 of Kalvium’s B.Tech CSE programme, and in the middle of her first placement cycle.
Five companies have already said no.
The first email she opened sounded polite enough. “Unfortunately, the company has moved forward with other hires. But make sure you have the enthusiasm and zeal in you and keep going forward.” She’d read enough of these now to know it almost word-for-word. Four more arrived in close succession.
It’s a number most engineering students don’t ever say out loud. Five rejections is the kind of thing you bury inside a resume revision or a quiet Sunday. Nahda did neither. She did something more interesting.
The one she’d actually prepared for
One of the rejections sat heavier than the others.
There was a company she genuinely wanted to work with. The role looked right. The culture, from everything she could tell, fit. She knew the role needed a programming language she hadn’t yet used in production. So she sat down and started learning it. She asked a friend who’d used it. She watched tutorials. She built small things in it. She got ready.
When the company said the first-round link would go out to shortlisted candidates, she was watching for the email.
The link went to one student in her class. Nahda wasn’t that student.
She didn’t get the rejection email a company sends when you’ve attempted a round. She didn’t get to attempt the round at all.
A lot of stories about resilience would smooth that part over. “It hurt, but she bounced back.” That’s not what she says now, looking back at it. What she says is: “I think I was being a bit greedy. I should be a little down to earth and work harder.”
The mindset that quietly changes everything
Read that sentence again, because the entire shift in how Nahda approaches her career is contained in it.
She didn’t say the company was unfair. She didn’t say the system was rigged. She didn’t say she got unlucky.
She said: I was overconfident. The thing I was telling myself was “I’ll apply, I’ll get it, pakka for sure.” That sentence was the problem, not the rejection.
When her academic mentor asks her now what she’s doing differently for the next cycle, she lists actual things. Her resume needs better project framing. Her preparation needs more depth, not more breadth. She’s getting more honest with herself about what she actually knows versus what she’s been performing. She’s stopped assuming things will work out and started working to make them work out.
That sentence is twelve words long and it took five rejections to earn.
What nineteen looks like, from up close
Watch how Nahda talks about whether she considers herself a failure, and you’ll understand why the people who mentor her see something other people don’t.
She doesn’t think she is one. She points out, unprompted, that people at twenty-five are still facing rejections in their careers. She knows this is part of the work, not a verdict on her potential.
She is also not blaming the companies. Not blaming the screening process. Not blaming bad luck. She is taking ownership of what she can control, which is her effort, her preparation, and her approach.
Ownership at nineteen looks unusual because it is unusual. Most engineering graduates pick up this disposition somewhere in their late twenties, after a few jobs have explained it to them the hard way. Nahda is picking it up in Year 2.
What October looks like for her
She’s already preparing for the October cycle. Two more companies have visited campus. She has applied to both.
What’s different this time isn’t the applications. It’s the preparation under them.
Less assumption. More specificity about what each company actually wants. Resume rewritten with the kind of project framing that survives a thirty-second skim. A clearer story about what she’s built and what she’s still learning. A more honest read on which roles match her current depth and which she needs another six months for.
When she does land an internship, and the mentors who work with her are quietly certain she will, the first call will go to her family. There’s a long-running joke about her elder sister’s Amazon cart waiting for Nahda’s first stipend. Her parents have been watching her work this hard for two years.
But what’s actually waiting on the other side of that call is not the internship. It’s the version of Nahda who learned, at nineteen, that rejection is feedback if you let it be, and a verdict if you don’t.
What we learned watching Nahda’s first cycle
A few things stay with you, watching a Year 2 student navigate her first real professional rejection.
One. The students who go furthest are the ones who treat a no as data, not damage. That disposition is teachable, but only if the cohort around them models it and the mentors around them refuse to comfort their way into the easier story.
Two. The hardest part of placement preparation isn’t the technical work. It’s the honesty work. Knowing the gap between what you say you can do and what you can actually do is a skill nineteen-year-olds aren’t normally asked to develop. Inside a real placement cycle, with real outcomes on the line, they have no choice.
Three. The companies that said no to Nahda this cycle are not the companies that decide her career. The way she’s responding to those five no’s is what decides her career.
She’s not at the finish line. She is not the same person who applied to those first five companies either. That’s most of what the four years of a B.Tech programme is supposed to do, if it’s working.
She is nineteen. She’s learning lessons most engineers don’t learn until twenty-five. And she isn’t stopping.