Way of Interview

1. "What is the hardest bug you've had to find and fix?"
2. Give ten pages of code and figure out the design
3. "What happens when you type http://www.google.com in a web browser address bar and press enter? You have 45 minutes, go as deep as you want with your explanation.
4. code something from scratch in 3 hours, then explain my design and solution
5. the best thing that they had created as a programmer
6. I will usually ask for code samples before the interview, or look at what they have at github
7. "what's in your feed reader" who do you follow?" and "how do you keep up to date?"
8. Make two armies fight each other and output the result. Introduce an element of randomness".
9. "What is your go-to language or the language that you are most proficient in?" and then "What would you change about <that language>?"
10. Write a function that takes a function and two ints and applies it to the two ints. 

------------------------------------------------------------------------------------------------------------

• "What is the hardest bug you've had to find and fix?"

1. When skydrive brand changed to onedirve and deployed to df, page does not get displayed
2. Multiple entries for single users in onedrive logs which cause data reporting invalid.

• Give ten pages of code and figure out the design
• "What happens when you type http://www.google.com in a web browser address bar and press enter? You have 45 minutes, go as deep as you want with your explanation.

1. You enter "facebook.com" into the address bar.

1. Browser resolves this to the numeric IP address (this can be cached by the OS or require a trip out to a DNS server).
2. Browser issues a "HTTP/GET" request. It passes along an HttpRequest which includes metadata about the browser, user preferences (like preferred language) and any stored cookies for that domain.
3. Facebook servers receive the request and their code begins to craft a response.
   1. Facebook will use the passed information including cookies to determine who the user is and what information to send back
4. A HTTP Response is returned from Facebook including a status line (200 OK, etc). Headers which include content-type, etc and the HTML body.
5. The browser receives the Response and begins to parse it for display.
   1. The HTML body will include links to CSS, JS and images. All of these will trigger additional calls back to servers to retrieve those bits
6. The browser layout engine will start to assemble the final page for display.
   1. CSS information may alter the layout and look of the page
   2. JS and DHTML may alter the layout of the page
7. The final page is assembled and rendered to the end user
8. http://igoro.com/archive/what-really-happens-when-you-navigate-to-a-url/

• code something from scratch in 3 hours, then explain my design and solution
• the best thing that they had created as a programmer
• I will usually ask for code samples before the interview, or look at what they have at github
• "what's in your feed reader" who do you follow?" and "how do you keep up to date?"
• Make two armies fight each other and output the result. Introduce an element of randomness".
• "What is your go-to language or the language that you are most proficient in?" and then "What would you change about <that language>?"
• Write a function that takes a function and two ints and applies it to the two ints.