I had to look it up, once I did, I knew exactly what you were talking about, I just didn't know it by name. I was thinking about the process a request/response

I had to look it up, once I did, I knew exactly what you were talking about, I just didn't know it by name. I was thinking about the process a request/response goes through via TCP/IP port. I've been doing this for 20 years. Maybe you need to rethink your interview questions. You are just testing for word/definition association which doesn't really matter outside of tech chest pumping. Perhaps explain what a call stack is, then ask why it's important and how it's used for debugging, etc. You shouldn't care so much about the what but rather the why. I remember an old Delphi interview where they asked me what a I already forgot was. I didn't know by name, but once they showed me what they were talking about, I could explain it in depth. They ended up hiring me and I fixed their broken DSS engine and it ended up in a lucrative M&A. Anyway, standard IQ tests have sections for various skills. Among the ones that are important for programming is abstract thinking and pattern recognition. You should be testing for that rather that word/definition association. http://www.thinktonight.com/WISC_IV_subtests_s/331.htm http://www.thinktonight.com/WISC_IV_subtests_s/331.htm