My process kicked off online with some kind of coding challenge sent after I applied—one time it came by email with a deadline window, and in general it was framed as a JavaScript exercise. I had to work within the timing they gave me, and the challenge itself ranged from “pretty manageable” to moderately difficult for me depending on how familiar I was with that style.
After submitting, I moved into the live rounds. I had a recruiter screen where we covered behavioral questions and general fit, then I went through multiple technical interviews. The recurring theme was clean, production-minded code and LeetCode-style problem solving focused on data structures, plus at least one system design or a design-adjacent technical discussion. One round in particular involved writing through a problem and emphasizing correct, well-tested structure. I also did interviews with senior technical folks, including a CTO round that was framed around problem solving and critical thinking, and there was a later conversational round with founders or leadership in the flow I experienced.
> 1 year
Average Positive United States
I had a process that started with the standard coding-focused gate, and after that it shifted into interviews that were more about how I think and how I communicate. In one set of rounds, I worked through LeetCode-style coding problems and then talked through behavioral experience, with an emphasis on producing clean code and writing in a way that suggested I could deliver solid, well-tested implementations.
But the tone didn’t stay consistent for me. Even when the technical conversations felt friendly at times, I experienced HR and interviewers being assertive in a way that didn’t match what I expected from the culture. In another HR screen, the questions got personal—things like internship outcomes and GPA—so the whole call felt more like pressure than discussion. The process also felt inefficient at points, with interviews running over time or getting disrupted (including technical issues that forced a change in how we worked), which made it harder to perform the way I wanted to.
> 1 year
Average Positive United States
I started with a take-home coding assessment, which felt like the main hurdle of the process. I got through it, and then the next step was a recruiter…
> 1 year
Average Positive Canada
I had a recruiter experience that stood out for being fast and time-conscious. The recruiter replied quickly, kept things moving without unnecessary d…
> 1 year
Easy Negative United States
I interviewed with the China team, and the whole thing felt rough from the start. They effectively dumped an online coding assessment on me to complet…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Initial Coding Assessment
Candidates typically start with a take-home coding assessment focused on JavaScript or production-level code, which is seen as a significant hurdle in the process. The difficulty can vary, and candidates should be prepared for a timed challenge that emphasizes clean, well-tested code.
JavaScriptCoding assessmentProduction code
Recruiter Screening
The recruiter screening is generally a friendly and approachable conversation covering behavioral questions and general fit, though some candidates noted inconsistencies in tone and assertiveness during this stage. Candidates should prepare for both personal and professional questions.
BehavioralRecruiter screenGeneral fit
Technical Interviews
Technical interviews focus on LeetCode-style coding problems and system design discussions, with an emphasis on producing clean, production-minded code. Candidates may experience varying levels of professionalism and communication styles among interviewers.
Technical interviewLeetCodeSystem design
Interview Coordination and Communication
Overall, candidates noted that the coordination and communication from recruiters were generally responsive and efficient, although some experienced a lack of clarity regarding interview formats and outcomes. Candidates should expect a well-organized process but may seek clarity proactively.
Recruiter communicationProcess efficiencyClarity
Interview Experience and Tone
The tone of interviews can vary significantly, with some candidates experiencing assertive questioning that felt more like pressure than discussion. This inconsistency can affect confidence levels, so candidates should be prepared for a range of interpersonal dynamics.
Interview tonePressureConfidence
Feedback and Closure
Many candidates reported dissatisfaction with the lack of feedback and closure after the interview process, often receiving rejections without clear explanations. Candidates should be aware that follow-up communication may be limited and prepare to seek feedback proactively if possible.