
Boston Dynamics Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 41 interview experiences · FREE TO READ
Which role are you interviewing for?
22 roles · 41 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Boston Dynamics.
Mechanical Design Engineer
The interview process started with an HR phone call where they asked about my salary expectations and a typical day. This was followed by an interview with the hiring manager and an in-person interview. They seem to really want someone with prior robotics experience or the ideal candidate. Be prepared for some on-the-spot statics questions, which can be tough unless you're a recent grad. It felt like an IQ test. I noticed they don't ask questions that evaluate overall experience, creativity, or technical skills as much as they do textbook questions. It's odd because you can look up answers on Google, but you can't Google creativity. The base salary is around the middle of the market.
- Can you complete a take-home design challenge?
- Are you able to answer questions based on first principles?
Electrical Engineer
The whole thing took about 3 weeks and had 3 interview rounds. I talked to HR first, then a senior engineer, and finally a manager and another engineer. After the HR chat, the rest were technical questions, plus talking about the company and the job (and I got to ask my own questions too). It was cool, everyone I met seemed to like their jobs and asked about my plans. HR was also good about replying fast and being upfront about how things would go. Honestly, the smoothest interview process ever.
- Can you elaborate on a project you were involved in and the difficulties you encountered?
Shipper/Receiver
I applied for a job and they contacted me about a different one. The interview process was pretty basic. First, there was a phone screen with the HR person who reached out. Then, I had a phone interview with the manager. The manager was late to the call and didn't seem to know much about the role. They didn't give me a clear description of the position. The questions were really simple, and the whole interview felt awkward. After I answered, there were long pauses because the interviewer didn't know what else to ask. I'm glad I didn't continue since I got another offer soon after.
- Can you tell me about yourself?
- What's your experience?
- Describe a challenge you faced at work and how you handled it.
Software Engineer
The interview started pretty standard, but they let me know upfront I'd need to do a presentation. The person coordinating things was nice and hit me with some tough technical questions about memory busses and stuff. It was a whiteboard session, not a big deal, but maybe not what I expected for this level, even with my hardware/software background. Their projector wasn't working, which ate into my presentation time. I managed to get the presentation going and suggested we save the Q&A for the end because of the delay, and everyone agreed it was a good idea. But then, two out of the four interviewers kept cutting me off, and one asked totally random questions. It was weird, and I got the sense it was on purpose, or if not, that's just how it is. At the end, the lead interviewer said, "Good job, thanks." I asked, "Any questions?" and he replied, "Well, no, because you didn't leave any time for questions!" with this look of disbelief. I didn't explain about the equipment delay or the interruptions; better to just be gracious. I figured right then that if I got an offer, I'd have issues working with some of the team. I saw other comments about the "MIT" vibe and think that might be it. Had lunch with the recruiter and someone else not involved in the interview, which was fine, always good to meet people. They mostly talked to each other, not super rude, but it showed there was no effort to sell me on the role. The employee, not the recruiter, walked me out, another sign. The robots were really cool, though. I got a small tour, and I messed up by joking, "Atlas is sleeping; he sure must be tired from all those videos." I was told off for using a pronoun that personifies it. I get it; they don't do that there to avoid emotional attachment to something that looks human. The team's reaction felt out of line, and I don't think it was intentional, which is concerning.
- Can you explain shared memory and its application in a specific situation?
Boston Dynamics Interview Questions
Quoted word for word from Boston Dynamics interview reports.
“Can you explain what a SLAM algorithm is in general terms?”
Read reports →“Given this broken robot part, what do you think caused the failure, and what are some ways to improve its strength without major changes to how it's made?”
Read reports →“Could you illustrate the force vs. displacement relationship for springs and dampers?”
Read reports →“Can you design a filesystem utilizing object-oriented programming principles?”
Read reports →“For a set of components shown, what were their manufacturing processes and what is the function of specific features?”
Read report →“What are your thoughts on Tesla as a competitor right now?”
Read report →“In what ways could you revolutionize the world using robotics?”
Read report →“What about planning in robotics?”
Read report →“Looking at this drawing, what flaws or areas for improvement can you identify?”
Read report →Formats, difficulty and experience
Across all 41 Boston Dynamics interview reports.