Slow and very conservative sometimes.
I think you should do as many side projects as you can and then prepare a lot of interview questions from the book. Luck is very important. Other than that, you need experience for around 2 to 3 years.
I applied for a Google SWE position and went through a recruiter call first. The recruiter was very friendly and clear about the process. My phone screen had two coding questions: * One on arrays (two sum variant) * Another on dynamic programming (u
Typically, five people were on-site, posing a mix of design and coding questions. The coding questions were pretty standard, with three in total. The disappointing part was that the interviewing seemed very mechanical. There was no real conversation
I think you should do as many side projects as you can and then prepare a lot of interview questions from the book. Luck is very important. Other than that, you need experience for around 2 to 3 years.
I applied for a Google SWE position and went through a recruiter call first. The recruiter was very friendly and clear about the process. My phone screen had two coding questions: * One on arrays (two sum variant) * Another on dynamic programming (u
Typically, five people were on-site, posing a mix of design and coding questions. The coding questions were pretty standard, with three in total. The disappointing part was that the interviewing seemed very mechanical. There was no real conversation