My process was short and ended earlier than I expected. I only made it through the recruiter phone screen before I was rejected. The recruiter conversation leaned heavily on resume questions and my related experience, and it became clear pretty fast that I was missing some of what they were looking for.
The questions themselves weren’t confusing—everything was about verifying my background—but I felt underqualified as we went deeper, and the direction suggested they weren’t going to stretch the evaluation further. Once that happened, the loop never really got a chance to start.
4 months ago
Difficult Positive San Mateo, CA
My interview journey had multiple rounds, and the structure emphasized interaction with team leadership as well as technical evaluation. The first and third conversations were with team managers, and between them I hit a technical coding round. The questions felt exciting and moderately difficult, and overall it came across as a genuine attempt to see how I reasoned rather than just whether I could guess.
One part that really stuck with me was how quickly the tone could shift during the coding exercise. I was told to stop talking and just complete the problem, which made the experience feel less like collaboration than I expected from the way they described what they valued. The technical piece itself was two medium leetcode-style problems, with about half an hour on each.
6 months ago
Average Neutral San Mateo, CA
I went through a fairly typical sequence that started with an HR call, then moved into a take-home assignment, and then ended with a technical intervi…
10 months ago
Difficult Neutral San Mateo, CA
My interview sequence had a few distinct formats chained together. I started with a recruiter screen, then completed a take-home assignment, followed …
Unlock every Robotics Engineer interview experience
