My interview process was much like the others described here. It started with a recruiter phone screener. In the call, the recruiter described the role, the tech stack, salary range, and benefits.

The next stage was a coding exercise. You receive a URL for a page describing the exercise. You need to hit an endpoint, transform the data, and post it to another endpoint.

My final interview was done 100% virtually. I had four different interviews over the course of five hours (including two breaks).

I first interviewed with the hiring manager for 45 minutes, with 15 minutes for any questions I had. This was a behavioral interview, but felt more like a conversation.

The second interview focused on algorithmic complexity in an approachable way. Where some interviews ask how to use an algorithm or data structure you'll never use again, this involved real-world algorithms and data structures. There were no "gotcha" tricks. The questions built upon each other to expand requirements and alter functionality. It's important to know how to speak in big-O notation.

My third interview focused on JavaScript, as I was interviewing for a frontend position. It was intended to see if I knew the foundations of how the language worked. Similar to the algorithmic complexity interview, these tasks built upon each other to cover different JS aspects. For this, it's important to know how JS works, not just its syntax.

The last interview was a frontend systems design interview. The prompt was very simple and required asking questions, as most system design interviews do. The interviewers answered questions well and tried to guide the discussion. I was dinged for not going deep enough (I agree; I've been dinged for going too deep in the past and overcompensated). It's important to first show breadth of knowledge in systems design, but also go deep on topics you're strongest in.

For each of the technical-focused "on-site" interviews, speaking your thought process out loud is crucial. Each stage of the process also involved behavioral questions.

Can you give me an example of a tough technical challenge you've had?

What is an example of a time when you changed direction because of customer feedback?