Free lesson · JavaScript Basic to Advance
Founder Stories: The Full Rejection Arc
The People Who Built This Platform
This is the final Topic. Across thirteen modules and ninety-some Topics, you've learned JavaScript at the depth needed for senior and staff FAANG interviews. You've worked through over a hundred thousand words of material. The credentials of the people who taught you have appeared in fragments throughout - references to Google, Meta, Amazon, Microsoft, Apple, Netflix, and AlgoInsight itself.
What hasn't been gathered in one place is the story underneath the credentials. The path each founder took to get from where you might be sitting now to where they are today. The aggregate is the platform's central marketing wedge: the seven founders of AlgoInsight have been rejected by FAANG companies fifty-eight times collectively before getting their offers.
This Topic puts those stories side by side. Not as marketing. As proof. Proof that the people on the other side of the interview table were once in your seat, didn't make it through, kept going, and eventually broke through.
The number is real. We kept the rejection emails. We compared notes. We discovered, as we worked together, that the failures had taught each of us something different - and that the collective experience across the seven of us was the foundation we'd been missing as candidates.
This Topic gathers each founder's story, in their own voice. The full version of each story has appeared in earlier Topics; this is the consolidated reference.
Nikhil Joshi - Google L5 SWE, CTO
I failed Google twice before getting in. The first time, at 24, I'd just shipped a payment system at Razorpay handling 800 crore rupees per day. I was supposed to be ready. The interviewer asked me to implement a Segment Tree. I had never heard of one. I walked out of the Google Hyderabad office, sat in the parking lot, and cried.
The second attempt, 18 months later: cleared coding, bombed System Design. I had built distributed systems in production but I couldn't articulate them in 45 minutes with a stranger watching.
The third attempt: passed. The difference wasn't ability. The difference was language. I'd learned to translate production experience into the vocabulary the interviewers were listening for.
What I took from those years: you cannot fake the runtime model in a senior interview. You either understand it or you don't. Spend the time.
Deepika Nair - Meta E6 Staff, Chief AI Officer
I have 23 rejection emails from FAANG companies. I kept every single one. My problem wasn't knowledge - it was time. Under pressure, I wrote correct solutions 8 minutes too late. I was a perfectionist who over-engineered under stress.
I built a spreadsheet tracking every mock interview - time per problem, where I got stuck, which patterns I recognized versus derived from scratch. I treated myself as a system to be optimized.
Four months of that discipline. Then Meta's loop. E6 offer, skipping E5 entirely. That spreadsheet became the inspiration for AlgoInsight's AI evaluation engine.
Twenty-three rejections taught me that the gap between "knows the answer" and "produces the answer in time" is a real, trainable skill. Most candidates work on the first gap. The senior candidates work on the second.
Deepika owns the AI evaluation engine on the platform - the quantified-feedback system that came out of her interview-prep spreadsheet methodology.
Brandon Carter - Amazon L7 Principal, Head of Curriculum
I'm the first person in my family to go to college. Graduated from Georgia Tech in 2008 into the financial crisis. Spent 4 years at IBM doing enterprise Java that never touched algorithms. I'd never thought about Binary Search Trees.
Applied to Google in 2012 on a whim. Bombed it. Reapplied 3 years later and failed again, this time on System Design. I could code by then, but I couldn't design at scale in 45 minutes with a stranger watching.
Joining Stripe taught me what "designing at scale" actually meant. Systems handling 100M+ transactions per day. I reapplied to Amazon with that context. L7 Principal offer on the first attempt.
The lesson that's served me through 300+ interviews as Amazon Bar Raiser: most candidates over-rely on inheritance for OO design. The first instinct - "this is similar to that, so subclass it" - is the instinct senior engineers learn to resist. Composition first. Inheritance only when the model demands it.
Brandon's story appears in Topic 8.7 - the OO design Interview Lens. His 300 interviews as Bar Raiser inform the OO Design course he owns on AlgoInsight.
Olena Marchenko - Microsoft L60 SWE, Head of Product
I didn't study CS. I studied Economics and spent 4 years as a financial analyst in Warsaw. Learned to code at 26 from freeCodeCamp and YouTube. My first 11 tech interviews were all rejections.
The problem wasn't being behind engineers with CS degrees. The problem was that nobody told me a self-taught background meant I had specific foundational gaps that needed a structured path. No mental model for time complexity. No familiarity with graph algorithms. They just said "not quite ready."
Moved to London. Joined Zalando. Spent two years deliberately building what I'd missed. Microsoft offer on the second attempt.
What I took from those years: the gap between bootcamp grad and CS grad is real, but it's specific, and it's closeable. The hard part is identifying what's actually missing. That's the work the AlgoInsight platform is meant to make easier - naming the gaps so they can be closed deliberately.
Olena's story appears in Topic 12.7 (the Zalando drag-and-drop moment) and shaped the non-traditional-background learning track she owns on the platform.
Arun Selvam - Apple ICT3, Head of Community
I'm 24. 9.2 CGPA from Anna University, top 500 on Codeforces, two internships - and 14 consecutive rejections before Apple. Atlassian, Flipkart twice, Amazon, Microsoft, Uber, and 9 others.
I was 70 percent of the way to correct solutions each time. Correct, but slow. I had no framework for the moment I hit a wall - I'd freeze, the clock would drain, the interviewer would close their laptop ten minutes later.
Apple was my 15th attempt. I spent 3 months rebuilding my approach specifically around the 30-second window after my mind went blank.
The Stuck Protocol came out of that rebuild. It's in Topic 14.3 of this course. It's the single most important interview skill I learned, and it's the framework I teach in every Discord mock interview I run. If you take one thing from Module 14, take that protocol.
The course material for Module 14 - orientation, question map, Stuck Protocol, 30-day plan, mock interview - comes from my work as Head of Community on the AlgoInsight platform, and from those 14 failed interviews.
Emeka Okafor - Netflix L5, Head of Data Infrastructure
I grew up in Lagos, teaching myself Pascal at 14 on a second-hand computer with a pirated compiler. Andela's inaugural cohort in 2015 was my first access to world-class engineering mentorship.
First Google attempt from Lagos: passed the coding screens. Then visa coordination for the onsite fell apart. Three months of preparation, gone.
Second attempt from London: passed everything including reference checks. Then received a form rejection with no feedback. No reason given.
Built up 5 years of production data engineering at Booking.com handling 1.5M bookings per day. Netflix reached out. Passed 7 rounds in Los Gatos.
Two rejections is the smallest count among the founders. But what those two taught me about the asymmetry between candidates inside the US and candidates outside it is what drives the Global Candidate preparation track I own on AlgoInsight. The interview process is harder when you're solving for visas and timezones on top of the technical questions.
Emeka's Netflix work informed Module 9 (Async) and Module 13's memory and performance Topics. The Booking.com concurrency-limit question from Topic 9.12 is from his interview prep.
Swati Bajpai - Google L8 EM, CEO
My story is different from the others. I have zero technical rejections. I got into Google on the first attempt. I was on the Senior Staff track.
Then I spent 3 years watching less technically capable engineers get promoted faster than me - because they understood the performance review system, how to frame impact, how to work the FAANG career ladder strategically. They were playing a game I didn't know had rules.
I left for an MBA at IIM Ahmedabad specifically to understand organizational dynamics. Came back to Stripe as L6 Principal. Returned to Google as Engineering Manager.
My failure wasn't technical. It was meta - not knowing how the game was scored. That's why the Career Trajectory category exists on AlgoInsight: most platforms stop at "you got the offer." The unique competitive wedge we have is what happens after.
Swati's career trajectory track isn't covered in this JavaScript course - it lives in a separate part of the AlgoInsight platform. But her story is part of the team's collective experience.
The Aggregate
Fifty-eight rejections across six founders. Most of them at the start of careers that are now thriving at Google, Meta, Amazon, Microsoft, Apple, and Netflix.
If you take one thing from this Topic, take this: the people on the other side of the interview table were once where you are. They failed. They learned. They tried again. The path is not linear. The rejections are not verdicts.
Every founder on this team has watched candidates with their exact pattern of strengths get an offer, and watched candidates with their exact pattern of weaknesses bomb the interview. The variable is preparation, articulation, and composure. Those are trainable. That's why this course exists.
You finished it. Now interview.
The end of the course. Thank you for reading. The team will be reading your feedback on the Discord - come find us there with questions, mock interview requests, or success stories.
— Arun, on behalf of Nikhil, Deepika, Brandon, Olena, Emeka, and Swati