[deleted]
“What happens when you type Google.com into your browser and press enter?”
81–90 of 136 posts
Re: “What happens when you type Google.com into your browser and press enter?”
#82[deleted]
It's pretty common to fail someone out at that point. If you wanted to be charitable you could try to ask them questions as much like homework questions from university as possible. "Write out in [psuedo] code how you would add two numbers and display the result on the screen using system interrupts" or something. You may have to pay the ultimate price and be stuck working with the person after that, though.
Re: “What happens when you type Google.com into your browser and press enter?”
#83Love it! One of my favourite bad interview questions. I got asked this in an interview ~5 years ago. My response was to look shocked... Pause. Then ask: "What do you mean? What detail do you need? DNS? SYN / ACK? HTTP?" At the point I started talking about syn/acks they just cut me off and moved on to the next question. Same company (different person) started the phone screen with 'oh so your CV says you know linux,…
That's part of the point of the question - which part you go into detail on is a pretty good indication where your strengths lie. Someone who spends a lot of time on DNS and SYN/ACK is probably a low-level networking guru, and the rest of the interview should be structured accordingly. Someone who immediately jumps into HTTP requests, HTML parsing, and stylesheet application is probably a web developer, and the rest…
At least in my line of work, the big gist of that question is: "Can this person summarize a technical issue in a comprehensible way for the audience? e.g. So that it could be passed through various sales teams and project managers, but is still sensible when it lands in the client engineer's inbox?"
The correct answer starts along the lines of "How hard should I geek out?"
Re: “What happens when you type Google.com into your browser and press enter?”
#84Earlier quoted context omitted.
That's part of the point of the question - which part you go into detail on is a pretty good indication where your strengths lie. Someone who spends a lot of time on DNS and SYN/ACK is probably a low-level networking guru, and the rest of the interview should be structured accordingly. Someone who immediately jumps into HTTP requests, HTML parsing, and stylesheet application is probably a web developer, and the rest…
At least in my line of work, the big gist of that question is: "Can this person summarize a technical issue in a comprehensible way for the audience? e.g. So that it could be passed through various sales teams and project managers, but is still sensible when it lands in the client engineer's inbox?" The correct answer starts along the lines of "How hard should I geek out?"
If your interview question has a correct answer, it's probably the wrong question.
Re: “What happens when you type Google.com into your browser and press enter?”
#85Earlier quoted context omitted.
I'm not so sure it's a bad interview question. Or rather, perhaps it's only bad if you, as the interviewer, have a specific answer in mind. We used it once with the caveat that "there's no right answer, we don't really know every step either, lets see what happens". We collaborated with them, it was great, and by the end of the conversation were pretty certain we wanted to keep the conversation going by hiring them.…
> it's only bad if you, as the interviewer, have a specific answer in mind. This is true of all interview questions. The goal is to get a sense of how a candidate thinks about things and works through problems. Asking a sequence of clarifying questions is a huge part of that, and very similar to the process of requirements gathering in day to day work.
This question is better than the cliched "bad" interview question because the answer is actually relevant to a software engineer's work.
Re: “What happens when you type Google.com into your browser and press enter?”
#86Earlier quoted context omitted.
At least in my line of work, the big gist of that question is: "Can this person summarize a technical issue in a comprehensible way for the audience? e.g. So that it could be passed through various sales teams and project managers, but is still sensible when it lands in the client engineer's inbox?" The correct answer starts along the lines of "How hard should I geek out?"
If your interview question has a correct answer, it's probably the wrong question.
It's quite acceptable - often a good idea - for the correct answer to a question to be another question.
Re: “What happens when you type Google.com into your browser and press enter?”
#87Lots of interesting things happen in between your computer and Google's servers - like ISPs exchanging routing information using BGP, so the routers can determine a route through each different AS (provider/transit network) it has to go through to actually Fong the machine with that IP, and the kinds of physical and data layers it goes through (cable or DSL, fibre, and Ethernet, SONET/SDH, maybe tunnelling over MPLS…
Is Fonging a thing, or typo? :)
This is a question everyone has to Fong out themselves.
Re: “What happens when you type Google.com into your browser and press enter?”
#88the time-to-live value for a datagram reaches zero at which point the packet is dropped Someone should write a Victorian-style novel on the hard, short, but virutous life of a packet.
Or a multilevel story-within-a-story type where the browser tells the HTTP server a story about an OS who tells a story about keyboard interrupts and network packets and so on.
Re: “What happens when you type Google.com into your browser and press enter?”
#89Earlier quoted context omitted.
> That's part of the point of the question - which part you go into detail on is a pretty good indication where your strengths lie. Someone who spends a lot of time on DNS and SYN/ACK is probably a low-level networking guru, and the rest of the interview should be structured accordingly. Hmm, interesting, I had not thought of it that way. I'd probably start talking about the debouncing logic in the keyboard microcont…
I sat in on someone who gave this question an half hour treatment on all levels. Lots to learn.
[deleted]
Re: “What happens when you type Google.com into your browser and press enter?”
#90I would really like to know what happens when Im driving down a highway at say 60mph and browsing the web on my smartphone (or well let's say my wife is doing the driving and Im browsing the web :-) ). What kind of communication is happening between me and the cellphone towers? What data is my phone sending to the different cellphone towers as I drive by them? How does the cellphone tower send that data to the intern…
Like tinco said, above TCP/IP it's pretty much the same as on your desktop. If you want to know about TCP/IP and below, I suggest this title: "From GSM to LTE-Advanced: An Introduction to Mobile Networks and Mobile Broadband".
http://www.amazon.com/From-GSM-LTE-Advanced-Introduction-Bro...