I went through a longer interview loop that started with an online assessment and then moved quickly to a phone interview. The phone screen used an Airtable-style scenario. That set the tone for the live coding portion, where the questions were meant to feel realistic and the follow-ups focused on explaining my choices, not just producing working code.
After that, I had several technical interviews back-to-back. They covered algorithmic coding, system design, and product-focused engineering. One interview centered on a UI flow from product requirements. I had to turn a mockup into an interface that handled hierarchical data without making it overly complicated. Another asked how I would implement a given UI mockup and usage description, including a pseudocode implementation and how I would structure the underlying code. I also had a more traditional "tell me about a time..." behavioral conversation.
The process was thorough without feeling chaotic. The take-home work I saw in this general path focused on edge cases and design tradeoffs. I didn't always feel that every interviewer asked the same kind of questions, but the direction was consistent: realistic problems, high-signal discussions, and a lot of explanation. I didn't end with an offer. I liked the intent behind the process, although it was demanding enough that one weak explanation could affect the decision.
Location: United States. Overall feedback: Positive. Offer status: No offer.
Discussion
Loading comments…