They call it a three-step process, but it's closer to 8+.

1. Talk to the recruiter
2. Code screen
3. Interview "Power Day"
   • Behavioral interview
   • Behavioral interview 2
   • Case interview (details below)
   • Tech interview - system design
   • Tech interview - coding
4. Team fit interview (they insist this isn't an interview, but I had to meet three hiring managers before getting an offer, so I would absolutely call this an interview)

Code Screen: I won't put the actual questions here, but the code screen consisted of four algorithm (LeetCode style) questions that you had to implement over the course of an hour.

I don't think you have to finish the whole thing to pass, but the first two were very simple and should only take a moderate coder 15-20 minutes at most. The third question also had a simple solution but took a little longer to implement. The fourth question was the only one that had constraints that prevented me from using the simplest brute-force solution.

Behavioral Interviews: Each of these consisted of three standard "describe a time where you..." manager questions. The caveat here is that you have to answer in the SAR format (Situation, Action, Result). They tell you this upfront and they mean it. Stick to the script and say: "The situation was (...). My actions were (...). The results were (...)." If you deviate from that, your interviewer will get lost very quickly.

Case Interview: I expect these vary depending on your interviewer, but mine was a simple business case, and they gave me a code snippet that was meant to be a partial solution to that business case. The interviewer and I discussed what the code was currently doing, if it solved the use case, and what changes we might make to improve it (and also actually made some changes to the code). So it was a combination of code comprehension, code editing, understanding the use case, and critical thinking.

System Design: I thought this was a pretty standard system design question. Draw out your architecture, say what kind of technologies you'll use and why, and describe some of the interactions between your components.

Live Coding Interview: Pretty simple LeetCode-style question. Just talk through what you're doing as you're writing it.

Team Fit Interview: This was my biggest gripe with the whole process. No one in the above sections is actually on or related to the team you'll be interviewing for. If you pass all of those, you then talk to a potential hiring manager, and they decide if you're a fit for the role. As I said above, I still very much consider this part of the interview process because hiring managers can and will pass on you for little things or things out of your control. For example, my first interviewer passed on me because I admitted Java/Spring isn't my preferred tech stack. My second interviewer passed on me because they were actually looking for a tech lead and not a manager. My third interviewer apparently liked me enough, and I did get an offer. If that didn't happen, I'm sure I could have eventually run out of potential hiring managers.