Similar to what many others have shared, the process has four steps.

The first step is a 30-minute phone chat with HR. No technical questions were asked in this initial round.

The second step is a timed coding challenge hosted on HackerRank. I was asked to solve two problems using knowledge of data structures (trees, hash tables, etc.).

The third step is an hour-long phone screen with one of the engineers. Some questions were about projects on my resume. These questions can sometimes go really deep into implementation details and reasons behind design decisions.

The majority of questions emphasized theories and concepts from the CS undergraduate core curriculum, including data structures, algorithms, OS, networking, compilers, and software engineering.

The fourth and final step is on-site. In the morning, there were three technical interviews, each taking about fifty minutes.

An engineer came in with my resume and used it to formulate some starter questions. After the resume questions, the interviewer began asking coding questions. Depending on the interviewer, the questions, and how much time was left, the format could be whiteboard coding only, or whiteboard coding plus peer-to-peer real coding on a computer.

After the three technical sessions, two engineers took me to lunch, which was explicitly stated to be not part of the evaluation. I got to chat with them and ask many questions.

After returning from lunch, I met with a manager who introduced his team and their tasks. This meeting was only about 20 minutes, as he was rushing to another meeting. Then, I met with the HR representative I had been contacting throughout the recruiting process. The HR asked a few final questions, but none were technical or behavioral.

Data structure: Heap, Hash table internals