I second this. It's fun knowing where the interests and existing skills are. Do they talk about software, hardware, networking? Do they talk about CDNs and performance? Do they talk about the web servers and databases? Do they know how the browser makes the request, or what a request actually is? Do they mention load balancers, routing or DNS? Etc etc. And it's usually a fun conversation that could go on forever.
Or about how the browser interpret the answer? How and when are loaded css and js? Where is stored the information during the whole process? What about some eventual caching?
it never ends and most of the time even being the interviewer I discover new aspects of the question... :D
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I second this. It's fun knowing where the interests and existing skills are. Do they talk about software, hardware, networking? Do they talk about CDNs and performance? Do they talk about the web servers and databases? Do they know how the browser makes the request, or what a request actually is? Do they mention load balancers, routing or DNS? Etc etc. And it's usually a fun conversation that could go on forever.
Or about how the browser interpret the answer? How and when are loaded css and js? Where is stored the information during the whole process? What about some eventual caching?
it never ends and most of the time even being the interviewer I discover new aspects of the question... :D