In my experience, the interview process was pretty standard. I also ended up being an interviewer for the company for a while, so I saw it from both sides.

There were four rounds:

• An initial 1-hour round that emphasized behavioral/culture fit, but still included a CoderPad problem (online coding challenge).
• Three follow-up technical rounds, each 45 minutes long, that emphasized CoderPad questions.

There are several different types of potential technical rounds, and which ones you will get depend on the role you are interviewing for. When I was doing the interviews, the different types of technical rounds were not well-defined and were in flux. But suffice it to say, you could get something more algorithm-focused or more high-level system design, again depending on what you were interviewing for.

If all this goes well, you would have a final interview round with someone higher up, like a VP. I think this is just supposed to be a quick chat/sanity check to ensure a high-level person has had a chance to review you and make sure you have questions and passion for the job/company. That's what it seemed like to me when I did it; it was about 30 minutes and was mostly the VP answering my questions (so make sure you have good questions ready to go, which is good general interview advice anyway). There were no technical questions in this round.

After that was one more 15-minute meeting that was basically just the "in-person" offer.

At the risk of pointing out the obvious, this was all remote. Although an important note is that you can interview in any language that CoderPad supports, which is a pretty long list of common languages. However, some languages are better for interviews than others, in my opinion.

One of the technical questions I was asked was the spiral matrix problem:

https://medium.com/@amishav/javascript-coding-interview-the-spiral-matrix-99db31843be4