Google Interview Questions

Direct onsite because I interviewed in the past and did well that time. From the time I sent my resume to interview day: 2 weeks. From interview day to offer over the phone: 2 weeks. The syllabus for the interviews is very clear and simple: 1) Dynamic Programming 2) Super recursion (permutation, combination,...2^n, m^n, n!...etc. type of program. (NP hard, NP programs) 3) Probability related programs 4) Graphs: BFS/DFS are usually enough 5) All basic data structures from Arrays/Lists to circular queues, BSTs, Hash tables, B-Trees, and Red-Black trees, and all basic algorithms like sorting, binary search, median,... 6) Problem solving ability at a level similar to TopCoder Division 1, 250 points. If you can consistently solve these, then you are almost sure to get in with 2-weeks brush up. 7) Review all old interview questions in Glassdoor to get a feel. If you can solve 95% of them at home (including coding them up quickly and testing them out in a debugger + editor setup), you are in good shape. 8) Practice coding--write often and write a lot. If you can think of a solution, you should be able to code it easily...without much thought. 9) Very good to have for design interview: distributed systems knowledge and practical experience. 10) Good understanding of basic discrete math, computer architecture, basic math. 11) Coursera courses and assignments give a lot of what you need to know. 12) Note that all the above except the first 2 are useful in "real life" programming too! Interview 1: Graph related question and super recursion Interview 2: Design discussion involving a distributed system with writes/reads going on at different sites in parallel. Interview 3: Array and Tree related questions Interview 4: Designing a simple class to do something. Not hard, but not easy either. You need to know basic data structures very well to consider different designs and trade-offs. Interview 5: Dynamic programming, Computer architecture and low level perf. enhancement question which requires knowledge of Trees, binary search, etc. At the end, I wasn't tired and rather enjoyed the discussions. I think the key was long term preparation and time spent doing topcoder for several years (on and off as I enjoy solving the problems). Conclusion: "It's not the best who win the race; it's the best prepared who win it."

I was contacted by a recruiter (vendor supporting google) after applying for a job at Careers website. I asked the level for which I would be interviewing. The recruiter said that Google would do team matching but did not specify the level. The phone interview was setup and I attended the phone interview. I did not receive any communication from the recruiter for a week after which I followed up. The recruiter replied saying that I performed well but the position is closed. After contacting recruiters through LinkedIn, one of the recruiters (seemed working at Google) responded and proceeded with Onsite interview. During initial call with this recruiter, the recruiter mentioned that she helped several people to get jobs during her term with Google. I think she was paid to perform that role at Google. That is not help. Except one interviewer, I think other interviewers were fine. In one of the interviews, I confirmed a clarification with the interviewer. While I was coding another method, the interviewer said changed that clarification. I told him that I clarified with him earlier but he did not confirm that nor did he apologize. When I used Java character as index, he asked me why I am using it. I told him that it would work. He again asked the same question. When I mentioned this to the recruiter, the recruiter said it is just miscommunication. Is it right if an interviewer does something wrong?

I had to go the extra mile and put in additional effort, only to face rejection in the end. It was a challenging experience filled with numerous obstacles, particularly related to trees. The tree problems I encountered were no walk in the park; they were quite difficult to overcome.

- Task submission asked in advance (test) - Starts with a short interview about your background and then straight to the submitted test. - Multiple interviewers online and face to face ( from friendly and nice to semi-negative/aggressive interaction --- testing yourstress levels) - Team presentation/office tour - End of interview - Teeshirt and very friendly goodbye chat

it was really long but interesting. i learned a lot. i didn’t get it. it was quite a long process. I don’t know what else to say other than it was okay.

Typical interview, had to do 2 questions. The first I would describe as a Leetcode easy, then a follow-up question that slightly changed the problem to be more like a Leetcode medium.

round 1 : Hard-medium leetcode question round 2 : Hard-medium leetcode question round 3 : Hard-medium leetcode question Didn't get an offer. Did well in 1 round, average in 2nd round and didn't do well in 3rd round

It was smooth. Nothing too crazy. First interview with the recruiter. Questions came from a bank and after 20’ talking I was told that we will be moving to the next stage.

it's a multiple-stage process. The stages mainly comprise job interviews held either one-on-one. call with recruiter one on one, call with hiring manager one on one, assignment to be done on my own time, and then presenting it to the team

Outstanding company! From start to finish, their impeccable service, high-quality products, and knowledgeable team impressed me. They went above and beyond to ensure my satisfaction. I wholeheartedly recommend them for an exceptional experience