> If im ever being interviewed by Google, i'm going to say "hold up let me google the solution to that real quick."

If Google just wanted people to take existing publicly known parts and hook them together, they would be recruiting people fresh out of community college instead of fresh out of masters and PhD programs, and they'd be offering around $50k/year salary.

Google is trying to find people who can create the parts that ordinary programmers hook together.

I can't hire IT in Chicago for $50k/yr.

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.

Now you're just responding to an entirely different argument that no one is making.

Deleted my comment because a) you were correct and b) I don't have time at the moment to completely rewrite my comment to express my thought on it in a cogent manner.

Thanks for the reply.

While you're not expected to be an encyclopedia of knowledge about any particular language, framework, or API; having the frequent need to look things up is a red flag because if you're always looking things up you may not move fast enough.

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?

you might miss out on a lot of bright bulbs if you keep red-flagging them because you think they won't move fast enough.

I may; hiring is tough. You only have a few minutes to gauge whether you'll work well with that person or not and bad signals are bad signals. I can't green light all candidates just in case.

It all depends on the tone and the body language and if they're able to continue with guidance.

Then you've turned the interview into a waste of time. There is no actionable information that is produced from that answer.

If you honestly are looking for a job and aren't looking to make some kind of F-U 2 The Man statement, do yourself a favor and don't give an answer like that.

This just seems silly to say.

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?