The interview process has 5 steps. The first step of the interview process is with the recruiter. If this goes well you will have to schedule a technical assessment with engineers in the company. I was only able to get to the technical interview phase of which I thought went decently well. The interview was will ask you a series of systems interview questions and then you have to solve up a coding problem. I did solve the coding problem and the interviewer close the call. I waited over a week to hear back from my results and j never received a follow up from the recruiter. I reached out via email to follow up with the recruiters and still no response. I then decide to call the recruiter and it seems like she forgot about me. For other developers who are applying for this company, be careful as it seems like they like to ghost people during the process. I wouldn’t waste my time.

I recently completed a 75-minute screening that included: 2–3 behavioral questions 5 rapid-fire system-design questions a 45-minute coding round and a short window for me to ask questions The technical questions were fairly straightforward, and I felt confident in my responses — clear, structured, and technically sound. While I haven’t received feedback yet, my best guess is that my rejection may have stemmed from the Q&A portion. I asked a few candid questions about the product vision, team culture, and growth opportunities — the kind of questions I believe any thoughtful engineer should ask when evaluating a team. Some of these seemed to catch the interviewers off guard, which might have left a mixed impression. Still, the engineers were pleasant, and the overall experience was positive. The only downside is the lack of feedback — something that always makes it difficult to learn what truly went wrong. Sometimes, teams might already have an internal candidate or be interviewing for formality’s sake — though that may not be the case here, the absence of closure leaves room for guesswork.