Google Software Developer interview questions

I do take my NDA seriously, but in general terms: the interview questions at Google are extremely difficult and often very tricky. With that said, contrary to popular opinion, they are not necessarily any harder than the questions that any tech company with high standards would ask. Know your data structures and algorithms back to front; be prepared for questions as high-level as very general OOP design problems and as low-level as bit manipulations; and know your resume cold, because every interviewer was interested in at least one item on it. I HIGHLY recommend finding a copy of at least one coding interview book (Cracking the Coding Interview, Programming Interviews Exposed, and Design & Analysis of Algorithms served me well) and tackling the problems in it -- they will give you a good idea of what to expect. I will say that I had never seen any of the questions I was asked in my Google interviews (whereas the rest of the industry seems to recycle the same 20 questions over and over), but my practice with general interview-style coding questions was extremely useful nonetheless. Remember that the interviewer wants to see how you approach a problem you haven't necessarily seen before, so think out loud a lot, and don't forget your edge cases!

The question I can remember is explain how a TCP/IP connection is started at the protocol level. .