11–20 of 239 posts
Keyword research and trends... https://trends.google.com/trends/explore?date=all&geo=US&q=G...
Isn't the interview different depending on the job?
But to answer your question, yes, absolutely.
Genuine Question: Apart from maybe the money or a nice resume entry, why would you/do you want to?
The amount of time required to 'learn' the Google interview would be time that could be spent learning more universally applicable skills. Is it true that an experienced developer would not be able to pass the interview without studying using a similar guide? If so, then the interview process is... fubar.
In that sense, it's probably a good indicator for Google that the interview advice includes "practice writing code", "make it a habit to validate input", and "learn about data structures", and it's probably a bad indicator for Google that the advice includes "practice writing syntactically correct code on a whiteboard" and "practice solving problems with a 30 minute timer."
Genuine Question: Apart from maybe the money or a nice resume entry, why would you/do you want to?
> For the phone interview, it will be on a Google document, and for the onsite interview, it will be writing code on a whiteboard. That part is not completely correct. At onsite can choose to write code in a Chromebook which will have a lightweight editor with syntax highlighting.
Genuine Question: Apart from maybe the money or a nice resume entry, why would you/do you want to?
Return question: Do you have a firm grasp on quite how much money it is?
Genuine Question: Apart from maybe the money or a nice resume entry, why would you/do you want to?
Isn't the interview different depending on the job?
My immediate reaction to the title of the article was "... for SWEs and possibly SREs". But to answer your question, yes, absolutely.
The amount of time required to 'learn' the Google interview would be time that could be spent learning more universally applicable skills. Is it true that an experienced developer would not be able to pass the interview without studying using a similar guide? If so, then the interview process is... fubar.
A perfect job interview could be defined as an interview for which the best study technique is to become a better choice for the role. Studying skills that would not directly contribute to job performance would not change the result of a perfect job interview in any way. In that sense, it's probably a good indicator for Google that the interview advice includes "practice writing code", "make it a habit to validate in…
> practice writing syntactically correct code on a whiteboard
This probably differs from interviewer to interviewer as to how strictly it's adhered to, but it's not really a hard and fast rule. I'm sure there are some interviewers that will ding you on a forgotten semicolon, but I suspect that most would not.
Personally I look for code that isn't so far from syntactically correct that it's clear you are trying to BS me. I'll even accept pseudocode for the most part. But I've had candidates that try to make up language features, and that doesn't fly with me.
> practice solving problems with a 30 minute timer
I only give my candidates 30 minutes. The whole interview is 45, I spend 5 minutes introducing myself and setting up expectations, 30 on the question, and 10 on answering their questions (after all, they're also interviewing us).
You can tell pretty early whether they're on a solid trajectory, and I'll offer the occasional hint to keep someone on track, or ask tangential questions if they're doing well on time. Not finishing isn't a deal killer, provided you had a solid approach and weren't just running in circles. But a good candidate will finish in about 25 minutes and we can spend some time talking about alternate approaches. Sometimes I'll show them the optional approach and see how that conversation goes.
Nine times out of ten a candidate scores low because they overlooked an infinite loop or code would crash on boundary conditions and candidate wasn't able to realize that even with hints.