|
|
|
|
|
|
by grog454
1504 days ago
|
|
|
If I was given this question my first inclination would be to ask what your current understanding of the process is and you want to know. If that didn't help, I'd start with the absolute highest level "the google.com website loads in the area below the address bar" and then I'd be back to "what else do you want to know?". Hopefully that would be enough for you to start narrowing in (what does "load" mean and how does that work?). Opening with DNS, HTTPS, TCP, etc. could end up being a complete waste of time depending on what signals your looking for, what you're really asking, and your background. I'm curious how my responses would be interpreted by you as someone who's asked questions like this before? |
|
|
Like, my goal isn't to see how much of a spiel you've rehearsed for a finite set of possible interview questions.
That sort of exercise constitutes a useless hazing ritual that selects for people with low anxiety at the moment, not aptitude with the relevant technologies for the job.
I'm going to keep pushing the conversation along until you've either hit the depth of your knowledge and say "I'm not sure", or we need to move onto other questions. If we hit your depth early but we're headed into an interesting direction, I might ask, "How would you build [protocol or feature you're not sure about]?" This potentially gives useful data in how you, as a candidate, approach abstract problems.
But I should also note: I'm an introvert. I'm shy. I get nervous easily in social situations. I'm not the best interviewer, and I don't believe the processes I learned from my employers are necessarily the right way to hire technical expertise. I would rather replace the interview with timeboxed work-sample tests. But I don't call those shots.