1. Phone screen with the recruiter for job fit.

2. Homework problem involving using a food truck API to make some reports in a CLI.

3. Final round: a. Systems Design Problem. b. Code review on the homework, and a little paired programming on an enhancement or bug fix. c. Pseudocode problem focused more around object-oriented coding design (think data structures and design patterns). d. Lunch interview. More behavioral, pretty low-key. e. Hiring manager: Talk about system design in a recent project and weigh the pros and cons. Talk more about your accomplishments in your past roles.

Overall, I loved the process and team; I actually had a lot of fun in this one. The interview was fair for a Senior level candidate. It was a top two offer for me, and I only turned it down because my other offer was better aligned with my current career goals. The team has a fantastic engineering culture with a clear focus on diversity and inclusion. 10/10, would apply again if the role better fits my goals.

The biggest part of coding is a homework problem around using an API endpoint for food trucks data to make some reports.

System design is going to be mostly practical applications for residential real estate.

Our object-oriented design session will be less focused on real estate and more on decisions around how you lay out classes, how they interact, and the data structures you use.