Download AppI still remember refreshing my email every hour for two weeks straight, convinced my laptop's wifi was somehow eating the recruiter's reply. That's the part nobody puts in the LinkedIn post-offer announcement — the waiting is worse than any DSA round.
A bit of context: I'm from a tier-2 engineering college in UP, no campus placement drive for Amazon that year, so this was a cold off-campus application through the careers portal in August. Not a referral, not a hackathon shortlist, just a resume and a lot of hoping. I'd applied to maybe fifteen companies that month and Amazon was the third one to even respond, so by the time the OA link showed up I'd already half convinced myself it would go nowhere, the way the other two had.
The four months before any of this even started
Before I get into the rounds, a quick note on prep, because I think people underestimate how long the runway actually needs to be for an off-campus fresher shot. I started seriously around April, four months before I even applied, doing maybe two problems a day on the side while finishing my final semester coursework, which in hindsight was not nearly consistent enough and I paid for it with a few shaky weeks in July when I realized graph problems still made me sweat. Arrays, strings, and two-pointer patterns came easily by June. Trees, graphs, and DP took the full four months and honestly I'm still not fully confident on hard-level DP even after the offer.
I also spent an embarrassing number of nights reading old interview experience threads instead of actually solving problems, telling myself it was "research." Some of it helped, most of it just fed the anxiety by showing me how many brilliant-sounding people had still gotten rejected. If there's one thing I'd change, it's spending less time reading about other people's interviews and more time doing timed mock rounds on my own, out loud, to actually get comfortable narrating my thought process instead of just solving quietly in my head.
The OA nobody prepares you for properly
Everyone tells you to grind LeetCode for the Amazon OA and, yes, do that, I got two DSA problems on HackerRank, one array/sliding-window question and one that was basically a dressed-up graph traversal presented as a delivery-route problem, very on brand for Amazon honestly. But what actually threw me off was the Work Style Assessment section after the coding part. It's this weird personality-style simulation where you're dropped into a mock Amazon workday, emails piling up, a manager asking for a status update, a teammate blocking your progress, and you pick how to respond from a set of options that all sound reasonable until you read them three times.
I went in expecting pure code and ended up spending twenty minutes second-guessing whether "escalate immediately" made me look like Ownership or like I couldn't handle ambiguity on my own. There's no right answer sheet floating around for this section the way there is for DSA, which made it weirdly more stressful than the actual coding. If you're prepping, actually read up on the sixteen Leadership Principles before this section, not just before the interviews, they're testing the same thing here, just without a codebase in front of you. I wish someone had told me that instead of me finding out mid-assessment, staring at four almost-identical-sounding options with the clock quietly ticking down in the corner.
Cleared the OA, got the "we'd like to move forward" email about ten days later, and then complete radio silence for almost three weeks. I checked my spam folder more times than I'd like to admit, at one point convincing myself the recruiter's entire domain must be blacklisted by my email provider, which obviously wasn't true, I was just bored and anxious in equal measure. My mom kept asking "coding wale se koi reply aaya?" every single evening and I kept saying "abhi tak nahi" until it started to feel like a running joke in the house, one that got slightly less funny with each passing day.
Round one: DSA plus a Leadership Principle that caught me off guard
First technical round, video call, interviewer joined two minutes late which somehow made me more nervous than if he'd joined early. I sat there staring at the "waiting for host" screen replaying my resume in my head, wondering which project he'd ask about, half convinced my wifi would cut out at the worst possible moment the way it always seems to during anything important. Two DSA questions, a dynamic programming one that was a variant of the classic house robber pattern, and a string problem around finding the longest substring without repeating characters. I solved the first one fine, walked through recursion, then memoization, then got it down to O(n) space, no issues, and he seemed genuinely satisfied with how I explained the space optimization instead of just jumping straight to the answer.
The second one, honestly, I blanked for a good ten seconds. Not because I didn't know the pattern, I use sliding window all the time, but because he asked me to explain my approach before writing any code, and my brain just went completely quiet. I said "give me a second to think out loud" and actually meant it, staring at the whiteboard like it owed me an explanation. Recovered, walked through it slowly, got there, and honestly those ten seconds of silence felt like ten minutes in the moment, the kind of silence where you can hear your own heartbeat over the laptop fan.
Then came the Leadership Principle question: "tell me about a time you disagreed with a teammate." I hadn't rehearsed this one specifically and ended up rambling about a college project argument for way too long before looping back to what I actually learned from it. He didn't seem bothered, but I definitely over-explained, the kind of answer where you can feel yourself going in circles but can't find the exit ramp. Note to self for next time: STAR method exists for a reason, use it instead of narrating the entire timeline of a group project gone slightly sideways.
Round two: the bar raiser round everyone warns you about
This is the one that has an entire folder of Blind posts dedicated to it, and honestly, the mystery is bigger than the actual round. Nobody tells you who the bar raiser is, mine was from a completely different org, SageMaker-adjacent, nothing to do with the team I was interviewing for, and it just felt like a slightly longer, slightly deeper version of round one. I'd spent the two days before this round trying to guess which of my upcoming interviewers would be the bar raiser based on absolutely nothing concrete, which in hindsight was a complete waste of nervous energy I could have spent actually revising.
Two more Leadership Principle deep-dives, both with a lot of "and then what happened, and then what did you do, and why that and not something else" follow-ups. This is where "don't use BS stories" actually matters, the moment my answer got vague, he zeroed in on it, gently but persistently, like he already knew there was more to the story and was just waiting patiently for me to get there myself. One DSA question too, a merge-k-sorted-lists variant, and by this point I'd stopped being nervous about the coding part entirely, it was almost a relief to be asked something with a definite right answer after twenty minutes of behavioral cross-examination that felt closer to therapy than an interview.
What surprised me most about this round was how unremarkable it felt in the moment. No trick questions, no gotchas, just someone patiently pulling threads on every answer I gave until we hit something real underneath the polished version. It's the follow-up questions on your own decisions that actually test you in this round, not the algorithm, and I only understood that properly after it was over and I was replaying the whole thing on my walk back from the library.
Round three: the hiring manager round and then more waiting
HM round was almost a relief after the bar raiser, mostly project discussion, why I built what I built, some light system-design-flavored questions kept appropriately shallow for a fresher, nothing like a full HLD interview, just "how would this scale if 10x more users showed up" and "what would break first." Felt like a conversation more than an interrogation, the interviewer even laughed at a self-deprecating comment I made about my project's questionable database schema decisions from six months earlier.
We also spent a good five minutes just talking about the team, what they actually build day to day, what a typical sprint looks like, which nobody tells you also doubles as them quietly checking if you're actually interested in the role or just chasing the brand name on your resume. I asked more questions than I usually would in an interview, partly out of genuine curiosity and partly because I'd read somewhere that asking good questions signals ownership, and either way it seemed to land well, judging by how much longer the round ran past its scheduled slot.
Then: eleven days of nothing. I refreshed my email so much my roommate started making fun of me, doing an exaggerated impression of me lunging for my phone every time it buzzed for an unrelated Swiggy notification. I tried to distract myself by applying to more places, half-heartedly finishing a side project, anything to stop the compulsive email-checking, but it never fully worked, there's a particular kind of restlessness that sets in when a decision that big is sitting in someone else's inbox. Recruiter finally called on a random Tuesday evening while I was mid-dinner, and I picked up with rice still on my hand, heart absolutely pounding before she'd said a single word beyond "hi, is this a good time to talk."
The offer call itself was almost anticlimactic after all that buildup, a few minutes of congratulations, a rundown of next steps, documentation, background verification, and a joining timeline still a couple months out. I hung up, sat in complete silence for about thirty seconds staring at nothing in particular, and then called my parents, who I'm pretty sure didn't fully register what had happened until I said the word "Amazon" three times in three different ways.
What I'd tell my past self
Prep DSA, obviously, but don't skip the Leadership Principles the way I almost did, thinking they were just HR fluff tacked onto the real interview. They show up in the OA's work simulation, in every technical round's behavioral half, and they're the entire spine of the bar raiser round, so treating them as an afterthought the way I initially did is genuinely a mistake that costs you more than a shaky DP answer would. Write out two or three real stories in advance, ones with actual conflict and a real lesson, not the sanitized version you'd put on a resume, because the follow-up questions will find the gaps in a story you haven't actually thought through properly.
Also: the silence between rounds is normal, not a rejection signal, even when it stretches past two weeks and your brain insists otherwise at 2am. I spent so much energy those weeks constructing elaborate theories about what the silence meant, when really it was just recruiter bandwidth and scheduling, nothing personal, nothing dramatic playing out behind the scenes. If I could go back, I'd tell myself to keep applying elsewhere in parallel instead of treating every gap in communication like a verdict on my worth as a candidate.
And the coding, while important, is genuinely not the hardest part for a fresher going in with a decent DSA foundation built up over a few consistent months. The harder part is staying composed when someone keeps asking "why" after you think you've already answered the question, and being honest enough in your stories that the follow-ups don't trip you up later in the loop.
One last thing I underestimated completely: how much the whole process tests your ability to just sit with uncertainty. Between the OA and the offer call there were maybe five separate multi-day silences, and each one felt like it demanded some kind of action from me, refresh the portal, reread the job description, message a senior for reassurance, when really the only thing that actually helped was going back to normal life and treating the process like background noise instead of the main event. Easier said than done, obviously, especially the first time you're going through it, but it's the one piece of advice I'd actually want past-me to internalize rather than just nod along to.
If you're just starting out, the mock interviews and resume feedback on devsunite.com/resources genuinely helped me get past the first filter before any of this even started, and looking back, that early prep is probably what gave me the calm to handle the harder, more personal rounds later on.