Step 1) Phone call from recruiter. Typical introduction and matchmaking call.

Step 2) Live coding with video cam. I used Data Structure Set for this one, and the interviewer had a follow-up scenario wherein a coworker made a code pull request to answer the same question but with a different approach. How would you review his code?

Step 3) On-site interview. Buckle up for a long day. Total of 5 hours.

• 30 min interview with Product Manager.
• 1 hour interview with 2 senior software engineers. They had me whiteboarding and then, with a different question, using an online tool like CoderPad.
• 15 min break.
• 30 min behavioral Q&A with Executive Director.
• 15 min talk with recruiter.
• 30 min break.
• 1 hour system design & architecture with 2 software engineers. This is the most challenging, so try to really understand the tools and strategy needed to scale based on the application you're given to work with. Like recording stats about the total number of hits and up-votes/down-votes, or adding comments on an article. How about offline access? Do you need cache management? How about a load balancer? Or how about rendering on the server side vs. client side?
• 1 hour interview with Senior Software Engineering Manager to see if there is a fit for you under different teams.

Overall, I had a very positive experience. Everyone has been pleasant and nice to talk to. It felt more like a very, very technical conversation over an interview.

Whiteboarding with Set Data Structure. Follow up with Map and Array for phone interview. On-site includes whiteboarding algorithms and CoderPad. System design architecture.