My experience overall felt easygoing, and the people I spoke with were genuinely nice. The process didn’t come off as hostile or overly intimidating, and that made it easier to stay confident.
What mattered most was how I presented myself—staying confident, being well-prepared with the basics, and speaking clearly about the fundamentals I’d learned through school. First engineering principles came up as a key theme in how I needed to frame my thinking, and I felt like I could do that without struggling.
1 month ago
Difficult Neutral Berlin
Two technical managers joined my interview, and the intensity level jumped immediately. The conversation covered both motivation and a mix of technical and behavioral questions.
On the technical side, I was asked about something tied to a motor module, and it required me to be more rigorous than I expected. Then the behavioral part challenged how I’d handle difficulties when working as an engineer in production, where issues can pile up fast and you still have to deliver.
1 month ago
Average Positive Fremont, CA
After a phone recruiter screen, the process was pretty direct: two rounds total. The first interview was LeetCode-style, focused on algorithms and pro…
1 month ago
Average Positive Fremont, CA
My interview kicked off with four back-to-back one-on-ones, each about 30 minutes. The overall flow was fast, but the timing felt consistent: the firs…
1 month ago
Difficult Positive Fremont, CA
Most of my interview was a resume overview that quickly turned into technical depth. The interviewer kept pointing back to what I’d written and asked …
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 & Flow
The interview process typically consists of multiple back-to-back rounds, often starting with behavioral questions followed by technical assessments. Candidates experienced a mix of formats, including one-on-ones and panel-style interviews, with varying degrees of structure and pacing.
multi-roundbehavioraltechnical
Technical Assessments
Technical interviews often focus on algorithms, data structures, and specific engineering principles relevant to the role. Candidates reported a mix of coding challenges and system design questions, with an emphasis on clear reasoning and practical application of knowledge.
codingalgorithmssystem design
Behavioral & Fit Questions
Behavioral questions are a significant part of the process, assessing candidates' problem-solving approaches and teamwork experiences. Interviewers often look for resilience and how candidates handle real-world engineering challenges.
behavioralresilienceteamwork
Depth of Knowledge Required
Candidates noted that interviews demanded a deep understanding of core concepts, particularly in areas like controls, ML, and project-specific knowledge. The ability to explain technical details clearly was crucial for success.
core conceptstechnical depthexplanation
Communication & Interaction Style
The communication style of interviewers varied, with some candidates experiencing a more conversational approach while others felt rushed or condescending. This aspect significantly impacted candidates' ability to showcase their skills effectively.
communicationconversationalinteraction
Overall Difficulty & Candidate Reflection
Candidates found the overall difficulty of the process to be moderate to difficult, with many reflecting on the importance of preparation and clarity in their responses. Some expressed confusion over the evaluation criteria and felt the process lacked transparency.