Your question is Browser Request Flow. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
What happens when you type google.com into a browser?
Asked in the Technical Interview stage. The interviewer wanted to explore the request path down to kernel syscalls. Explain the sequence from parsing the address through DNS resolution, connection establishment, encryption, HTTP exchange, response processing, and rendering.
Whether you can connect browser behavior to operating-system networking, including sockets and kernel-managed I/O. The interviewer is also checking that you distinguish DNS, TCP or QUIC, TLS, HTTP, and browser rendering rather than treating the operation as one network request.
Discuss a modern desktop browser and typical HTTPS behavior, including relevant alternatives such as cached DNS, HTTP/2, and HTTP/3.