If google didn't exist, I would have a completely different approach to doing my job. I am really, really good at finding what I need with google. From diagnosing and fixing some of my own medical problems, to engineering projects, to code, to financial stuff, google is my primary resource. I use google to find programming books on amazon, which will supplement google. Books are often useful to gain a good overview of a subject when depth is needed.
If you aren't an idiot, you won't blindly pick the first answer that comes your way unless it is right. Often it takes several iterations of refining search terms, analyzing why your code breaks, etc to come across the right answer. And if the source comes from someone who has a bajillion posts and lots of rep points on whatever forum you've googled, chances are it's good information. A lot of factors come into it.
I'm always researching or learning something. I learn so many different things, quickly, and in a reasonable degree of depth (my major was in engineering, so in many cases programming is a means to an end, not the end) that I find it difficult to remember the specifics of any given language. So sue me. I don't have a favorite language, just languages I use for particular problems.
And I quickly forget the syntax. I remember the syntax by looking at my code, or if I can't find it or I'm starting out, by googling. e.g. If I'm scripting in bash, I will have the Advanced Bash Scripting Guide or whatever it's called open, and just click to loops, conditionals, functions, or whatever. The important thing is that I know what I want to do and how to do it.
As a result, I've done some pretty cool things in a variety of different languages. But I don't waste my mental cache on remembering syntax. I certainly know the difference between a for loop and a while loop though. I know data structures, or at least I know where to look them up if it has been a while. I know what non-normalized tables in a database look like (but I will refresh before doing a database related project). I know that if I have a heavy text parsing project, Perl is a good choice. For databases, it's PostgreSQL. For typical systems administration stuff, bash or sh is good.
These are the "take home" messages I have internalized. As far as remembering syntax, I don't. It's absorb, purge, absorb, purge, absorb purge. I must have taught myself regular expressions and then forgotten specifics about a dozen times by now. There are far more important things to dedicate to your mental HDD to than language syntax, IMO. Syntax is arbitrary. Every language has a different one.
Of course, I know the commercial reality expressed by foreyez in his answer and that's just life. I would approach a job interview the same way he does, bone up for that, and meanwhile be able to point to what I've accomplished and my references. What I do works for me. I bet it works for many others.