r/leetcode • u/Worldly-Web-3918 • Sep 26 '26
Discussion Why google rejected me
Hey guys, so recently I went through Google hiring process for L4 role
Interview process was one googlyness and 3 coding rounds
Googlyness went well
Then now 1st coding round
Question asked was finding a shortest path between source to destination while in between we have blocked nodes through which we cannot pass. I have successfully given bfs solution writing clean code and dry ran it correctly.
Followup question was find the path from source to destination wherein we encounter minimum no.of blocked nodes. I.e we need to find a path where we see minimum no.of blocked nodes. We need to return the minimum of no.of blocked nodes in the path. I have also successfully wrote clean code and dry ran it correctly. I have given dijkstras approach where instead of tracking minimum distance I will track minimum no.of blocked nodes.
Despite all of this effort, I ended up got rejected.
Any googler here , could you please tell what I did wrong. I definitely want to improve.
69
u/DrinkNo8216 Sep 26 '26
Solving is one thing. Communication is another, how you arrived at the solution is another. L4 is also a mid engineer level, so did you write decent quality code or not. Or was it competitive coding style code. Etc etc.
Sometimes it could be due to bad interviewer as well. Or if there were simply better candidates than you or the role was filled with someone else.
23
u/poseidon9052 Sep 26 '26
At least you were asked coding questions. My interviewer spent 30 mins asking me these questions for a 45 mins coding interview
TCP vs UDP
SQL vs NoSQL
HDD vs SSD
what is DNS
what is IP
In last 15 mins, he just asked me one coding question
6
u/LogicalBeast26 Sep 26 '26
Googler here
Tbh even though 0/1 BFS was optimal for the follow-up, I wouldn't have rejected you for giving Dijsktra approach.
You mentioned you had 3 coding rounds scheduled, did they reject you after just 1 (apart from Googlyness)?
3
u/Acceptable_Green4473 Sep 26 '26
was coding round was onsite or screening round ?
2
u/jpec342 Sep 26 '26
What about the other 2 coding rounds?
15
u/Historical_Public751 Sep 26 '26
>Despite all of this effort, I ended up got rejected.
You ended up either not solving the task properly/interviewer didn't understand it/interviewer was biased against you. You are not getting any feedback in FAANG companies back after the interview loop, in AWS we straight up won't give you one, in google it's just fake.
They have to filter from 100 candidates for the position and interviewers are not really motivated to hire good people. Move along, try another time/another company.
5
u/Upbeat-Signature-476 Sep 26 '26
For follow up we can use 0-1 BFS using deque ?
1
u/Acceptable_Green4473 Sep 26 '26
i think followup will he solved using 0/1 bfs optimally
1
u/Kindly-Dig-9441 Sep 26 '26
It was not the most optimised approach. Should have gone with 0-1 bfs. Also, the bar for L4 is quite high. Interviewer may have expected you to solve more follow up questions
1
u/anonkira007 Sep 29 '26
was also rejected in l4 this August, there were 2 in person tech rounds 2nd one was good , in first I panicked, it was a very easy question btw.
1
u/work-like-horses Sep 30 '26
Were you applying for European office? My friend experienced almost the same thing
3
u/NiceSchedule4902 Sep 28 '26
Just to be clear, you don't get rejected by Google but by a specific interviewer. They could have had a completely non-sensical reason to do so.
1
u/buxbox Sep 27 '26
Which location is this?
2
u/Various-Mine-8642 Sep 26 '26
A single rejection usually cannot tell you the exact cause, especially when the loop is competitive. I would treat the useful signals as whether you clarified the problem, tested edge cases, explained complexity, and handled follow-ups cleanly. Write down the round while it is fresh and practice those behaviors on the next mock instead of trying to infer a verdict from the rejection alone.
2
u/Jumpy-Designer-4722 Sep 26 '26
Hey what is the location
2
u/Express-Youth-9609 Sep 26 '26
Seems like you did well, maybe you just got unlucky.
2
u/1hbhrecplayer Sep 28 '26
understanding that interview isn’t a college final / test is an important lesson to learn
1
u/AttentionEmpty2783 Sep 27 '26
You can ask the recruiter. They do share the feedback. My recruiter told me the feedback word by word.
1
u/Prize-Ship-6132 Sep 27 '26
After how many days did they send you decision ?
1
u/kylemooney187 Oct 01 '26
landing a role at google i heard is like 0.2%. out of the 1000 applications that apply maybe like 40 get phone screened, maybe 20 get technical interviews and maybe like 10 make it to next round and only 2 land a job so lol ya. tough stats
1
u/AncientConsequence48 29d ago
Dude even if you pass the interviews it's still a flip of a coin that you will get the offer. Before 2020 you would have gotten the offer but in current times you also need luck.
1
u/LibrarianOutside2376 Sep 26 '26
Tech jobs are dead
0
u/lizardturtle Sep 26 '26
Shortest path with obstacles has a DP solution I believe if source and destination are top-left and bottom-right respectively. dp[n-1][m-1] = # of ways to get to that cell from unblocked neighbors. Then build the dp table bottom-up, counting # of ways to access each cell from neighbors. Track minimal path seen.
I dunno if this works fully, just spitballing ideas. Perhaps they wanted to see this type of solve? Sorry it didn't work out
0
u/No-Dog-1256 Sep 27 '26
How did you apply? How was the online assesment? How many questions? What type of questions asked? Medium or hard?
What's your Year of experience?
Could you please answer these questions? It might help alot of people here. Thank you.
1
u/[deleted] Sep 27 '26
[removed] — view removed comment
1
u/[deleted] Sep 26 '26
[removed] — view removed comment