I have L5 onsite interview coming up for Google next month. What to expect ? Any tips? Role: Software engineer
What role...?
Updated the post thanks
inb4 downlevel
??
What he is saying is "don't do it man. They will downlevel you and low-ball you and make you feel worse..."
Why moving from fb?
TC YOE?
Also curious how much YOE to qualify for L5 interview.
TC: 360k YOE: 4.5
Develop a weird tic so the interviewer has some sympathy for you
I also have a google on-site coming up. Are you interested in doing practice mock interviews? 30 mins each then switch.. practice makes perfect
Typically your recruiter will explain you what to expect and send you links on some training materials. Beyond that here are some tips from my experience: * Since you are interviewing for an L5 software engineer position, you should focus both on coding and system design. * Practice coding exercises. There are plenty of online sites. Cracking the coding interview is a good book. You don't have to read the entire book. But definitely read initial chapters on what to expect, how to analyze code for computational/space complexities. Practice on tree search, solving problems using hashtables * You don't have to know all libraries or subsystems. For ex: I did not know the Android Camera API well. I simply declared some API on my own as a starting point and focused on solving the problem using that. * Often the best solution comes from trying to solve the problem as we humans do. Try not to think complex algorithms directly. You can fine tune and improve the solution afterwards. * Your recruiter will work you. If you run into issues during the interview, always explain that to your recruiter. In my case, I could solve only one half of the problem in the last interview, because the interviewer took major portion of interview time to talk about Google and Google culture. I only had 15 mins to listen to, ask questions and solve the problem.
Do you know what might be asked in a object oriented design round?
That will be really up to the interviewer. There are no predetermined set of questions. In my case, the interviewer simply took a problem that his team was trying to solve and asked me to solve that and asked questions surrounding that. With a solid OOP background, this part of the interview should be a breeze compared to coding interviews.
You could just post your name here
Abdo and tyrone checking in.