If I ever get asked "What happens when you type a URL into the browser and hit enter" we are having an exciting journey via hardware interrupts, the kernel, display servers, toolkits and accessibility interfaces
Oh gosh I forgot about the scan matrix let's start there
This is *such* a terrible interview question
Honestly the best interview question I ever had was one asking me how to access a restricted resource for free, followed by how I'd stop myself from doing that. Covered a lot of technical understanding along with social approaches.
Anyway the reason I frame this as a terrible question is because what you're testing in some cases is the candidate's ability to sound smart about things you don't understand enough to evaluate their answer. It's way too broad a question, and it benefits self-confident candidates
Or, alternatively, you end up penalising a candidate because they answered outside the range you expected them to. In either case, don't ask a question unless you know the (full) answer!
