I applied online. I interviewed at 98point6 (Seattle, WA) in Sept 2020
Interview
The main interview loop (following phone screen) involved a take-home assignment followed up by two technical sessions and three behavioral sessions.
The take-home assignment was a somewhat arbitrary problem largely unrelated to the position, but one which had interesting challenges and which clearly demonstrated software design skills. The problem statement was clear and comprehensive.
One thing I particularly appreciated was how closely reviewers looked at the code. At one point, I included a comment about an inconsistency in the API spec and how it required some special handling by the service. A technical interviewer noticed and asked some follow-up questions about the comment and how I would restructure the API.
The interview spanned about 6 hours with regular small breaks. The additional information provided helps support you through the behavioral sessions. One thing I did note is some overlap in questions during the technical sessions.
I applied online. The process took 2 weeks. I interviewed at 98point6 (Seattle, WA) in July 2021
Interview
The process was quick and consisted of a recruiting call, a take home project with plenty of room to show off, and the interview loop.
Most of the loop was behavioral and focused on my experience. There were a couple system design questions and a review/expansion of the take home work, but instead of an interrogation it was more of a conversation about requirements and other considerations.
Interviewers were from all teams in the company, which including those with non-technical backgrounds. Everyone seemed passionate about what they do and were incredibly transparent, including HR when discussing benefits and salary.
Overall it was a very positive, informative, and refreshing experience - especially when compared the all-day grinds of random LeetCode problems that I've experienced at many other companies.
Interview questions [1]
Question 1
Expect standard behavioral questions and be able to explain your answers to different types of audiences.
Standard system design questions (stakeholders, architecture, scale, etc.) around an API to drive a mobile game with some interesting requirements added in here and there to explore how you think about the problem.