I've done more interviews over the last two years than I'd like, and honestly - I have no problem with folks googling "how do I solve X in language Y". Frankly

I've done more interviews over the last two years than I'd like, and honestly - I have no problem with folks googling "how do I solve X in language Y". Frankly, we tell folks up front - "This is not a memory test, please feel free to ask questions, use google/stack overflow/man-pages/etc." I'm in the interview to give you a problem that looks as close as possible to the work we're going to ask you to do, and then discuss with you how you solved that problem. If you copy from stack overflow and it works, great! Now we can talk about possible edge cases, performance issues, testing, add a new requirement, etc. I don't really care how you get the code into the file, or where it comes from - I care that you understand it, and can think through how that code will perform in different situations. Most importantly of all - I care that you can tell me that information in a coherent fashion.