A recruiter reached out to me and immediately set up a phone interview with a VP of Engineering. He mostly asked questions about my experience and things I've worked on, and dove into some technical details of past projects. The interview went well, so I was told on the phone that I could skip the online quiz part of the process and come right in for an on-site interview.

Being a full-stack engineer, I was also told that the on-site would consist of either backend or frontend questions, and I had to choose one. I was also asked if there was any part of the stack that I didn't know as well, which for me was relational databases. This was really important because they ended up taking it easy on me when it came to any database questions during the interview. I would highly recommend being open and honest about your strengths and weaknesses.

The on-site interview consisted of:

• A quick chat and tour of the offices with the recruiter.
• Three, one-hour-long technical interviews, each with two members of the engineering team.
• An hour-long interview with the VP.
• A brief wrap-up with the recruiter.

The technical interviews started with about 15 minutes of chatting about past projects, and then went into scripted technical questions that involved whiteboarding. The technical questions were somewhat challenging but extremely practical. There were none of those, "I'll never have to do this in real life," questions. There was also some time left at the end of the interviews to ask questions. The interview with the VP was unscripted but fairly technical as well. We talked in detail about past systems that I've implemented, and he would propose scenarios, e.g., "Suppose the API you were using was rate-limited..." and ask how I would handle them.

After the interview, the recruiter maintained frequent communication and was very responsive to any questions I had. I received an offer exactly one week later and accepted!

Design a URL shortener.