ok so this is going to sound like i am bragging but i promise the opposite. 400 leetcode problems. four months. i had a spreadsheet with columns for topic tag, solve time, first attempt yes or no, and i color coded the whole thing green when i got one right. 85 percent acceptance rate on mediums. i used to open it before work and just look at it which typing that out now makes me realize how unhinged that was lol. graduated 2024, horrible market, Blind and reddit both screaming 300 to 500 minimum for any FAANG offer. i always overshoot targets so 400 it was. two mediums before work every day, one hard after dinner, everything logged.
month three i was around 280 and stressing. crossed 400 end of month four and the morning of my Google onsite i sat there looking at 400 green rows thinking no shot i fail this. absolute confidence. delusional confidence actually.
then Marcus texts me like three days after my rejection. says he got into Meta. i go congrats how many did you do. he says 150. i put my phone face down on the kitchen counter and did not text him back for two full days because i had no idea what to say. did three times his number, got rejected, this dude is heading to Menlo Park. i still feel bad about ghosting him honestly, he did not deserve that, i was just in a really dark place about it.
the rejection email said "strong on coding fundamentals but could not extend solutions past the initial approach." recruiter friends have since told me what that means in plain english. he solved the textbook version fine and completely froze when we changed one single constraint. one.
phone screen was fine. sliding window, caught an edge case, eight minutes, whatever that part does not matter. round one graph problem, fine. round two is the one that wrecked everything and i need to explain exactly what happened because it changed how i think about all of this. tree question. recognized it from something i solved like a week before so i wrote the code fast, had that little smile on my face, interviewer probably saw it too. then she goes ok cool now your tree has a billion nodes and none of it fits in memory.
my brain locked. sat there getting hot in the face staring at code i wrote thirty seconds ago and suddenly could not even explain to myself. across four hundred problems on that beautiful spreadsheet i never once, not one single time, thought about what happens when data does not fit in RAM. the leetcode judge assumes everything fits. always. every single problem. i trained for four months on that assumption and Google asked the one question leetcode never does and i had nothing lol.
finally called Marcus after ghosting him and that conversation honestly changed everything. he only solved maybe 50 unique problems. fifty. but he never moved on from them. solved it with an array then the input becomes a stream then you need concurrent access then flip from optimizing time to optimizing space. same fifty problems mutated over and over until he could handle whatever somebody threw at him. he said he found some blog that went through like 200 FAANG interview write-ups and the big takeaway was that interviewers change your constraints mid-problem in roughly 80 percent of rounds. follow-up questions. the thing i did zero practice on across all 400 of my leetcode solves. literally zero. solved it, green check, scrolled to the next one. like training for a fight by hitting a bag that cant swing back and then wondering why a real person drops you immediately.
Jake got Google with about 180. another friend did 120 but burned a full month on system design and behavioral stuff. i did 400 and got the rejection email. there is no correlation between raw count and whether you pass once you are past maybe a hundred done properly, it turns into something completely different from what reddit makes you think.
stopped doing new problems after that call. pulled 50 from my solved list and Marcus got on zoom twice a week and absolutely destroyed me. memory is limited now what do you do. this has to run across three regions what changes. duplicates everywhere and your code assumed unique values. i kept failing things i had green checkmarks on which was genuinely humiliating that first week but thats the entire point apparently. also crammed two weeks of system design which i completely skipped during the grind because i was staring at the leetcode count like it was my GPA or something. Google weighs system design equal to coding. i gave up all that prep time for nicer spreadsheet formatting.
second attempt i had InterviewMan running during the actual calls. mic picks up conversation and throws nudges on an overlay nobody on the call can see. the follow-up hints were everything, interviewer changes a constraint and instead of dead air i had something to pull on. twelve bucks a month and i almost laughed at the price given what four months of solo grinding cost me in time. only worked because i had done the depth stuff with Marcus though, hints are just random words if you dont have context to make sense of them.
two offers. six weeks. zero new leetcode problems. still sitting at 400 on my profile and that number means nothing to me anymore. the fifty i actually went deep on, those got me through. if you are at a hundred right now panicking about getting to three hundred just stop and go back. start changing the problems you already solved. that is what they actually test for and almost nobody does it.
Ready to Ace Your Next Interview?
Join 57,000+ professionals using InterviewMan to get real-time AI assistance during their interviews.
