There's a very specific kind of dread that comes with a "let's catch up" calendar invite from your manager with no agenda attached, sent exactly five months and three weeks into a six-month internship. I stared at that invite for a solid ten minutes before opening it, running through every mistake I'd made in the previous six months like some kind of guilty highlight reel, before realizing I was about to find out whether an entire off-campus gamble I'd made back in college had actually paid off.
How the internship even started, off-campus, with nobody's help
My college never had PhysicsWallah on its placement list, not for internships and not for full-time roles, and honestly I don't think most of my batch even considered it a "core tech" company back then, the way people casually rank companies by how impressive the name sounds in a group chat. I'd used PW's app myself years earlier for a few subjects, so I actually cared about the product in a way I didn't about half the companies my classmates were chasing, and one evening in November I just applied cold through their careers page for a six-month SDE internship, no referral, no placement cell involved, just a resume and a cover note I rewrote four times.
The recruiter reached out about two and a half weeks later, later than I'd hoped but not the silence I'd half-expected. The internship interview process itself was lighter than I'd braced for, one coding round with a mid-level engineer, a couple of array and string problems plus a light discussion of how I'd design a simple quiz-scoring function, followed by a short conversation with the team I'd actually be joining about what I'd be working on. I remember being almost disappointed at how quick it was, like the low stakes of an internship offer somehow made the moment feel smaller than it should have, even though getting it off-campus, with zero institutional backing, was genuinely the harder part of the whole thing.
The six months that turned out to matter more than the interview
I joined a team working on the live doubt-solving and DPP, daily practice problem, systems, the kind of infrastructure that quietly has to hold up when a few hundred thousand students are all hammering the same feature within the same twenty-minute window after a mock test result drops. Nobody tells you as an intern that "India's biggest edtech platform" isn't just a line on a slide deck, it's a very real, very specific kind of traffic spike that makes your code's edge cases stop being theoretical.
The formative moment of those six months happened around month four, during a JEE mock test result release, one of those nights the entire team quietly braces for without saying so out loud. A caching layer I'd touched two weeks earlier, a change I'd been fairly proud of at the time, started serving stale doubt-thread counts under load, nothing catastrophic, just wrong enough that students were seeing doubt counts that didn't match what was actually there, and a few of them noticed and started posting about it. My mentor pulled me into a call at close to midnight, not angry, just focused, and we spent the next ninety minutes tracing it back to a cache invalidation edge case I hadn't accounted for when a record got updated and deleted in quick succession. I remember apologizing about four times in the first ten minutes before he told me, fairly directly, that the postmortem mattered more than the apology, and could I please just walk him through what I now understood about the bug instead. That reframe stuck with me for the rest of the internship, more than any single code review comment did.
The rest of the six months was a mix of smaller wins and a slowly building sense that I actually understood the systems I was touching instead of just following instructions inside them, which is a distinction that sounds obvious written down and felt genuinely uncertain while I was actually living through it.
The "let's catch up" invite, and the conversion process nobody explains upfront
Back to that calendar invite. It turned out to be the informal start of the conversion process, not a warning, though nobody had told me in advance that's how it would work, which is exactly why I spent ten minutes assuming the worst. My manager walked me through a rough performance summary, mentioned the caching incident by name, and said the way I'd handled the aftermath, specifically staying on the call until it was actually fixed instead of just flagging it and going to sleep, had mattered more to him than the mistake itself had. Then he told me there'd be a short conversion loop over the next week if I wanted to convert to full-time, and that it wasn't a formality exactly, but it also wasn't designed to catch me off guard the way an external candidate's loop would be.
It was still a real loop. One technical round with a senior engineer from a different team, a DSA problem on finding cycles in a linked list followed by a slightly heavier system design conversation than I'd expected, design a simplified version of the doubt-thread caching system I'd actually broken months earlier, which felt almost deliberately pointed, though I don't think it was. I talked through cache invalidation strategies with a level of specificity I genuinely wouldn't have had six months earlier, not because I'd memorized a better answer, but because I'd lived through what happens when you get it wrong. The interviewer asked, at one point, whether I'd handle it differently now than I had in production, and I said yes, honestly, and walked him through exactly what I'd change, which felt less like defending a mistake and more like finally getting to show my work.
The second round was with an HR partner and briefly with the hiring manager together, mostly compensation and role scope for the full-time SDE-1 position, along with one genuinely direct question: did I want to stay on the same team or was I hoping to rotate somewhere else. I said I wanted to stay, partly because I actually meant it and partly because I suspected the honest answer mattered more than whatever sounded most ambitious on paper.
The offer, and the strange feeling of already knowing everyone in the room
The offer came four days later, over a call from the same manager who'd sent that dread-inducing invite two weeks earlier, and it was quietly one of the most anticlimactic good moments of my life, mostly because there was no dramatic reveal left to have. I already knew the team, already knew the codebase, already knew what a bad night during a mock test release actually felt like from the inside. What I hadn't expected was how different accepting a full-time offer from your own internship team feels compared to how I'd always imagined an offer call would feel, less like a finish line and more like someone quietly confirming something I'd already half-believed for weeks.
I told my parents that evening over a video call, and my mother's first question, before "congratulations," before anything else, was whether this meant I'd stop calling at odd hours during mock test weeks. I did not have a good answer for her.
What I'd tell my past self
If I could go back to the version of me who applied cold to that internship listing in November, unsure whether an edtech company without a "core tech" reputation in my college's WhatsApp groups was even a legitimate choice, I'd tell her that the caching bug in month four mattered more to how this whole story turned out than the actual interview did, on either end. The internship interview got me in the door. What got me converted was staying on a midnight call until a real problem was actually fixed, and being honest about it afterward instead of quietly hoping nobody would bring it up again.
I'd also tell her to stop assuming a six-month internship interview loop being lighter than a full-time one meant the stakes were lower. In hindsight, everything that actually determined the outcome happened in the six months between the two loops, not during either individual round, and if I'd treated the internship as a stepping stone to rush through instead of the actual evaluation period it quietly was, month four would have gone very differently for me.
And I'd tell her, gently, to stop scrolling through other people's interview experiences 2026 threads at midnight during the anxious gaps between updates, the way I did constantly during that final conversion week, and instead just go back to actually understanding the systems in front of her, since that's the thing that ends up mattering when someone actually asks you to defend a decision under a follow-up question. If you're somewhere in your own internship right now, wondering whether the offer at the end depends more on the interview loop or on how you handle the version of that midnight call that's inevitably coming your way, it's the second one, and the mock interviews and resume feedback I used on devsunite.com/resources before that internship even started are honestly what got me comfortable enough to stay calm on calls like that one in the first place.