One of my best interview experiences was when I was asked a few relatively simple questions, looked over a class of their code and describe what it does and som

One of my best interview experiences was when I was asked a few relatively simple questions, looked over a class of their code and describe what it does and some mistakes that might be in there, and went over a code sample I brought in. Then he said, "Okay, I know you can do the job, now I'm just curious how much you really know." And then the really hard, low level questions came out. I said I didn't know a few times, and struggled even when I sorta knew the answers, and he took it in stride and played the role of teacher and taught me a few things that I still remember today. I didn't feel pressure like I did in other interviews, despite being much harder questions than I get asked elsewhere. If you do it that way, I'm cool with it. If you start right out the gate with the hard questions, and you make no indication that you're not expecting right answers, I have no choice but to assume I better get them right, or else (especially considering I haven't moved on to the next stage of interviews before for getting one question wrong, or saying I didn't know for one of the questions, or the HR person was looking for a particular keyword I didn't say, quite a few times).