Preparing for Success - Google
I recently managed to clear AWS and Uber interview but got dinged by Google. The recruiter mentioned that my performance was not consistent across all rounds. Background - I have done 235 LC problems and did some system design and OOP practice. I am not sure what it takes to get in. What can I improve upon. Should I solve more LCs, should I structure my code well during interviews, should I always come up with the most optimal solution? Any help is appreciated.
Dude really ... Stop thinking that you need to be validated by Google
I agree that it all comes down to validation. Do you think I should stop preparing and focus on real open source projects than spending time doing LCs everyday?
@wbwhtwwnw Stop telling yourself that and look around you and you'll realize that amazon sucks.
So which one are you going with Uber or AWS? What their offer?
I stopped leetcoding and started doing open source project after I got an offer from google. Leetcoding is waste of time
As a Googler, let me tell you this. There is nothing special at Google. It's just another company. In my opinion, you should be looking at team and quality of work that you would be doing. Half of us just move protos from A to B and nothing else. So don't feel bad and be obsessed for joining Google. Go to places where you can learn more and be happy.
Same shit at amazon Move some coral responses from point A to point B. These days most engineers write Lambda and CloudFormation templates.
recently I was asked an upgraded version of a rare LC question (some traps were added, instead of algorithm, he asked to design a service whose core idea was the same as the LC question) and asked to do it bug free and hand writing compiling in 20 mins for a screen. The interviewer reserved 20mins before to ask other questions and 5mins after the coding for Q&A. I got the idea right, but my code didn’t compile at the beginning, and didn’t have enough time to fix a bug in the code. No onsite of cause.
I wish if I can ask the interviewer to do the same problem in the same amount of time...
There are two kinds of interview preps. One is for Google and the other is for all other companies. For the first one study EPI and do Google tagged questions for practice. For the second one study CTCI and do the top 100 tagged and company specific questions.
This stuff is random, you could easily have gotten Google and then been rejected by Uber.
235 is such a low number. Just come back next year :=)
235? Those are rookie numbers.
Was this sarcastic or true?
Truth.