The interview was really bad. The interviewer was fifteen minutes late because she was looking for a phone to call me. No phones available at Google?
She asked three decent questions, but I don't think she was prepared at all for the interview. I believe she picked these questions online quickly:
I could tell she picked that question online very quickly and probably didn't have a real answer herself. As I was trying to solve the problem, she was picking on little syntax, which even great programmers don't pick up on the first try.
With this question, it takes a long time to simply check that the string is long enough and not too short. Then she said you can simply get the alphanumerics, i.e., 1800GOFEDEX. But of course, that doesn't work because someone can write: 1800()GOFEDEX, 18(00)GOFEDEX, 1800(G)OFEDEX, 1()800GOFEDEX, 1-(800)-GOFEDEX, etc.
So, going through these cases alone takes a long time, not ten minutes, especially when she was late. As I pointed out how crazy it would be to write actual code, she said time was over. She definitely didn't have any clue how that problem would be solved.
What happens when you type google.com in the browser?
What is the difference between GET and POST in forms?
Write a program to translate an alphanumeric phone number to numbers only.
The following metrics were computed from 26 interview experiences for the Google Software Engineer role in Boston, Massachusetts.
Google's interview process for their Software Engineer roles in Boston, Massachusetts is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Google's Software Engineer interview process in Boston, Massachusetts.