Robotics Software Engineer applicants have rated the interview process at Nimble Robotics with 4 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 33% positive. To compare, the company-average is 70% positive. This is according to Glassdoor user ratings.
Candidates applying for Robotics Software Engineer roles take an average of 14 days to get hired, when considering 3 user submitted interviews for this role. To compare, the hiring process at Nimble Robotics overall takes an average of 25 days.
Common stages of the interview process at Nimble Robotics as a Robotics Software Engineer according to 3 Glassdoor interviews include:
Phone interview: 40%
One on one interview: 40%
Skills test: 20%
Here are the most commonly searched roles for interview reports -
I interviewed at Nimble Robotics (San Francisco, CA)
Interview
Recruiter Call asked common behavioral questions and background. Next was a coding challenge to complete in 72 hrs. The prompt doesn't have clarity on what all things they expect in the code. Got a. feedback within 1 hr of submitting the challenge and they have a rubric they use to grade the challenge which should have been provided before.
Interview questions [1]
Question 1
WebRTC WebTransport based client server implementation.
I applied online. I interviewed at Nimble Robotics (San Francisco, CA) in Dec 2025
Interview
Call with recruiter - Mike
1 hr technical screen with Hiring Manager
Take Home (Quite time consuming actually - well over estimated 4hrs)
1 Coding Round
1 Domain Technical
1 System Design
CEO round
Feedback for each round was within a day or two
Interview questions [1]
Question 1
Planning concepts
Controls concepts
Basic DSA
System Design
I applied through a recruiter. The process took 2 weeks. I interviewed at Nimble Robotics
Interview
The process had 2 take home coding challenges to be completed in 3 days each. The 1st is a software challenge and the 2nd is a robotics challenge. In the first challenge, you have to simulate a bouncing ball and share frames of the ball using a specific library across 2 nodes. The second challenges covers, kinematics, dynamics and perception.
Interview questions [1]
Question 1
In the first challenge, you have to simulate a bouncing ball and share frames of the ball using a specific library across 2 nodes. The second challenges covers, kinematics, dynamics and perception.