Quite long an challenging. 3 stages of technical interview - live coding, technical discussion and system design. Then last stage team fit. It took almost a month to go through the whole process

The experience was similar to what has already been described by others. I passed the first two stages but did not pass the system design interview. My first attempt was definitely on me — I was not prepared well enough. I took the feedback seriously, prepared much better for the second attempt, and expected a more balanced evaluation. However, the second system design interview felt frustrating because the interviewer repeatedly guided the discussion toward minor or less important parts of the design, which consumed a significant amount of time and prevented me from properly covering the core architecture and trade-offs. Overall, the process was useful, but the system design stage felt inconsistent and highly dependent on the interviewer’s style.

The coding round itself isn't particularly difficult. The challenge isn't solving the problem—it's writing code that could realistically be shipped to production. Getting the code to work is the baseline. What the interview really evaluates is whether you naturally make production-quality engineering decisions: choosing appropriate data models, validating inputs, designing maintainable APIs, handling edge cases, considering concurrency, writing tests, and producing code that can evolve as requirements change. My impression is that they're testing engineering habits more than pure problem-solving ability. You can solve the problem correctly and still struggle if your design choices suggest the code wouldn't be suitable for a real production system.