The first step was to talk with the recruiter. The second step was a phone screen with two engineers; they asked me data structures and algorithms problems, LeetCode-style. After that, you get an onsite interview. My experience was not great: I had to work on a front-end project alone for more than two hours (I don't know the point of having an onsite; you could work on that project remotely). There were some technical difficulties setting up the machine, and when I asked the two interviewers about the problems I was having, one of them was super rude (I think he was having a bad day). Well, I spent most of the time setting up the project instead of working on it. The last session was to present what I had done to the team; one guy was in another office. He was rude and told us he didn't have time for this because he had another meeting. I couldn't present a lot of the features because I didn't have time to finish it. Then, they gave the recruiters feedback. The recruiters were 'trying' to get me a video interview so I could finish the project, but instead, they decided to reject me and move on.
Algorithms project
The following metrics were computed from 6 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 very selective, failing most engineers who go through it.
Candidates reported having good feelings for Niantic's Software Engineer interview process in San Francisco, California.