Short Bytes: A computer engineer with 37 years of coding experience has written a blog post detailing all the questions Google asked him in an interview. He has also shared the answers he gave and how things went wrong. The questions asked during the interview will surely impress you.
Pierre Gauthier, a computer engineer who started coding 37 years ago and set up his own company 18 years ago, applied for a director of engineering post at the company. However, he failed to give the right answer to the Google recruiter.
So, he decided to write a Gwan.com blog post to share the tricky questions, his answers and his views regarding the whole process.
Gauthier writes that as the telephonic interview progressed, he got more amount of questions wrong. The fifth question he answered was first one he got wrong. Here’s his conversation that followed the question — What is a Linux inode?
Not satisfied with recruiter’s replies, Gauthier soon found himself arguing. By the ninth question, he frustratedly asked, “What’s the point of this test?”
Well, here are the 10 Google interview question asked by the recruiter:
1. What is the opposite function of malloc() in C?
2. What Unix function lets a socket receive connections?
3. How many bytes are necessary to store a MAC address?
4. Sort the time taken by: CPU register read, disk seek, context switch, system memory read.
5. What is a Linux inode?
6. What Linux function takes a path and returns an inode?
7. What is the name of the KILL signal?
8. Why Quicksort is the best sorting method?
9. There’s an array of 10,000 16-bit values, how do you count the bits most efficiently?
10. What is the type of the packets exchanged to establish a TCP connection?
At the end of his blog post, he jokes, “My score is four on ten, that’s better than my best Google pagerank** ever!”
For all the details and the answers given by him, you read the blog post on Gwan.com.
Did you find this article helpful? Don’t forget to drop your feedback in the comments section below.