Real, anonymous reports from people who interviewed for Software Engineer at Intuitive Surgical, newest first and distilled into what to expect across the loop.
My interview loop started with a recruiter call, then quickly went into manager and hiring-manager conversations where the main goal felt like understanding how I’d operate and explain engineering decisions. The part that stood out most was the technical interview that leaned hard into fundamentals and engineering reasoning rather than generic software talk. I was asked about mechanical and materials fundamentals, test-method development, and how I’d think about sample size. It also included prototype testing, troubleshooting, and making clear engineering decisions under pressure.
My process started with a recruiter call where they summarized the team and then dug into my resume—especially academic projects and the experience I’d listed. After that, I had three independent virtual interviews: one with the hiring manager, one with another parallel manager, and one peer interview. The rounds felt like a blend of technical questions, discussion of my work history, and a clearer picture of what the role would actually involve.
The interview process typically starts with a recruiter call followed by multiple rounds, including technical and behavioral interviews, often culminating in a full-day on-site with presentations and case studies. Candidates noted that the structure can vary from well-organized to somewhat chaotic, impacting their overall experience.
Technical interviews focus heavily on engineering fundamentals, problem-solving, and specific domain knowledge, with some candidates reporting a mix of coding questions and practical engineering scenarios. The intensity and depth of these interviews can vary, with some candidates feeling challenged while others found them straightforward.
Many candidates are required to present a personal project or a hypothetical scenario during the on-site interviews, which tests their ability to communicate technical concepts and reasoning under pressure. This component is often seen as a critical part of the evaluation process.
Candidates reported mixed experiences regarding communication throughout the process, with some experiencing delays and a lack of feedback, leading to feelings of uncertainty and frustration. Others noted positive interactions but still faced long wait times for updates.
Behavioral interviews often focus on understanding candidates' past experiences and how they approach problem-solving in a team environment. The tone of these interviews is generally conversational, aiming to gauge cultural fit and collaboration skills.
The overall difficulty of the interviews is perceived as average to challenging, with candidates expressing varying levels of confidence in their performance. Many noted that the outcome often felt anticlimactic due to delayed feedback or lack of closure after the interviews.