Candidates describe Intuitive Surgical software engineer interviews as a recruiter screen, hiring manager conversations, and a technical round. Reports mention resume deep dives, project presentations, JavaScript coding and OOP design.
$158K
Avg. Base Comp
$214K
Avg. Total Comp
2-4 rounds
Typical Rounds
1-6 weeks
Process Length
Candidate reports for Intuitive Surgical software engineering roles share one theme: interviewers probe your background closely. One software engineer says the hiring manager asked about coursework and past projects, then had them present thesis work on slides and pushed hard on the reasoning behind technical decisions. Another was asked to walk through their resume in detail, explaining what they learned in each role and why they moved on. Prepare a tight career narrative and be ready to defend your choices.
Coding questions vary by report. One candidate received LeetCode-medium problems alongside a business-math question about unit variable cost. Another was asked to write a custom Promise implementation, discuss hash maps, and sketch a Google Forms-style system design. An intern reported a coder-pad exercise building a payroll class, focused on object-oriented structure. A test engineer reported an onsite with panels and a presentation, plus a question about image processing experience and an interest in safety-critical software.
Outcomes were mixed: two offers and several rejections across the reports. Several candidates describe slow or sparse communication after interviews, and one reports a long wait after an onsite. Ask the recruiter about timelines early and follow up politely. Because only a handful of reports exist and they cover different roles, treat the details as examples rather than a fixed process.
Synthesized from 6 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 | |
| Valid Anagram | |
| Google Maps Improvement | |
| Total Transactions | |
| String Mapping | |
| Sort Strings | |
| Brain Cancer Treatment Outcomes | |
| Sum to Zero | |
| Flatten JSON | |
| Cumulative Reset | |
| Customer Success vs. Free Trial |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report a recruiter or HR phone screen as the first step, covering general background and basic fit. One candidate says the hiring manager reached out within days of applying. Expect a conversational call, and prepare a concise summary of your experience.
Candidates report a conversation with a hiring manager or engineering manager focused on resume detail, motivations for leaving roles, coursework and projects. One candidate presented thesis slides and faced probing follow-ups on technical decisions, so be ready to defend your reasoning.
Technical rounds reportedly vary. Candidates mention LeetCode-medium problems, a custom Promise implementation, hash map discussion, an OOP payroll class on a coder pad, and a Google Forms-style system design. Coding in your own strongest language and practicing OOP and scalability reasoning may help.
Two candidates report an in-person final day. One described a full-day onsite in Sunnyvale with panels and a presentation, and another described back-to-back meetings with several managers. Consistent messaging about your background and role fit appears to matter. Some candidates also mention slow follow-up and silence afterward, so ask for timelines.
