To use our Doctor simile, you wouldn't ask about anatomy (or only briefly), you ask about diagnosing and treating ailments; that's what you are paying the perso

To use our Doctor simile, you wouldn't ask about anatomy (or only briefly), you ask about diagnosing and treating ailments; that's what you are paying the person to do. For technical interviews, you don't ask them about Computer Science things (or only briefly), you ask them about real-world software development; that's what you are paying them to do. The stuff they really don't go over in CompSci classes. What was the project you were most proud of and why? What was the hardest project for you and why? What are some of the ways you've connected to a database / datastore (if applicable)? What were some database design decisions you've grappled over? What designs were you considering? What's the most impressive code you've seen written by someone else and why? Tell me about how you organized classes in a particular project and why you did it that way. Describe a way you've organized your classes and wish you had done it another way, and why. How do you make sure if your software has a problem, you know about it and can figure it out quickly? What's the hardest software you've written and why? How do you handle disagreements with a colleague? Can you site an example of a disagreement and each person's reasoning? Notice almost all of those examples asked "why." That's the most important part. If someone isn't up to par, they will do one of two things: 1. Answer Briefly. 2. Babble on to the point it's obvious they don't know what they are talking about. #1 of course can be because the person is shy or intimidated or an extreme introvert, but not likely. Because you're talking about a subject they should feel extremely comfortable about, even introverts will come out of their shell.