Google Interview Experience
Google Interview Experience
- Telephonic Interview
- Face to Face Interview and On-site interview.
- This interview was absolutely technical and directly to the point and he asked me several technical questions about Programming Languages from the beginning, and I really appreciated that, because it made me feel confident and motivated.
- Questions were logically linked and I could tell that the interviewer was actually enjoying the discussion that arose about different techniques to, for example, An engineer mainly has to be renowned with everything such as algorithms, data structures, programming, networking, distributed systems, scalable architecture, troubleshooting.
- After these questions he asked me where I would like to job. Second half of the interview had some basic technical queries, just to make confident I knew something. The queries which they asked were about Linux systems administration, algorithms, computer architecture and C programming.
- I made some sensible mistakes but he was satisfied and we planned the next phone interview. Before disconnecting the phone call, he advised me that it will be very technical and I should do really good preparation. I asked him to give me an ample of time for the practice and we planned for the next interview round.
- The second round of interview was very scientific and started with an algorithmic problem & queries about data structures, TCP protocol, security vulnerability associated with TCP, networking in general, and Google itself.
- After the second round of interview the engineer had to write opinion on me. It was cheering and I could move on to the next round of interviews.
- In this interview they asked very easy programming query and I had to do coding over phone. I was free to prefer the language and at last I had to question about DNS again, then HTTP protocol, routing, and TCP data transfer.
- The response was again positive and I could practice for the on-site interviews.
- In my last phonic interviewer I got to know that there will be five on-site interviews, each will be exactly of 45 minutes long.
- After two weeks, some official person sent me an email & congratulating me and inviting me to Gurgaon for an on-site round of interviews. Google pays for all expense, and books a hotel for you to stay overnight and they also offered to book a cab for me, but I preferred to take a Metro train from Delhi.
- Interviewer informed me I would have two more meeting now and he took me to lunch to one of Google's eating place and then I would have three other interviews.
- At 10:45am the first on-site interviews commence. It was about my earlier job experience.
- I had a lot of job knowledge in the past and I decided to tell about a physical security measures announcement system that I coded in C on Linux a few years before.
- In the last few times of the conference he asked me several basic Unix file-system queries.
- It was a coding session and begins with a trick query and not a real coding problem.
- I was asked to perform the solution in C. The solution was a mathematical expression that was a one-line return report.
- Then I was asked to write an implementation of a very well known data structure. While coding, I made a error and fail to remember to initialize part of a data structure .I would have observed the fault, but Google engineers are very serious and said to me don't ever make any error!
- After this interview I had a lunch by the engineer who interviewed me on the second phonic interview. She told me she was working at Google for two years and was very pleased about it.
- It was a networking conference and interviewers sketch a network figure on the whiteboard and had expected a problem in there.
- I had to ask a bunch of specific networking queries to locate the problem and he was pleased and in the last few minutes of the interview he inquired me some exact networking device query.
- I was asked to realize an easy string manipulation subroutine in either C or C++. I opt C.
- Unluckily I made an off-by-one fault there - the most common programming mistake in the history of mankind.
- Whole interview focused on this one problem.
- It was algorithms and data formation meeting and trouble presented here was related to the problem in the 2nd interview.
- Interview was very free-style and we talked back and forth about the problem. I reached at the correct solution near the end of the interview and he said that not several candidates get that far in the respond. I was glad.
- After that interview the engineer accompanied me out to the lobby and I took a cab back to my hotel. That's it!
Get High Salary Sector Jobs in Top MNC’s