- Plus récents
- Plus anciens
- Plus faciles
- Plus difficiles
Entretiens chez Google
Entretiens pour les meilleurs postes chez Google
- Software Engineer (4762)
- Software Engineer(Internship) (595)
- Product Manager (520)
- Intern (444)
- Software Developer (337)
- Associate Account Strategist (249)
- Senior Software Engineer (228)
- Account Strategist (228)
- Account Manager (218)
- Software Engineering (180)
- Software Development Engineer (157)
- Software Engineer New Grad (157)
- Program Manager (151)
- STEP Intern (147)
- Analyst (138)
- Software Engineer Intern (137)
- Technical Program Manager (135)
- Internship (129)
- Engineering Practicum (129)
- Site Reliability Engineer (122)
- Associate Product Manager (122)
- SWE Intern (122)
- Data Scientist (108)
- Software Development Engineer (SDE) (107)
- Data Analyst (93)
- Software Engineering Intern (92)
- Business Analyst (86)
- Financial Analyst (85)
- Quantitative Analyst (84)
- Project Manager (83)
Employé anonyme, Auburndale, FL
J'ai postulé via la recommandation d'un employé. J'ai passé un entretien chez Google (Auburndale, FL) en avr. 2014
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."
Candidat anonyme à un entretien, Londres, Angleterre
J'ai postulé via un établissement d'enseignement supérieur ou universitaire. J'ai passé un entretien chez Google (Londres, Angleterre)
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.
- Why are you leaving your current job
Candidat à l'entretien anonyme
J'ai passé un entretien chez Google
A few rounds of interview full of cognitive test, must go through several interviews and there is a technical questions during the interview . Need to be prepared for the interview
- Technical questions and cognitive test
Employé anonyme, Londres, Angleterre
J'ai passé un entretien chez Google (Londres, Angleterre)
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.
- How do you hire 100 engineers?
Candidat anonyme à un entretien, Mountain View, CA
J'ai passé un entretien chez Google (Mountain View, CA)
You first have a phone screener with a recruiter. They get your general experience and background. The recuriter explained that the process included three additional interviews with associates and managers on the team. It seemed fairly straightforward.
- They asked about experience then had some additional questions about google products
Employé anonyme, New York, NY
J'ai postulé en ligne. J'ai passé un entretien chez Google (New York, NY)
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.
- Please explain a challenging time at work and how did you handle it
Candidat à l'entretien anonyme
J'ai passé un entretien chez Google
it was hard. first I had behavioral then I went to the coding round which consisted of some leetcode hard. Did not hear back after the interview. Whole process was nice and easy though
- Why should I hire you?
Candidat anonyme à un entretien, Waterloo, ON
J'ai passé un entretien chez Google (Waterloo, ON)
Interview process was pretty fast. The recruiter was pretty co operative. Initially asked a couple verifying questions before asking me for a date to schedule a phone interview. I had the phone interview scheduled and got response back in a week.
- Asked a dynamic programming question.
Candidat anonyme à un entretien, San Jose, CA
J'ai passé un entretien chez Google (San Jose, CA)
1. Recruiter screening 2. Phone interview with fellow product manager. Went through a general intro and then a product sense question. 3. Recruiter follow up with results and next steps 4. On-site with 5 interviews and 1 lunch meeting 5. Offer to interview again in 6-9 months
- Name your favorite product and how you would improve it. Lots of estimation questions in onsite. Lots of pie in sky questions about how to improve certain products.
Candidat anonyme à un entretien, Ann Arbor, MI
J'ai passé un entretien chez Google (Ann Arbor, MI)
The process was very smooth. This was last year. I was further along with another company which is why I ended after the first interview. Nice interviewer. Overall good experience.
- Tell me about something yourself?