10 questions you’ll have to answer if you want to be an engineer at Google

google1
google1

Working for a company like Google is really fun, isn’t it? But first, you have to clear the interview.

Pierre Gauthier – Computer Engineer Who applied for director of engineering role at the company was asked some intimidating questions in a phone interview by the company.

Unfortunately, he didn’t pass the Google’s interview and decided to create a Blog Gwan.com and in a post at Gwan shared his experience.

Gauthier managed to answer first four question correctly, it was all downhill from there. He soon found himself arguing on his answers with recruiter and by the 9th question frustratedly he asked, “What’s the point of this test?”

So, if you receive a call for an interview from Google you should know the answer to these 10 questions

10What is the opposite function of malloc() in C?

9What Unix function lets a socket receive connections?

8How many bytes are necessary to store a MAC address?

7Sort the time taken by CPU register read, disk seeks, context switch, system memory read.

6What is a Linux inode?

5What Linux function takes a path and returns an inode?

4What is the name of the KILL signal?

3Why Quicksort is the best sorting method?

2There’s an array of 10,000 16-bit values, how do you count the bits most efficiently?

1What is the type of the packets exchanged to establish a TCP connection?

If you think Gauthier was properly qualified for position but he began his post by summarizing his experience:

For the sake of the discussion, I started coding 37 years ago (I was 11 years old) and never stopped since then. Beyond having been appointed as R&D Director 24 years ago (I was 24 years old), among (many) other works, I have since then designed and implemented the most demanding parts of TWD’s R&D projects…

If you think I’ve missed something or you want to add a new comment below