#Google on-site
8 messages · Page 1 of 1 (latest)
The Google interview is very interactive. It isn't just a case of "here's this problem, solve it, and if you code up an optimal solution, you're good." They really care about the thought process, i.e., how you think and your ability to communicate and demonstrate this reasoning. This is in stark contrast to the interview process at Meta.
So, I'm not saying reading the "Intro to Algorithms" book is bad, nor is doing Google-specific questions on LeetCode a bad idea. But whatever your prep plan is, it must involve you solving problems under pressure with a human simulating the Google style. One big part of this is that, after solving a problem, they can throw in new information or constraints and then see how you adapt.
@soft adder
Would be good for you to outline a prep plan, and then use that to determine how much time you need. Make sense?
What level is this for? @soft adder
SDE2
I thoguht reading the book would me a good idea since it would allow me to get my fundamentals down pat. I would of course do practice interviews on praamp (although that kinda sucks) as well
I am so lost on how to prepare for this.. I assume I have like a month to prep
This guide will give you some structure, and the. You can tweak to suit your needs
An optimal way to prepare for coding interviews | how to grind smart not hard!
https://youtu.be/sLJ6p5rSnuo
This video discusses a phased approach. This 4-step approach is optimised to get you truly interview-ready with minimal amount of effort & time.
The primary focus is on those pesky coding interviews, you'll face when interviewing for software engineer roles. However the general idea behind this technique can be applied to other types of interv...