Nimble Robotics Software Engineer Interview Questions
& Process

I got contacted by the Head of Talent via HandShake after submitting my resume. The process kicked off with a 72-hour python coding challenge where I had to build an app based on some requirements. Then, there was an intro call with the Head of Talent to see if I was a good fit. After that, another 72-hour take-home challenge, this time building a full-stack web app with specific requirements. This was followed by technical interviews with team members. The final step was a discussion with the CEO. The entire process was really well-organized and laid out from the start. Big thanks to Mike, the Head of Talent, for managing it all so smoothly. The two take-home assignments really felt like a taste of actual work, letting me show I could handle tough problems and write production-level code. The interviews were also very productive, more like interesting discussions than just a Q&A. It seems like the company clearly knows the type of person they want and has a solid future vision.

So the whole thing started with my resume getting screened. After that, I was given two take-home coding assignments that I had to complete within 72 hours. These assignments were pretty detailed and seemed to cover a lot of what a candidate would need for day-to-day tasks. Then there was a recruiter call where we talked about behavioral stuff. After that, I had a technical interview. It wasn't a standard LeetCode-style question, but it wasn't super obscure either. It just felt weird to put so much effort into two take-home assignments and then not really use them much to decide on new grads.

The recruiter was good about giving quick feedback and was upfront about the salary being on the lower end. However, there were two 3-day take-home assignments, an interview with the chief engineer, and a few more interviews with other senior folks. The take-home tasks were pretty time-consuming but seemed like they were just skimmed over.