The joke's on you if your interview process consists of asking googleable questions.
Asking "Define X" questions is a really bad proxy for assessing development skill. If you think developers are winging it by c'n'p--any interviewer who asks the candidate to produce a bunch of facts for an hour is the same, if not worse. You don't interview a classical pianist by asking him what notes are on the keyboard.
The questions are on an ascending scale - this weeds out the bad candidates early on. Things like keywords and syntax are easily Googlable sure, but people who really do this stuff every day will rattle through that section of e interview in 5 minutes.
Many years ago, I had a friend who was trying to schmooze her way into a development position hoping to "learn on the job." Anyway, she was stunned and even angry that she was asked technical questions during the initial phone interview.
Before hearing her story, I was skeptical that anyone tried to pull this crap. She's now in a field (marketing) where she can put her slyness to more use.
These days there's so much content around that some people in surprisingly senior positions can wing it, Googling some stuff then c'n'p, and slyly passing the rest to cow-orkers, at least for day-to-day tasks, and at least in the short term. Then one day everyone's busy and Jo(e) Faker has to do some real work.
But you've got to watch out. The very slyness that makes them do this will also get them promoted to management...