Preguntas de entrevista para Google

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."

After initial coding interview, got notified that there was a hiring freeze so there would be delays in communication. Never heard back ever since. It has been over 4 months

Overall positive interview experience. Interviewers were friendly and knowledgeable. Questions were challenging but fair. I felt valued and respected throughout the process. Overall positive interview experience. Interviewers were friendly and knowledgeable. Questions were challenging but fair. I felt valued and respected throughout the process.

the interview process asked about specific algorithm questions that are relevant to what the candidate listed on his or her resume. it can be combinatorics or graph related problems, for instance.

The process was clear and consisted of 3 interviews. It also contained a business case study at the end. All in all it was one of the more pleasant processes

all the asked question were leetcode medium and were doable. Some questions required thinking and the interviewer helped during that time. Overall a pleasant interview. Needs some preparation but can definitely be cleared

Very structured process, several interviews with at least two people each time. Coding challenges, white board, behavioural interviews. Plenty of détailled feedback after each and every interview. You need to be prepared to ask good questions.

Contract role. 1 main interview meet 2 interviewers individually. Simple process. Quick turnaround. They want to know how you problem solve. They will also ask behavioural and hypothetical questions. Very positive interview experience and interviewers make you feel comfortable.

It is comprised of behavioral interview. They also would want to see your creative side by asking you some hypothetical question and the approach you are taking to answer the question.

Fine -- typical for a big company. Phone screen, one on ones, panel. Nothing out of the ordinary. I didn't make it all the way to panel or i'd give a more detailed review on that aspect of it.