Boston Dynamics logo

Boston Dynamics Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 7 interview experiences · FREE TO READ

2.7 Rounds average
Average Typical difficulty
57.1% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Boston Dynamics.

Showing 3 of 7
Boston Dynamics logo
Boston Dynamics

Software Engineer

Engineering · a year ago

Mid Difficult Positive experience No offer 3 rounds
Interview process
Recruiter call Phone screen Presentation Technical screen Onsite
Interview formats
Behavioral Technical Coding Presentation

It started with a recruiter call, then a chat with the hiring manager where we mostly talked about past experiences and they threw in a few easy technical questions. The final part was a 4-hour on-site with a project presentation and two live coding interviews.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

Boston Dynamics logo
Boston Dynamics

Software Engineer

Engineering

Lead Average Negative experience No offer 1 round
Interview process
Recruiter call Technical screen Presentation Onsite
Interview formats
Technical Presentation Behavioral Other

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.

Confirmed questions1 question
  • Can you explain shared memory and its application in a specific situation?
Boston Dynamics logo
Boston Dynamics

Software Engineer Intern

Engineering

Intern Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Background check
Interview formats
Behavioral Technical

The interview process had 4 stages: resume screening, then three rounds. The first round was a 30-minute HR screening. The second was a 45-minute technical interview with engineers, which was technical only. The third round was with a manager, focusing on your experiences and yourself. This round could still lead to rejection, which is what happened to me.

Confirmed questions1 question
  • Can you share an instance where a project you worked on failed?

Boston Dynamics Software Engineer Interview Questions

Quoted word for word from Boston Dynamics interview reports.

Can you explain what a SLAM algorithm is in general terms?

Read reports

Can you explain shared memory and its application in a specific situation?

Read reports

Prepare and deliver a 15-20 minute presentation on a subject you are knowledgeable about and which is relevant to the role.

Read reports

Can you share an instance where a project you worked on failed?

Read report

Formats, difficulty and experience

Across all 7 Boston Dynamics interview reports.

Interview formats

Technical 35%
Behavioral 30%
Presentation 20%
Coding 10%
Other 5%

Interview difficulty

Easy 0%
Average 57.1%
Difficult 42.9%

Candidate experience

Positive 57.1%
Negative 28.6%
Neutral 14.3%