Real, anonymous reports from people who interviewed for Software Engineer at Intuitive Surgical, newest first and distilled into what to expect across the loop.
Get your personalized Intuitive Surgical Software Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
After a recruiter screening that was pretty focused and fairly quick, I moved into a hiring manager call and then a longer technical interview. The process felt structured, with each round building on the last, and the pace picked up once they decided to keep me going. The technical interview pushed me to go deeper than just surface-level experience, but it still felt aligned with the role they were hiring for.
The final round ended up being the biggest hurdle: a full-day on-site with a presentation of a personal project and then mini case studies. During those case studies I talked through my thought process and how I’d troubleshoot and recover when things were failing in the field. I remember trying to stay organized under time pressure because the questions weren’t just about what I’d do, but about how I’d reason through what had gone wrong on site.
2 months ago
Average Negative United States
After a recruiter call, my interviews progressed through multiple stages, and at various points I could feel the momentum shift. I had rounds where the early communication felt present, but once I reached later steps the experience turned into a pattern of disappearing. I’d send follow-ups for feedback and status updates and either get no response or get ghosted right after key interactions.
In one stretch, I did the work of coordinating scheduling, and interviewers still showed up late without much acknowledgment, cutting into time when I could have asked my own questions. I also experienced awkward misalignment where the panel setup didn’t match what I was told in advance, and the process became feel-disorganized rather than organized. Even after finishing everything, I didn’t receive a proper rejection or any real closure; it was just silence for weeks. There were even moments where they specifically asked for references and then nothing followed—references didn’t appear to have been contacted, and eventually I was told they’d chosen someone else.
3 months ago
Difficult Neutral Sunnyvale, CA
My interview loop started with a recruiter call, then quickly went into manager and hiring-manager conversations where the main goal felt like underst…
4 months ago
Average Neutral Sunnyvale, CA
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’…
> 1 year
Average Positive United States
My process was short and split cleanly into two rounds. The first interview wasn’t technical at all, then the second round switched gears and became t…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Flow
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.
Recruiter callOn-siteStructured process
Technical Interviews
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.
PresentationCommunicationTechnical reasoning
Candidate Experience & Communication
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.
CommunicationFeedbackCandidate experience
Behavioral Interviews
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.
BehavioralCultural fitTeam collaboration
Overall Difficulty & Outcome
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.