1. Initial call with an internal recruiter 2. Hatchways take home project: Build an sdk for a simple api 3. System design interview: They asked me to design a distributed system for their core product. I received feedback a week later that was contradictory, it starts off that I didn't optimize then later claims that optimizations I outlined were not justified enough. Another part of the feedback was a problem with my proactive approach to user-centric design. When asked what would happen if a user searched for something that doesn't exist I first said "they would need to wait until it was available" and then designed a component to kickoff the building of the missing item. Looking back, that was a reasonable response considering the design prompt I was given included a web crawler that would make it rare for non-indexed items to be available. There's at least 1 more interview after system design, but I got rejected after the system design interview. I had a pleasant experience, although it was a bit lengthy for it to not turn into anything. Like other reviewers, based on my experience I have doubts about the legitimacy of the opportunities at this company for US based candidates.

The interview process involves four stages: an initial video screening with a recruiter, a take-home coding assignment to build a mini SDK via Hatchways, a technical interview with peers, and a final interview with the CEO.