I wonder. I've done a bunch of interviews and will tailor basic questions based on the resume. If they claim to understand networking, I'll ask them a basic "what is ping?" then progress to something like "what does arp do?" Then maybe a tricky, "whats the difference between a timeout and route unavailable error when pinging a host" And hit other topics. I wonder if this is too quizzy?
If it's about Bash, then basic questions about variables, exit statuses and such are asked. Surprisingly, so many people's resume accomplishments don't line up with what I'd imagine would be the type of knowledge they should/would carry based on the accomplishment.
If the candidate is out of college, then I am a bit more forgiving since I wouldn't expect them to know the intricacies of certain software stacks, but for someone working with something for 2-3 years can't really explain what they put on their resume, it's a big red flag and plays a very large part in disqualifying the person based on their technical merit alone even without getting to the "does this person play well with others" aspect of interviewing.
Your approach is pretty much standard practice in the engineering world. People in this industry like to claim that answers to those kind of questions can be faked, but you can't fake depth. At some point, if you know what you are doing[1], you will make them look like an idiot if they have been lying.
[1] If you don't know what you are doing, you have no business giving an interview. That's another big problem this industry has.
I'm glad to know I'm not the only one that does this. I'd say my results echo yours. I had one candidate with a resume that bragged about years of shell scripting experience. When I asked the trivial question of "What is your favorite shell?" he gave a panicked-deer-in-the-headlights look and muttered something about Ubuntu.
Phew. Glad to know that I'm not the only one dealing with bullshitters on resumes.
I noticed that the recruiting firm that got me my current job is that the candidates that they send aren't that great. I only met this firm because a friend passed the gig on to me. They just send anyone and hope that someone sticks. But once they find someone that sticks and is doing well, they keep on coming back once the headhunting contract limits are off.
If it's about Bash, then basic questions about variables, exit statuses and such are asked. Surprisingly, so many people's resume accomplishments don't line up with what I'd imagine would be the type of knowledge they should/would carry based on the accomplishment.
If the candidate is out of college, then I am a bit more forgiving since I wouldn't expect them to know the intricacies of certain software stacks, but for someone working with something for 2-3 years can't really explain what they put on their resume, it's a big red flag and plays a very large part in disqualifying the person based on their technical merit alone even without getting to the "does this person play well with others" aspect of interviewing.