The general interview process is what you would expect. The first step is a short phone call with a recruiter, followed by a one-hour shared coding session using CodeInterview.io, and then an onsite interview. There was approximately one week between each step before scheduling the next.

The onsite was the longest one I've ever done, at seven hours. The most notable part of the process is the independent coding project, which took up half of that time. It was a three-hour, full-stack project done on my own laptop, followed by a thirty-minute presentation of my work to two engineers. It started off with an engineer giving me a rundown of the project with a printout of the exact instructions. Then I was on my own working on it in a conference room, with a check-in halfway through. The engineer also gave me their phone number and showed me where their desk was in case I needed any help, but the instructions were clear enough for me that I never needed to ask them for help.

The rest of the day consisted of thirty or forty-five-minute sessions:

• Lunch
• Talk with a product manager
• Talk with an engineering manager
• Architecture whiteboarding session
• Coding whiteboarding session, focused on object-oriented design

I had my onsite at the end of December when a lot of people were taking time off for vacation. Because of that, I had to come back onsite for an hour a couple of weeks later to meet with the VP of Engineering and hiring manager. The recruiter scheduled a phone call with me a couple of days later, where I received an offer.

Full-stack web application using a web framework, a database, HTML, and JavaScript.