Real, anonymous reports from people who interviewed for Software Engineer at Nimble Robotics, newest first and distilled into what to expect across the loop.
Get your personalized Nimble Robotics Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
After a recruiter call, the process moved quickly into a 72-hour take-home assignment. It felt like the biggest hurdle right away, and the work was substantial enough that I treated the rest of my week like it was blocked off for the submission.
Once I finished the assignment, I was scheduled for a behavioral interview. That was followed by technical interviews, and the loop ended with a CEO round. The overall sequence was very structured, but the difficulty level matched how intense the take-home was, and I didn’t end up getting an offer.
4 months ago
Average Positive United States
The process began with an initial recruiter conversation, and then I was given a confidential full-stack take-home challenge. The task focused on building a local full-stack system with backend APIs and frontend user flows, including database persistence and boundaries around authentication.
It also came with clear expectations for documentation and a demo of what I built, so it wasn’t just about getting something to run—it was about explaining the implementation. After I submitted, I had a follow-up discussion with the team that went into the architecture and how I approached the engineering work. Overall it felt like an evaluation of real-world tradeoffs rather than just code correctness, and I didn’t receive an offer afterward.
9 months ago
Difficult Negative United States
My first step was a short behavioral recruiter chat. Not long after, they sent over a 72-hour take-home assessment. I started it, but even after spend…
> 1 year
Difficult Negative San Francisco, CA
My process started with a 72-hour hackathon built around a ball tracking application using WebTransport and WebRTC. The requirements were broad, and i…
> 1 year
Average Positive San Francisco, CA
This process felt chaotic compared to what I expected. I ended up on at least five phone calls before I spoke to anyone with a technical background. E…
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
Take-home Assignments
Candidates can expect two substantial 72-hour take-home coding challenges that require significant time and effort, often focusing on real-world applications and production-level coding standards. These assignments are seen as critical gatekeepers in the process, heavily influencing the overall evaluation.
Following the take-home assignments, candidates typically engage in multiple technical interviews that assess their problem-solving skills and understanding of system design, often with a focus on practical engineering scenarios rather than purely algorithmic questions.
system designproblem-solvingtechnical depth
Behavioral Interviews
Candidates will have behavioral interviews, often with the Head of Talent or senior engineers, where the focus is on fit and past experiences rather than a strict Q&A format. This part of the process is generally conversational and aims to assess cultural alignment.
behavioralcultural fitconversational
Feedback and Communication
The interview process is characterized by relatively quick feedback after each stage, usually within a day or two, which candidates appreciate. However, some candidates noted inconsistencies in communication, especially after the later stages.
quick feedbackcommunicationtransparency
Overall Structure and Difficulty
The interview process is described as well-structured but demanding, with candidates often feeling that the workload, particularly from the take-home assignments, does not align with the depth of evaluation in subsequent interviews. Many candidates reported not receiving offers despite significant effort.
structured processhigh difficultyeffort vs. outcome
Expectations and Clarity
Candidates expressed that the expectations for the take-home assignments were sometimes unclear, leading to confusion and stress during the execution phase. A lack of upfront clarity on evaluation criteria was a common concern.