Many money and good benefits. Good engineering culture.
Too big to do something.
Too much focus on technology.
Just do small things, get things done, and move quickly.
One-hour technical interview. Start to end, technical. Questions range from "bookish" ones, like "Tell me about Oracle memory structures," to scenario-based ones, such as "If you found a query to be slow suddenly, what would you do?"
Posted for a job in Jan 2013 on Google's website. A recruiter e-mailed me and called to set up a phone interview. I never had the soft skills interview; they immediately went into the technical interview. The questions were a bit interesting in that
The interview was intense but well-structured, with a strong focus on SQL, optimization, and cloud systems. It tested both technical depth and problem-solving under pressure, alongside teamwork and impact through behavioral questions.
One-hour technical interview. Start to end, technical. Questions range from "bookish" ones, like "Tell me about Oracle memory structures," to scenario-based ones, such as "If you found a query to be slow suddenly, what would you do?"
Posted for a job in Jan 2013 on Google's website. A recruiter e-mailed me and called to set up a phone interview. I never had the soft skills interview; they immediately went into the technical interview. The questions were a bit interesting in that
The interview was intense but well-structured, with a strong focus on SQL, optimization, and cloud systems. It tested both technical depth and problem-solving under pressure, alongside teamwork and impact through behavioral questions.