Principal Full Stack Developer
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections with real specific content. We must not repeat job title as heading. Must not put Job ID/requisition numbers as headings; fold minor metadata into short
or drop it. Remove boilerplate etc. We need to preserve all substantive information. Let's parse the posting. Key sections: - Additional Location(s): US-CA-San Jose; US-CA-Santa Clara (maybe location info) - Diversity - Innovation - Caring - Global Collaboration - Winning Spirit - High Performance (maybe values) - At Boston Scientific, we’ll give you the opportunity... (intro) - About The Role (section) - Work Model, sponsorship, relocation: (details) - Your Responsibilities Will Include (list) - Required Qualifications (list) - Preferred Qualifications (list) - Requisition ID: 635158 (metadata) - Minimum Salary: $116600 Maximum Salary: $221500 (pay info) - 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). (benefits/pay details) - For MA positions: It is unlawful to require or administer a lie detector test for employment. Violators are subject to criminal penalties and civil liability. (legal boilerplate, remove) - Boston Scientific transforms lives through innovative medical technologies... (company description, maybe keep as part of About? Might be considered boilerplate but it's substantive about company; but we might keep as part of About the role? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description might be considered not boilerplate but could be kept? It's not EEO; it's about the company. Might be okay to keep as a paragraph after About the role? However we need to avoid duplication. The posting includes "Boston Scientific transforms lives..." and later "Boston Scientific Corporation has been and will continue to be an equal opportunity employer." That's EEO boilerplate, remove. Also "Please be advised that certain US based positions..." about vaccination, that's legal/health requirement, maybe keep? It's not EEO but it's a requirement; could be considered relevant. However instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Vaccination requirement might be considered legal but it's a condition of employment; maybe keep? Not sure. Safer to remove legal boilerplate like that. The instruction says remove legal boilerplate. So remove vaccination requirement. Thus we keep: Additional Location(s) maybe as a short p. Diversity values maybe as a p. About The Role section content. Work Model, sponsorship, relocation details. Responsibilities list. Required Qualifications list. Preferred Qualifications list. Pay info (salary range). Benefits? The posting mentions benefits via link but not specific benefits; we should not create Benefits section unless posting actually states them. It mentions "value of core and optional employee benefits offered by Boston Scientific (BSC) – see www.bscbenefitsconnect.com—will vary..." That's not specific benefits; it's a reference. So we should not create Benefits section because no specific benefits listed. Schedule? Work model includes hybrid requiring at least three days per week in office. That's schedule info. So we could include a Schedule section with that detail. Or we could incorporate into Work Model section. The instruction: Use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have a Schedule heading if we have schedule info. We have hybrid work model requiring at least three days per week in office. That's schedule. Also mention relocation assistance not available, sponsorship not offered, defined-term position 24 months. That's more about work model/contract. Could be placed under Work Model heading? But we don't have a Work Model heading in list; we have Schedule. Could treat schedule as hybrid work model. We'll create a Schedule section with that info. Pay section: we have salary range. Also mention compensation variable etc. We'll include Pay section with salary range and note about variable compensation etc. Requirements vs Qualifications: The list includes Required Qualifications and Preferred Qualifications. Could map Required Qualifications to Requirements heading, Preferred Qualifications to Qualifications heading? Or we could have Requirements for required, Qualifications for preferred. The instruction says headings: Requirements, Qualifications. So we can use Requirements for required qualifications, Qualifications for preferred qualifications. Skills: Not explicitly listed; maybe we could extract skills from responsibilities? But we should not invent. So we skip Skills section if no specific skills listed. Benefits: we decided not to include. Now we need to output HTML fragment only, no /. Use
for headings, - for lists,
for prose.
We must preserve all substantive information. Let's gather substantive bits:
- Additional Location(s): US-CA-San Jose; US-CA-Santa Clara
- Diversity - Innovation - Caring - Global Collaboration - Winning Spirit - High Performance (maybe as values)
- Intro paragraph: "At Boston Scientific, we’ll give you the opportunity to harness all that’s within you by working in teams of diverse and high-performing employees, tackling some of the most important health industry challenges. With access to the latest tools, information and training, we’ll help you in advancing your skills and career. Here, you’ll be supported in progressing – whatever your ambitions."
- About The Role: paragraph(s) about Glassdoor Best Place to Work 2026 ranking No.15, role description: Principal Full Stack Developer serves as senior technical leader responsible for shaping design and delivery of innovative digital platforms that improve patient outcomes, connect medical devices, enhance clinician experiences worldwide. This role architects and delivers enterprise-grade applications across full stack, from intuitive front-end interfaces to scalable, secure back-end systems and cloud-native microservices. The position plays a critical role in advancing high-performing, compliant digital health and device software solutions while fostering engineering excellence and cross-functional collaboration.
- Work Model, sponsorship, relocation: hybrid work model requiring employees to be in Santa Clara, CA office at least three days per week. No sponsorship or take over sponsorship of employment visa. Relocation assistance not available. Defined-term position with anticipated duration of 24 months from start date.
- Responsibilities: list bullet points (we need to capture each). Let's list them:
1. Lead and coordinate engineering teams to deliver high-quality, scalable full stack solutions aligned to business objectives
2. Own the architecture, design, and delivery of end-to-end software solutions supporting digital health and connected device platforms
3. Define and implement cloud-native architectures using AWS, Azure, and microservices frameworks
4. Drive modernization initiatives, including cloud migration, API-first design, and transition to microservices-based architectures
5. Establish and enforce technical standards, best practices, and scalable design patterns across development teams
6. Develop and oversee complex applications and APIs using modern technologies such as React, TypeScript, Node.js, and Java Spring Boot
7. Partner with DevOps and data engineering teams to enable CI/CD pipelines and integrate analytics and AI-driven capabilities
8. Ensure solutions meet enterprise architecture, cybersecurity, and regulatory requirements, including HIPAA, GDPR, and FDA standards
9. Collaborate with product management, UX, and quality teams to deliver user-centered, high-performing software solutions
10. Mentor engineers and provide technical leadership across planning, estimation, and full software development life cycle execution
- Required Qualifications: list:
1. Bachelor’s or master’s degree in computer science, software engineering, or a related field
2. Minimum of 8 years' experience in software development
3. Minimum of 3 years' experience in a principal, architect, or technical leadership role
4. Deep expertise in full-stack development using Node.js and/or Java, with strong back-end architecture experience and approximately a 40/60 to 50/50 front-end/back-end development mix
5. Proven experience building scalable microservices and distributed systems in AWS and/or Azure environments
6. Proficiency in SQL databases
7. Hands-on experience with containerization and orchestration technologies such as Docker and Kubernetes
8. Strong understanding of security, performance, and accessibility best practices
9. Experience working in Agile/Scrum environments
10. Proven technical leadership and ability to influence across teams
- Preferred Qualifications: list:
1. Experience in medical device, digital health, or other regulated environments
2. Experience with event-driven architectures and streaming technologies such as Kafka or Event Hub
3. Familiarity with observability practices, including logging, metrics, and tracing
4. Experience with performance optimization and application security best practices
5. Exposure to AI/ML technologies and data-driven application development
6. Strong stakeholder management and cross-functional collaboration skills
7. Strong analytical, problem-solving, and communication skills
8. Demonstrated ability to work independently and deliver well-designed, technically sound solutions
- 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 that info in Pay section.
- Schedule: hybrid work model requiring at least three days per week in Santa Clara, CA office. Also note defined-term position 24 months. Could include that.
- Additional location(s) maybe as a p.
- Diversity values maybe as a p.
- Intro paragraph maybe as a p before About the role? Could be part of About the role? But we have About the role heading; we could put intro as a p under About the role? Actually the intro is separate from About The Role heading. We could treat it as a general description before the role. Could put as a p before About the role heading. That's fine.
Now we must not include boilerplate like EEO, vaccination, legal, etc. Also remove duplicated lines. Ensure we don't include "Requisition ID: 635158" as heading; we can fold into a short p or drop. Probably drop it as minor metadata. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can either drop it or include in a p. I'd drop it to keep
for prose. We must preserve all substantive information. Let's gather substantive bits: - Additional Location(s): US-CA-San Jose; US-CA-Santa Clara - Diversity - Innovation - Caring - Global Collaboration - Winning Spirit - High Performance (maybe as values) - Intro paragraph: "At Boston Scientific, we’ll give you the opportunity to harness all that’s within you by working in teams of diverse and high-performing employees, tackling some of the most important health industry challenges. With access to the latest tools, information and training, we’ll help you in advancing your skills and career. Here, you’ll be supported in progressing – whatever your ambitions." - About The Role: paragraph(s) about Glassdoor Best Place to Work 2026 ranking No.15, role description: Principal Full Stack Developer serves as senior technical leader responsible for shaping design and delivery of innovative digital platforms that improve patient outcomes, connect medical devices, enhance clinician experiences worldwide. This role architects and delivers enterprise-grade applications across full stack, from intuitive front-end interfaces to scalable, secure back-end systems and cloud-native microservices. The position plays a critical role in advancing high-performing, compliant digital health and device software solutions while fostering engineering excellence and cross-functional collaboration. - Work Model, sponsorship, relocation: hybrid work model requiring employees to be in Santa Clara, CA office at least three days per week. No sponsorship or take over sponsorship of employment visa. Relocation assistance not available. Defined-term position with anticipated duration of 24 months from start date. - Responsibilities: list bullet points (we need to capture each). Let's list them: 1. Lead and coordinate engineering teams to deliver high-quality, scalable full stack solutions aligned to business objectives 2. Own the architecture, design, and delivery of end-to-end software solutions supporting digital health and connected device platforms 3. Define and implement cloud-native architectures using AWS, Azure, and microservices frameworks 4. Drive modernization initiatives, including cloud migration, API-first design, and transition to microservices-based architectures 5. Establish and enforce technical standards, best practices, and scalable design patterns across development teams 6. Develop and oversee complex applications and APIs using modern technologies such as React, TypeScript, Node.js, and Java Spring Boot 7. Partner with DevOps and data engineering teams to enable CI/CD pipelines and integrate analytics and AI-driven capabilities 8. Ensure solutions meet enterprise architecture, cybersecurity, and regulatory requirements, including HIPAA, GDPR, and FDA standards 9. Collaborate with product management, UX, and quality teams to deliver user-centered, high-performing software solutions 10. Mentor engineers and provide technical leadership across planning, estimation, and full software development life cycle execution - Required Qualifications: list: 1. Bachelor’s or master’s degree in computer science, software engineering, or a related field 2. Minimum of 8 years' experience in software development 3. Minimum of 3 years' experience in a principal, architect, or technical leadership role 4. Deep expertise in full-stack development using Node.js and/or Java, with strong back-end architecture experience and approximately a 40/60 to 50/50 front-end/back-end development mix 5. Proven experience building scalable microservices and distributed systems in AWS and/or Azure environments 6. Proficiency in SQL databases 7. Hands-on experience with containerization and orchestration technologies such as Docker and Kubernetes 8. Strong understanding of security, performance, and accessibility best practices 9. Experience working in Agile/Scrum environments 10. Proven technical leadership and ability to influence across teams - Preferred Qualifications: list: 1. Experience in medical device, digital health, or other regulated environments 2. Experience with event-driven architectures and streaming technologies such as Kafka or Event Hub 3. Familiarity with observability practices, including logging, metrics, and tracing 4. Experience with performance optimization and application security best practices 5. Exposure to AI/ML technologies and data-driven application development 6. Strong stakeholder management and cross-functional collaboration skills 7. Strong analytical, problem-solving, and communication skills 8. Demonstrated ability to work independently and deliver well-designed, technically sound solutions - 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 that info in Pay section. - Schedule: hybrid work model requiring at least three days per week in Santa Clara, CA office. Also note defined-term position 24 months. Could include that. - Additional location(s) maybe as a p. - Diversity values maybe as a p. - Intro paragraph maybe as a p before About the role? Could be part of About the role? But we have About the role heading; we could put intro as a p under About the role? Actually the intro is separate from About The Role heading. We could treat it as a general description before the role. Could put as a p before About the role heading. That's fine. Now we must not include boilerplate like EEO, vaccination, legal, etc. Also remove duplicated lines. Ensure we don't include "Requisition ID: 635158" as heading; we can fold into a short p or drop. Probably drop it as minor metadata. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can either drop it or include in a p. I'd drop it to keep