Recruiter sent out numerous interview guides to review before the interview that repeatedly said 'talk out loud'. Interviewers asked questions that had pretty obvious answers so I explained all the more obvious but less optimal solutions before touching on the optimal one. The interviewers spent a lot of time asking about why those weren't optimal and apparently reported this as if I had to be guided to a solution. For what may be the first time ever, I got interview feedback saying I got to the optimal solution but it took some guiding. In summary, I did what the interview prep asked me to do, explain my thought process. This was perceived as if I kept taking the wrong path to the solution.
Interview questions [1]
Question 1
Easy questions with obvious, cliche solutions like "use a binary tree" or "use a hash map"
I applied through a recruiter. The process took 1 week. I interviewed at Google (London, England) in Apr 2021
Interview
The screening round was a 45 minute interesting question. The interviewer was good and also provided hints. Overall a very positive experience.
I feel that face to face would have been better experience as remote interviews have their own challenges. It took me a while to figure out to switch to google doc rather than the video. Also my unfamiliarity with google meet resulted in wasted 5 mins at the start - did not realise that I had to press a button to start the meeting.
I applied through a recruiter. The process took 3 weeks. I interviewed at Google
Interview
I was approached by Google through their foobar challenge. I thoroughly enjoyed working through the levels of the challenge (I got through level 4) and actually learned few things in the process. But everything after that was pretty terrible.
First, through all of the exercises in the challenge, I had already provided them several hundred lines of code that I had written specifically for Google. But then they still wanted me to do a phone interview with a virtual 'whiteboarding' session. Which basically amounts to writing code in a Google Doc. Which is something I have never done, and never will do ever in any real life situation.
I have written code almost every working day for the past 20 years, in a variety of different languages. I have designed and led teams building web applications with dozens of classes and thousands of lines of code. But I have never written code in a word processor program. So in the phone interview I was pretty slow, and due to that slowness the interviewer concluded that I did not know how to implement a fairly simple Java class. It was demeaning experience and a complete waste of my time.
Interview questions [1]
Question 1
Implement a Java class that read a log file from a web application. The log contained data about how users interacted with a specific feature in the application. The task was to build a method that collected some simple statistics on that data.