I took an online coding assignment containing two questions: one was easy, and the other was quite challenging.
Then, I was set up with an interview day, and I had four interviews: three technical and one behavioral.
I was told that the technical questions would focus on data structures and algorithms, but I was given one UI design question and two algorithmic questions.
Most of the questions weren't too difficult, but you are expected (like in most interviews) to find the best answer to the question.
The best thing about the interview is that you are not on your own to solve the problem; the interviewer also helps you work through the problem, and it is a good thing if you can show you can work with the interviewer.
You run a bank and have a set amount of money within the bank. Your goal is to maximize the number of transactions. However, you can skip the first x number of customers. After skipping, you must process the rest. You are given an array of customers and an integer value representing the amount of money you have.
The following metrics were computed from 1 interview experience for the Google early career software engineer role in San Diego, California.
Google's interview process for their early career software engineer roles in San Diego, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Google's early career software engineer interview process in San Diego, California.