My process was strange in the way it ended. I felt like I did well, and I did make it to a final interview stage. They didn’t really promise me anything during the process, but the momentum felt positive.
Afterwards, I followed up about a week and a half later and never heard back. That lack of closure was what stuck with me, more than anything that happened during the interview itself.
2 months ago
Average Positive São Paulo, São Paulo
After the recruiter step, I ended up in a technical interview that felt mid-to-hard. The main problem was a simulation—moving a rocket around in a game-like way. I could follow the idea and make progress, but the time box was brutal for what I needed to implement cleanly. By the time I got to the parts that would make it fully correct and complete, I’d run out of runway.
It left me with the sense that the target was more polished execution than just having a workable approach, and my pacing wasn’t good enough for their expectations. I didn’t move on from that round, and honestly it was disappointing because I could see how to solve it, just not fast enough for the format they used.
2 months ago
Difficult Neutral Palo Alto, CA
My process hinged on a take-home plus a live follow-up. The topic was a Python language model application, and it wasn’t enough to jump straight into …
3 months ago
Average Positive India
I didn’t start with a typical application flow. I was shortlisted by the recruiting team based on my GitHub profile and open-source work, and then I w…
4 months ago
Average Neutral London, England
My first interview was simple and direct. I was asked to introduce myself, and then the conversation quickly shifted into presenting a project. I had …
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
Interview Structure & Stages
The interview process typically begins with a recruiter call, followed by a mix of technical interviews, including coding assessments and project discussions, often culminating in a final onsite presentation or discussion. Candidates should be prepared for a non-linear flow that may include unexpected topics like electrical engineering or system design.
Candidates can expect a variety of technical assessments, including leetcode-style coding problems, simulations, and Python-focused tasks, often under time constraints that emphasize both correctness and execution speed. It's crucial to practice coding under pressure and understand the specific language requirements.
LeetcodePythonSimulations
Behavioral & Project Discussions
Interviews often include deep dives into candidates' past projects and experiences, focusing on technical decisions and reasoning rather than just surface-level descriptions. Candidates should be ready to articulate their thought processes and the rationale behind their engineering choices.
Candidates frequently report a lack of communication after interviews, which can lead to frustration and uncertainty about their performance. It's advisable to follow up after interviews but be prepared for potential delays or silence from the hiring team.
Follow-upCommunication issuesCandidate experience
Expectations & Difficulty Levels
The interview bar is perceived as high, with expectations for candidates to demonstrate strong fundamentals across various domains, including software engineering, machine learning, and system design. Candidates should prepare for challenging questions that require both depth and breadth of knowledge.
High expectationsFundamentalsDifficult questions
Cultural Fit & Company Values
Interviews often assess cultural fit, with questions that connect candidates' interests to the company's mission and projects. Understanding the company's values and being able to articulate personal alignment with them can be beneficial during interviews.