Nimble Robotics Robotics Engineer interview experience

Got offer

Hard

Positive

San Francisco, CAPosted Apr 2025 · Candidate report, summarized by Dataford

The first thing I did was a 72-hour coding challenge that tested both problem-solving and technical depth.

After completing that, the process moved into interviews that felt split between a technical introduction, behavioral conversation, and a coding interview. The pace stayed consistent and structured.

Then I hit a second 72-hour coding challenge that went deeper into real-world scenarios. By the time I reached the end of that loop, I understood why they emphasized engagement over pure trivia—the challenges were hard, but they were also the part where I felt I learned the most.

Mike, the Head of Talent, guided the whole process and was extremely responsive, with feedback coming back within a

Create a free Dataford account to unlock the full round-by-round breakdown, the questions asked and the outcome.

Read the full report Read the full report

Preparing for this interview?

Nimble Robotics Robotics Engineer interview guideThe full process, round by round, with the question bank Practice Robotics Engineer interview questionsReal questions from this role across companies All Nimble Robotics interview guidesEvery role we cover at this company