I received an email from a recruiter planning a phone "shared doc technical" interview. This interview felt fair, as I was able to focus on my stronger areas of software development since I was allowed to choose between a front-end search problem or a back-end graph problem. The question was straightforward, and I was able to answer with some pseudocode. I was also asked another question within the time period, which I answered. We then discussed the work they were doing, and I was asked some questions about my technical hobbies.
The in-person interviews consisted of two 45-minute technical interviews and one 30-minute lunch.
The questions weren't inherently difficult but definitely focused on your algorithmic and analytical abilities to analyze problems from different angles.
The two in-person interviewers were kinda standoffish, but I assume that is a front, as other employees in the office spoke highly of them.
Algorithms and data structures focusing on:
The following metrics were computed from 7 interview experiences for the Niantic Software Engineer role in San Francisco, California.
Niantic's interview process for their Software Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Niantic's Software Engineer interview process in San Francisco, California.