Five candidate reports on Intuitive Surgical software roles describe recruiter and manager conversations, project walkthroughs, and coding or design questions. Outcomes were mixed: two offers and three rejections.
$143K
Avg. Base Comp
$212K
Avg. Total Comp
2-4 rounds
Typical Rounds
1-6 weeks
Process Length
Candidates describe Intuitive Surgical's software interviews as built around your own background first, then technical questions. Most reports open with a recruiter, HR or hiring manager screen about your background. One candidate had to present thesis work on slides and defend specific technical decisions. Another was asked to walk through their resume and explain why they left each role. Be ready to tell a tight story about what you built and why.
The technical content varies a lot between reports. One candidate got LeetCode-medium problems plus a business math question on unit variable cost. Another had to write a custom Promise implementation, discuss hash maps, and design a Google Forms-style application. An intern candidate built a payroll class on a coder pad, with the interviewer focused on object-oriented structure rather than algorithm tricks. A test engineer candidate was asked about image processing and safety-critical software experience, and described a full-day onsite with panels and a presentation.
Several candidates who were rejected described slow or uneven communication. One waited about a month after an onsite and a reference request. Another felt the recruiter and the hiring managers were looking for different things. Keep your story consistent across conversations and follow up politely. Only one report gives a full timeline, about six weeks from first contact to the end, so treat timing as variable.
Synthesized from 5 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Intuitive Surgical process.
I went through what turned out to be a somewhat disjointed process at Intuitive Surgical. The early rounds moved quickly — recruiter phone screen followed by conversations with an engineering manager and hiring manager. Things felt promising at first, and I got the sense they were actively moving candidates through. Then came the in-person day, which was intense: I interviewed with three different managers plus the recruiter over the course of about an hour. It was a lot of back-to-back conversations, and honestly, the vibe felt scattered. One thing that stood out was how much emphasis they put on understanding my background and motivations. Early on, I was asked to walk through my resume in detail and explain what I'd learned from each role and why I'd decided to move on. It felt like they were really trying to assess fit for the specific position rather than just technical chops. That said, there was a noticeable disconnect throughout. What the recruiter seemed excited about didn't always align with what the hiring managers were probing for. The process had this unpredictable quality to it — some conversations felt substantive and others felt like we were covering the same ground. I never received an offer, and I got the sense there was some internal misalignment about what they were actually looking for in the role.
Prep tip from this candidate
Be prepared to deeply articulate your career narrative and the specific reasons you left each role — they focus heavily on resume walkthrough and fit for their exact position. Also, go in expecting the process to involve multiple managers with potentially different priorities, so stay consistent in your messaging across rounds.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Intuitive Surgical
How would you evaluate and choose between a fast, simple model and a slower, more accurate one for product recommendations?
| Question | |
|---|---|
| Image Classification Pipeline | |
| Alternative Vendor Tradeoff | |
| Your Strengths and Weaknesses | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Prime to N | |
| Flight Records | |
| Total Spent on Products | |
| Job Recommendation | |
| Hurdles In Data Projects | |
| P-value to a Layman | |
| Bagging vs Boosting | |
| Cumulative Distribution | |
| Retailer Data Warehouse | |
| Size of Joins | |
| Detecting ECG Tachycardia Runs | |
| Last Transaction | |
| The Brackets Problem | |
| Always Excited Users | |
| Google Maps Improvement | |
| Valid Anagram | |
| Sort Strings | |
| Brain Cancer Treatment Outcomes | |
| String Mapping | |
| Sum to Zero | |
| Flatten JSON | |
| Cumulative Reset | |
| Find Duplicate Numbers in a List | |
| Customer Success vs. Free Trial |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report starting with a recruiter phone screen or a short call with the hiring manager. These conversations covered general background, resume projects, and company context. One intern candidate described a 30-minute conversational call. Expect to summarize your projects and motivations clearly.
Some candidates describe further conversations with an engineering manager or hiring manager. One was asked to walk through their resume and explain what they learned and why they left each role. Another presented thesis slides and answered detailed follow-ups about technical decisions. Preparation should center on defending your own choices.
Technical rounds differ between reports. Candidates mention LeetCode-medium problems, a custom Promise implementation, hash map questions, an object-oriented payroll class, and a Google Forms-style system design question. One also got a business math question. Practice fundamentals broadly rather than expecting one fixed format.
Two candidates describe in-person days. One reports an eight-hour onsite in Sunnyvale with behavioral, coding, and design questions, panels, and a presentation. Another reports back-to-back meetings with three managers plus the recruiter. Not every candidate reports an onsite, so this stage may depend on the role.
Outcomes were mixed: two offers and three rejections across the reports. One candidate was asked for references the day after the onsite, then heard nothing for about a month. Another said feedback was sparse after technical rounds. An intern candidate got an offer about three weeks after the final interview.
