Nimble Robotics Robotics Engineer interview experience

No offer

Hard

Negative

United StatesPosted Feb 2025 · Candidate report, summarized by Dataford

The process hit hard up front with two separate take-home coding challenges, each scheduled for three days.

The first was a software challenge where I had to simulate a bouncing ball and share frames of it using a specific library across two nodes.

The second challenge was more robotics-oriented, covering kinematics, dynamics, and perception. Both assignments were demanding, and the difficulty came not just from coding but from dealing with the underlying concepts they were testing.

I made it through the process enough to complete the challenges, but I didn’t end up getting an offer. Reflecting on it now, the hardest part was how much multi-domain understanding the tasks assumed, not just how

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