Questions entretien chez Google

Candidature

J'ai postulé via une recommandation d'un employé. Le processus a pris 4 semaines. J'ai passé un entretien à Google (Mountain View, CA (États-Unis)) en avril 2014.

Entretien

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

Candidature

J'ai postulé via un établissement de l'enseignement supérieur ou universitaire.. Le processus a pris 2 semaines. J'ai passé un entretien à Google en avril 2015.

Entretien

Phone interview:
The Interviewer was late for 20 mins... Ask nothing on my resume.
Tow questions:
1) A string consists of ‘0’, ‘1’ and '?'. The question mark can be either '0' or '1'. Find all possible combinations for a string.
2) Give you a text file, remove duplicated lines.
    Follow up: If the file is very large, general hash map takes too much spaces, come up with a better solution.

Entretien

Industry standard. You pretty much have to be perfect on these. Got one un-optimized at the start of the day and it turned out to be the one that got me denied.

Candidature

J'ai postulé en ligne. J'ai passé un entretien à Google.

Entretien

Basic big tech software interview - algorithms focused on sorting, searching, and graphs. First two interview rounds were easier, the third interview was tougher. The process greatly depends on the engineer that is interviewing you unfortunately. I had one really great interviewer who I got along well with, another that was alright, and one that I had difficulty communicating with.

Entretien

Hard questions, but they were easy to talk to. Come prepared with questions. Come with points to talk about that is not on resume. Only made it to the second interview.

Entretien

I submitted my resume for another position, but then they reached out for the recruiting assistant role which was nice. I had a screener interview then a follow-up interview. I believe the whole process was supposed to be 3 interviews. The second interview was more of a challenge than I expected.

Entretien

Phone screening, first round, then virtual onsite. Went through product design, product strategy, analytics, and engineering. First round was a phone call and virtual onsite was a set of 5 interviews done over Google hangouts.

Candidature

J'ai postulé en ligne. J'ai passé un entretien à Google.

Entretien

Vet easy, standard questions. Because of covid, the interviews were all virtual. I wasn't prepared because I didn't tea want to leave my current company. It would be piece of cake for a well prepared candidate.

Entretien

the interview process was complicated and had multiple parts, need to study a lot to get pass it, it involved multiple questions from leetcode and some of them were hard difficulty

Entretien

The recruiter and interviewer are really nice persons. But the interview problems are hard to me. I still need to work harder to pass through the interview. The recruiter and interviewer are really nice persons. But the interview problems are hard to me. I still need to work harder to pass through the interview.