How is that a good answer at all? If I was asking a candidate that question, I'd expect them to make an inverted index
How I Embarrassed Myself in My Interview With Google
21–30 of 58 posts
Re: How I Embarrassed Myself in My Interview With Google
#22If im ever being interviewed by Google, i'm going to say "hold up let me google the solution to that real quick." A good engineer spends about 95% of their time discovering new things to learn about their craft. An even better engineer uses what other engineers have already discovered and shared with the world to further their understanding. If the world only consisted of the "even better" engineers things like this…
If you were asked to write a regex engine as an exercise you'd say "No thats not a problem that needs to be fixed anymore."?
How would you expect to be able to improve performance of regex engines without understanding how a basic regex engine works?
Re: How I Embarrassed Myself in My Interview With Google
#23Earlier quoted context omitted.
Yup, it's serious. I'm don't know for certain that I've been ruled out of a follow-up interview, but I got that vibe by the end.
Do you have any open source projects? The first thing i'm looking for as a developer when I visit your websites is a link to any code you have written. Which as far as I can tell doesnt exist? A programmer without a portfolio of source code is like a painter without a portfolio paintings. I assume Google scouts are usually looking to hook the exceptionally rare "Monet" and "Picaso" software engineers swimming around…
Google interviewers are interested in how well you can code (or design a solution) in a whiteboard for 45 minutes. I'm not claiming that it's the best way, and who knows, it might be the absolutely horrible way to interview candidates, but that's the way it is here.
Re: How I Embarrassed Myself in My Interview With Google
#24If im ever being interviewed by Google, i'm going to say "hold up let me google the solution to that real quick." A good engineer spends about 95% of their time discovering new things to learn about their craft. An even better engineer uses what other engineers have already discovered and shared with the world to further their understanding. If the world only consisted of the "even better" engineers things like this…
Also, having the "this is not a problem" attitude is a red flag; what else would this person not consider a problem when I hire them?
Re: How I Embarrassed Myself in My Interview With Google
#25If im ever being interviewed by Google, i'm going to say "hold up let me google the solution to that real quick." A good engineer spends about 95% of their time discovering new things to learn about their craft. An even better engineer uses what other engineers have already discovered and shared with the world to further their understanding. If the world only consisted of the "even better" engineers things like this…
Re: How I Embarrassed Myself in My Interview With Google
#26Earlier quoted context omitted.
Do you have any open source projects? The first thing i'm looking for as a developer when I visit your websites is a link to any code you have written. Which as far as I can tell doesnt exist? A programmer without a portfolio of source code is like a painter without a portfolio paintings. I assume Google scouts are usually looking to hook the exceptionally rare "Monet" and "Picaso" software engineers swimming around…
As a Google Engineer, I can assure you that nobody who interviews you will give a damn about your code in github. Unless you're James Gosling or someone at that level. (But then again I don't think they interviewed James Gosling in the same way they interviewed me, so the point is moot.) Google interviewers are interested in how well you can code (or design a solution) in a whiteboard for 45 minutes. I'm not claiming…
Re: How I Embarrassed Myself in My Interview With Google
#27If im ever being interviewed by Google, i'm going to say "hold up let me google the solution to that real quick." A good engineer spends about 95% of their time discovering new things to learn about their craft. An even better engineer uses what other engineers have already discovered and shared with the world to further their understanding. If the world only consisted of the "even better" engineers things like this…
I really can't get behind this kind of thinking. If you can't do what came before, how you plan on advancing the state of the art? Knowledge is hierarchical, one cannot get by forever by just googling the answer to everything if you're expected to be pushing new boundaries. Testing if you know the fundamentals is legitimate, even if there's already a million implementations of them on the web.
Re: How I Embarrassed Myself in My Interview With Google
#28Earlier quoted context omitted.
I really can't get behind this kind of thinking. If you can't do what came before, how you plan on advancing the state of the art? Knowledge is hierarchical, one cannot get by forever by just googling the answer to everything if you're expected to be pushing new boundaries. Testing if you know the fundamentals is legitimate, even if there's already a million implementations of them on the web.
[deleted]
Re: How I Embarrassed Myself in My Interview With Google
#29Earlier quoted context omitted.
[deleted]
Now you're just responding to an entirely different argument that no one is making.
Thanks for the reply.
Re: How I Embarrassed Myself in My Interview With Google
#30People who reject physical reality should receive a bit of negative conditioning about doing so...