Well, yeah.
When I see them claiming experience with any of the "cool" technologies, I usually throw them a couple questions related to Haskell[1], ocaml, Erlang, Lisp, 6502 assembly, etc. If they flub that area without acknowledging that it was a toy project, I'll know they are probably lying someone else. I'll be a lot more aggressive zoning in on the design and implementation of their most recent project. If they're soft, where I might normally give a little room for "nervous at interviews," they're pretty much done.
However, if they nail it, I know we're going to be able to work well together. Especially so if they get excited that someone is asking them about something...that...they'll...never...get...to...work...with...in...our...boring...IT...department.
sigh
[1] This one is almost too easy. "I hear these 'monad' things are really tough. What are they about?"
The point is not that schooling sucks, but that it isn't guaranteed, either.
As others have noted, what made me successful wasn't that I avoided the classroom. It was that my way of teaching myself was to actually program things. It gives the experience you need to lock in the knowledge you're gaining.