My interview path followed a fairly classic structure: a recruiter screen, a technical screen, and then meetings that expanded into onsite-style rounds. The technical portion included system design and practical problem-solving that combined algorithmic work with a frontend component, so it was more ambiguous than pure coding.
The hardest part for me was figuring out what the interviewers expected. I sometimes struggled to interpret what they were asking, especially during the practical portion, which had several moving parts. The recruitment team was described positively overall, but the interviews themselves felt as if the company was busy. At different points, the interviewers seemed distracted, which made it harder to keep my answers aligned with the evaluation.
The final set included 4 to 5 sessions covering harder LeetCode-style problems, system design, and behavioral questions. One detail that stayed with me was that the behavioral segment effectively turned into system design again. That made the flow feel confusing rather than cleanly separated.
I didn't get an offer. In retrospect, the structure of the process seemed fair, but the unclear expectations during the practical work and the scattered engagement during the interviews made it feel less predictable than I wanted.
Location: San Francisco, CA. Overall feedback: Neutral. Offer status: No offer.
Discussion
Loading comments…