Google's “Director of Engineering” Hiring Test

Re:Google's “Director of Engineering” Hiring Test by seanp2k2 on Friday October 14, 2016 @04:43AM (#12706821)

GET / HTTP/1.1\r\n and some kind of sensible response is not too much to expect someone to know. HTTP is super easy and I see the HTTP transaction test as "did you ever get curious as to how exactly a core part of the current Internet actually works". I'm sure that there are app developers out there who can spin crud stuff all day and have no idea about this, just as there are curious people who couldn't stand up todomvc to save their life, but in general, all of the most talented people I've worked with knew their stuff front to back, and had at least a few areas of expertise.

CGI is also cool to learn about the workings of, since it almost seems too simple.

[ Parent | on HN ]

Re:Google's “Director of Engineering” Hiring Test by aninhumer on Friday October 14, 2016 @09:22AM (#12707866)

> I see the HTTP transaction test as "did you ever get curious as to how exactly a core part of the current Internet actually works".

Sure I did.

Then I forgot most of the details because they didn't matter, and I knew I could look them up quickly if I ever needed to write a HTTP client/server for some reason.

[ Parent | on HN ]

Re:Google's “Director of Engineering” Hiring Test by ninkendo on Friday October 14, 2016 @12:36PM (#12709227)

You would've gotten it wrong though!

You need two newlines to finis the request, plus the HTTP 1.1 standard requires clients to send a Host: header for all requests.

Not saying every interviewer would care about that in an early screening process.

[ Parent | on HN ]

Re:Google's “Director of Engineering” Hiring Test by dekhn on Friday October 14, 2016 @09:49AM (#12708028)

if you answer "GET / HTTP/1.1\r\n" I'm going to ask you if you left anything out.

Because you did: after that you have to provide a Host: <hostname>.

[ Parent | on HN ]