Software Verification Engineering Manager

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (maybe combine Required Qualifications and Preferred Qualifications?), Benefits, Pay, Schedule. Must include only sections with real content. We have content: - About The Role: paragraph(s) describing role. - Responsibilities: bullet list under "Your Responsibilities Will Include". Need to extract each bullet. - Required Qualifications: list of qualifications. - Preferred Qualifications: list. - Work model, sponsorship, relocation: includes work model (on-site at least four days per week), no sponsorship, relocation assistance not available but may be considered. This could go under Schedule? Actually schedule is about work model (on-site days). Could be a Schedule section: "On-site work model requiring employees to be in our Santa Clara or Valencia office at least four days per week." Also mention no sponsorship, relocation not available. - Pay: Minimum Salary: $116600 Maximum Salary: $221500. Also note compensation varies etc. We should include Pay section with that info. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. We have salary range, so Pay section is appropriate. Benefits: Not explicitly listed besides mention of core and optional employee benefits but no details. The posting says "the value of core and optional employee benefits offered by Boston Scientific (BSC) – see www.bscbenefitsconnect.com—will vary based on actual location". That's not specific benefits; it's a reference. Should we include Benefits section? The rule: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The benefits mention is vague; not specific benefits. So we should NOT create a Benefits section. Schedule: we have work model details: on-site at least four days per week. That's specific. So Schedule section appropriate. We also have location info: Additional Location(s): US-CA-San Jose; US-CA-Santa Clara; US-CA-Valencia. Also earlier mention Santa Clara or Valencia office. Could be included in a short paragraph maybe under About the role? But we need to preserve all substantive information. Could include location in a short

maybe after About the role? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include location and maybe requisition ID in a short p. We must not include boilerplate like EEO, COVID vaccine, etc. Remove those. We must preserve all substantive information: that includes the description about Boston Scientific recognition, the role details, responsibilities, qualifications, preferred qualifications, work model, sponsorship, relocation, salary range, location, maybe the note about compensation varying etc. Also the note about "At BSC, it is not typical for an individual to be hired near the bottom or top of the anticipated salary range listed above." That's substantive; include in Pay section maybe. Also note about variable compensation etc. That's also substantive; include. We must not repeat the job title as a heading. The job title is not given explicitly but we can ignore. We must output only HTML fragment, no /, no markdown. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections that have real content. We have About the role, Responsibilities, Requirements (maybe combine Required and Preferred?), Pay, Schedule. Could also have Qualifications? The instruction list includes Requirements, Qualifications, Skills as possible headings. We could use Requirements for required qualifications, and maybe Qualifications for preferred? Or combine both under Requirements? Better to separate: Required Qualifications under

Requirements

, Preferred Qualifications under

Qualifications

. Or we could use Skills for preferred? But we have both required and preferred; we can use Requirements for required, Qualifications for preferred. We must not create Skills section unless there is specific skills content; we could put some skills under Qualifications but not needed. We need to use

• for any list of duties/requirements/benefits. So for Responsibilities, Required Qualifications, Preferred Qualifications we need lists. We need to use

  for prose. We must not repeat the job title as heading. We must not include Job ID/requisition numbers as headings; we can fold them into a short

  . We must remove boilerplate: EEO, COVID vaccine, etc. Let's extract content. About The Role: Paragraph: "Boston Scientific was recognized by Forbes as one of the Best Workplaces for Engineers in 2026, reflecting a culture where engineers do meaningful work. This position is responsible for leading the Neuromodulation R&D Software Verification team, with a focus on verification and automated testing of medical software applications. This hands-on engineering management role combines people leadership with active technical contribution. Approximately 50% of the role is focused on leading, developing and supporting a team of engineers, while the remaining 50% is dedicated to hands-on software engineering, including test development, automated testing, technical reviews and code reviews. The Software Verification Engineering Manager plays an active role in delivering the efficient, high-quality design, development and testing of critical medical software while building technical capability and driving excellence across the team." We can keep as one or two paragraphs. Responsibilities list (from "Your Responsibilities Will Include"): - Lead, manage and mentor R&D software verification team members, fostering a culture of innovation, technical excellence and continuous development. - Ensure high-quality R&D functional deliverables, support technical projects of significant scope and maintain technical excellence across product and technology integration activities. - Develop and monitor department budgets; determine appropriate staffing levels, schedules and resources; and develop and manage resource plans for R&D initiatives. - Define project- and program-level verification strategies for assessing, documenting, modifying and testing integrated medical devices. - Build strong cross-functional partnerships with quality, regulatory, project management, manufacturing, marketing and other teams to drive results. - Present project and technical updates and strategic recommendations to senior management, communicating clearly with stakeholders at key milestones. - Ensure compliance with applicable regulatory requirements and standards throughout the product life cycle while monitoring relevant industry trends and technological advancements. - Lead technology integration and knowledge transfer within the area of responsibility and drive the development and continuous improvement of department tools and methodologies. - Develop project investment proposals and business cases as needed. - Develop test plans and test procedures and write and review automated functional and end-to-end tests. - Participate in peer code and design reviews, providing architectural, verification and testability feedback. We need to ensure each bullet is a

• . Required Qualifications list: - Bachelor's degree or higher in software engineering, computer engineering, computer science or related technical field. - Minimum of 10 years' experience with a bachelor's degree or minimum of 6 years' experience with a master's degree. - Minimum of 4 years' experience testing applications across Android, iOS, Windows or Android tablet platforms, including a minimum of 2 years' experience using Python. - Minimum of 3 years' experience in leadership, supervisory, project management or people management roles, including demonstrated ability to influence others to drive technical results. - Demonstrated success leading teams of six or more engineers, managing complex projects and delivering results in sustaining, integration or new product development environments. - Experience in a regulated development environment developing automated and manual verification tests; medical device experience preferred. - Hands-on knowledge of automated testing for Android or iOS applications. - Proven technical leadership in product and process design. - Sound technical judgment with a demonstrated ability to synthesize input from multiple and varied sources, draw conclusions and make recommendations. - Strong leadership, communication, collaboration and organizational skills. - Demonstrated effectiveness working with minimal direction in a global, matrixed and fast-paced environment. Preferred Qualifications list: - Proven ability to build and sustain effective partnerships with cross-functional stakeholders across and beyond product development. - Experience collaborating with and leading initiatives across global R&D organizations with direct or dotted-line reporting teams. - Demonstrated ability to prioritize resources and balance competing needs across multiple projects and strategic priorities. - Proven track record of leading organizational and change management initiatives through successful implementation. - Excellent written and verbal communication skills, with the ability to lead complex technical discussions confidently and influence stakeholders at all levels of the organization. Work model, sponsorship, relocation: - Work model: on-site work model requiring employees to be in our Santa Clara or Valencia office at least four days per week. - Sponsorship: Boston Scientific will not offer sponsorship or take over sponsorship of an employment visa for this position at this time. - Relocation: Relocation assistance is not available for this position at this time but may be considered. We can put these in Schedule section? Actually schedule is about work days. Could include sponsorship and relocation under a separate section? The instruction only mentions sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to fit sponsorship/relocation somewhere. Could be part of Schedule? Not exactly. Could be part of About the role? Or we could create a short

  after About the role for metadata like location, work model, sponsorship, relocation. The instruction says: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can put work model, sponsorship, relocation in a short

  (maybe as a paragraph). That seems acceptable. Pay section: include salary range and notes about compensation. Pay: Minimum Salary: $116600 Maximum Salary: $221500. Also note: "The anticipated compensation listed above and the value of core and optional employee benefits offered by Boston Scientific (BSC) – see www.bscbenefitsconnect.com—will vary based on actual location of the position and other pertinent factors considered in determining actual compensation for the role. Compensation will be commensurate with demonstrable level of experience and training, pertinent education including licensure and certifications, among other relevant business or organizational needs. At BSC, it is not typical for an individual to be hired near the bottom or top of the anticipated salary range listed above. Compensation for non-exempt (hourly), non-sales roles may also include variable compensation from time to time (e.g., any overtime and shift differential) and annual bonus target (subject to plan eligibility and other requirements). Compensation for exempt, non-sales roles may also include variable compensation, i.e., annual bonus target and long-term incentives (subject to plan eligibility and other requirements)." We should include all that as prose in Pay section. We should not include Benefits section because no specific benefits. We should not include Skills section. Thus sections: About the role (

  About the role

  ), Responsibilities (

  Responsibilities

  ), Requirements (

  Requirements

  ), Qualifications (

  Qualifications

  ), Pay (

  Pay

  ), Schedule (

  Schedule

  ). Also maybe a short

  for location and work model etc. But we already have Schedule for work model; we could put location in that paragraph as well. But schedule section should contain the work model details (on-site at least four days per week). Could also include location info? The location is separate but we could include in schedule paragraph: "This role follows an on-site work model requiring employees to be in our Santa Clara or Valencia office at least four days per week. Additional locations include San Jose, Santa Clara, and Valencia." However the posting says Additional Location(s): US-CA-San Jose; US-CA-Santa Clara; US-CA-Valencia. So we can mention those. Sponsorship and relocation could be placed in a short

  after schedule or within schedule? Might be better to put them in a short

  after schedule as metadata. But we must not create extra headings for them. So we can just add a

  after schedule containing: "Boston Scientific will not offer sponsorship or take over sponsorship of an