Boston Scientific software engineering interviews reported here combine an initial conversation with technical discussion of C++ internals, memory, runtime tradeoffs, project tools, and code reasoning.
$116K
Avg. Base Comp
$135K
Avg. Total Comp
2-4 rounds
Typical Rounds
1-2 weeks
Process Length
Boston Scientific Software Engineer candidates should prepare for a process that tests how clearly they can discuss practical engineering work as well as core computer-science concepts. One Software Engineer II candidate described an initial behavioral or informational conversation, followed by technical discussion, with a final conversation blending behavioral and technical questions. That candidate’s process added a fourth technical round after interviewers had mixed views, so applicants should treat the extra round as a candidate-specific possibility rather than a standard stage.
For a C++-focused role, be ready to explain implementation details and tradeoffs aloud. Reported questions covered vtables, shared versus unique pointers, stack versus heap memory, inheritance, polymorphism, and the runtimes of algorithms and data structures. The discussion was described as conversational and included a code-review-like emphasis on performance reasoning.
An intern candidate encountered a shorter behavioral conversation and a technical interview with two engineers. That report also included questions about tools or frameworks used in past projects, running LLMs locally, memory management, and tracing tree code. Prepare concrete examples from your own work, then practice narrating your reasoning rather than relying on silent recognition of an answer. The available reports span different levels, so the exact mix of C++ depth and project discussion may vary.
Synthesized from 3 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 Boston Scientific process.
I met a recruiter at a career fair, and they followed up with an interview opportunity a few weeks later. When the call came, I was pleasantly surprised. My interviewer was genuinely friendly and kept things casual throughout, immediately putting me at ease. We dove into my internship experience and what I'd actually learned from the work, not just what looked good on a resume.
The interview ran roughly an hour and felt naturally conversational. There was no attempt to trick me or drill me on obscure edge cases. Instead, my interviewer took the time to explain the role, the job scope, and where it fit in the broader team. They asked questions that felt like genuine exploration rather than box-checking exercises. It seemed like they actually cared about understanding my background and finding real fit.
What really stood out was the process quality. The scheduling platform was intuitive, I got reminders, and communication was clear throughout. No mysterious radio silence or unclear next steps. The whole thing felt organized and respectful.
The main things I'd recommend: prepare solid stories about your internship projects and university work, ask your own questions about the team and role, and go in expecting a conversation rather than a technical interrogation. That's what I got, and it worked out.
Prep tip from this candidate
Prepare detailed stories about your internship and project experience with concrete examples of what you learned. The interview style is conversational rather than technical-heavy, so focus on articulating your background and fit.
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 Boston Scientific
Which model do you pick given 85% and 82% accuracy
| Question | |
|---|---|
| Stakeholder Communication | |
| Justify a Neural Network | |
| Debug Marriage Data | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Prime to N | |
| Flight Records | |
| Retailer Data Warehouse | |
| Hurdles In Data Projects | |
| Job Recommendation | |
| Total Spent on Products | |
| P-value to a Layman | |
| Bagging vs Boosting | |
| Cumulative Distribution | |
| 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 | |
| Find Duplicate Numbers in a List | |
| Cumulative Reset | |
| Customer Success vs. Free Trial |
Synthesized from candidate reports. Individual experiences may vary.
A Software Engineer II candidate reported a first round focused more on behavioral and informational topics. An intern candidate separately reported a roughly 15-minute behavioral conversation about background and interest in the work.
One Software Engineer II candidate reported technical questions on vtable implementation, smart-pointer choices, stack versus heap memory, inheritance, polymorphism, and runtime tradeoffs. That discussion also had a code-review-like component.
An intern candidate reported a 45-minute technical interview with two software engineers covering tools and frameworks used in projects, running LLMs locally, memory management, data structures and algorithms, and tracing tree code.
One Software Engineer II candidate completed a fourth technical round because interviewers had split consensus after a process initially planned for three rounds. This may occur, but the report does not establish it as a standard stage.
