4 ms·

I like the one where you ask the person to explain “what happens between when you type an address in a browser until you get something to show up” in as much de

by tucaz 3y ago

I like the one where you ask the person to explain “what happens between when you type an address in a browser until you get something to show up” in as much details they can. It tells you a lot about people understand all the different concepts involving computing.

brezelgoring 3y ago
I did this as an exercise just now, and I noticed I answered mostly in networking terms. Sockets, ports, explaining what an autonomous system is and how DNS requests flow between them, explaining a TLS handshake, and HTTP and HTML and what a server is, and how it works, there's always more to cover. I realized I know very little of what happens _inside_ the computer during the typing, what libraries are involved? How does data flow _inside_ the computer? I like to think I know enough about my hardware, but this has been humbling. Thank you for bringing this up.
loveparade 3y ago
This is a great one!
2rsf 3y ago
Good one, it can also show you how people thinks and not only knowledge, for example how organized are they
codingdave 3y ago
I tend to ask this type of question as well. Not only does it show you the level of detail they know, but it also show you how well they filter that knowledge to the situation and audience. I'd expect someone being hired for a networking role to talk more about the networking and DNS, while someone begin hired for a front-end role would talk more about the content that is sent and returned to the browser, and a back-end or full-stack dev to talk about how the destination server handles the request and builds a response. Even better if they ask a clarifying question to confirm which pieces I really want to hear about.
comprev 3y ago
This is always my favourite question to ask as their answer tells me exactly where their knowledge is strongest and thus would the candidate be suited to the role - or get bored very quickly and I'd be back to square one for hiring in 12 months time?

by tucaz 3y ago

brezelgoring 3y ago

I did this as an exercise just now, and I noticed I answered mostly in networking terms. Sockets, ports, explaining what an autonomous system is and how DNS requests flow between them, explaining a TLS handshake, and HTTP and HTML and what a server is, and how it works, there's always more to cover. I realized I know very little of what happens _inside_ the computer during the typing, what libraries are involved? How does data flow _inside_ the computer? I like to think I know enough about my hardware, but this has been humbling. Thank you for bringing this up.

loveparade 3y ago

This is a great one!

2rsf 3y ago

Good one, it can also show you how people thinks and not only knowledge, for example how organized are they

codingdave 3y ago

I tend to ask this type of question as well. Not only does it show you the level of detail they know, but it also show you how well they filter that knowledge to the situation and audience. I'd expect someone being hired for a networking role to talk more about the networking and DNS, while someone begin hired for a front-end role would talk more about the content that is sent and returned to the browser, and a back-end or full-stack dev to talk about how the destination server handles the request and builds a response. Even better if they ask a clarifying question to confirm which pieces I really want to hear about.

comprev 3y ago

This is always my favourite question to ask as their answer tells me exactly where their knowledge is strongest and thus would the candidate be suited to the role - or get bored very quickly and I'd be back to square one for hiring in 12 months time?