Principal Technical Writer
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to ensure we don't create sections with filler text. So we will include sections: About the role, Responsibilities, Required Qualifications, Preferred Qualifications, Benefits, Pay, Schedule. Possibly combine Required and Preferred into Requirements? But instruction: use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have separate Required Qualifications and Preferred Qualifications under Qualifications? Could do Qualifications heading with sub-sections? But simpler: Use Requirements heading for required qualifications, and Preferred Qualifications heading for preferred. Or combine both under Qualifications. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we can have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. But we have both required and preferred qualifications; we could put required under Requirements, preferred under Qualifications. That seems fine.
We need to preserve all substantive information: So we need to include the required qualifications list items, and preferred qualifications list items.
We also need to include the work model, sponsorship, relocation info under Schedule? Or maybe under About the role? The schedule section should contain hybrid work model, location, no sponsorship, no relocation. We'll put that.
Benefits: mention core and optional employee benefits, link.
Pay: include salary range and note about compensation varying, bonus, etc.
We must not include boilerplate like EEO, etc. We'll omit the equal opportunity paragraph, the COVID vaccination note, the company description paragraphs (maybe those are boilerplate? They are about company mission; could be considered substantive? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description paragraphs are not explicitly listed as boilerplate, but they are generic marketing. Might be considered boilerplate? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The company description may be considered substantive? It's about the company; but it's not specific to the role. It might be considered boilerplate but not explicitly listed. Safer to keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It does not say to remove company description. However earlier: "Prefer a few substantive sections over many thin ones." The company description is not specific to the role; could be considered filler. I'd lean to omit it to keep focused on role. But we need to be careful not to remove substantive info. The company description is not about the role; it's generic. I'd omit.
Also we need to drop duplicated lines: there may be duplicated lines like "Boston Scientific transforms lives..." etc. We'll omit.
Now construct HTML.
We'll start with About the role
then
with the prose from About The Role section (the paragraph after "About The Role").
Then
Responsibilities
then - each responsibility line.
Then
Requirements
then - each required qualification.
Then
Qualifications
then - each preferred qualification.
Then
Benefits
then about core and optional employee benefits link.
Then
Pay
then with salary range and notes about compensation varying, bonus, long-term incentives, etc.
Then
Schedule
then with hybrid work model, location list, no sponsorship, no relocation.
We must not include Job ID/requisition numbers as headings; we can drop them.
Check for any list of duties/requirements/benefits: we have lists.
Now ensure we don't include filler like "commensurate with experience" etc. In Pay section we have note: "Compensation will be commensurate with demonstrable level of experience and training, pertinent education including licensure and certifications, among other relevant business or organizational needs." That's somewhat filler but it's actual content from posting. It's not a placeholder like "commensurate with experience" but it's a phrase. It's okay.
We also have "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.
We also have variable compensation details.
Now ensure we don't include any duplicated lines.
Let's extract the exact text.
About The Role paragraph:
"Boston Scientific was recognized as a Glassdoor Best Place to Work in 2026, ranking No. 15 on the Top 100 list, reflecting the culture our employees experience every day. Boston Scientific is seeking an experienced Principal Technical Writer to join the Global Quality Systems organization. In this highly visible role, you will lead the development, governance and continuous improvement of enterprise-level procedures, work instructions, training materials and knowledge resources that support Corrective and Preventive Action (CAPA), Product Inquiry Reports (PIR), Nonconformance Event Process (NCEP) and related Global Quality System processes. This incumbent will collaborate with global process stewards, quality leaders, business analysts and digital teams to ensure quality system documentation is clear, compliant, user-focused and audit-ready. In addition, you will own the Corporate CAPA, PIR, NCEP and Nonconforming Material (NCM) SharePoint knowledge environment, establishing best practices for content governance, knowledge management and enterprise-wide communication. This role also plays a critical part in supporting enterprise eQMS implementation activities, Project Guardian initiatives and ongoing Global Quality Systems transformation efforts."
That's the prose.
Responsibilities list (from "Your Responsibilities Will Include"):
- Author, revise and maintain global procedures, work instructions, guidance documents, templates and job aids supporting Global Quality Systems.
- Develop documentation that complies with FDA Quality Management System Regulation (QMSR), 21 CFR Part 820, ISO 13485, EU MDR and other applicable regulatory and internal quality system requirements.
- Drive consistency in terminology, documentation standards, process flows and procedural structure across Corporate Quality processes.
- Partner with global process stewards, business analysts, information technology teams and subject matter experts to develop future-state procedures and user guidance supporting enterprise eQMS implementation.
- Support Project Guardian initiatives by creating standardized work instructions, execution guidance and documentation that enables sustainable corrective actions.
- Own and maintain the Corporate CAPA, PIR, NCEP and NCM SharePoint knowledge environment, ensuring content is accurate, current, accessible and governed according to established standards.
- Develop and maintain learning content and knowledge resources that support adoption of new quality processes, systems and technologies.
- Collaborate with Quality Systems leaders and process stewards to communicate procedural updates and ensure organizational awareness of process changes.
- Identify opportunities to improve documentation quality, usability and efficiency through standardization and continuous improvement.
Required Qualifications list:
- Minimum Bachelor's degree in Technical Communications, Quality, Engineering, Life Sciences, Regulatory Affairs or a related discipline.
- Minimum of 8 years' experience in technical writing within a regulated industry.
- Experience authoring and maintaining controlled procedures, work instructions and quality system documentation.
- Demonstrated ability to translate complex technical concepts into clear, concise and user-focused documentation.
- Strong document management, editing and technical writing skills.
- Proven experience administering SharePoint sites and managing enterprise knowledge content.
- Strong collaboration and communication skills with the ability to work effectively across cross-functional, global teams.
Preferred Qualifications list:
- Demonstrated experience supporting CAPA, nonconformance, complaint handling, field action or other quality management system processes.
- Demonstrated experience supporting enterprise system implementations, including eQMS, PLM, ERP or similar platforms.
- Proven experience using Microsoft Visio, Microsoft 365 applications and learning management systems.
- Familiarity with change management principles and organizational learning methodologies.
- Knowledge of document governance, knowledge management best practices and continuous improvement methodologies.
- Proven experience supporting regulatory inspections or internal and external quality audits.
Benefits: The sentence: "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."
We can put that in Benefits section.
Pay: We have Minimum Salary: $85000 Maximum Salary: $161500. Also note: "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'll include all that.
Schedule: "Work
for prose. We need to ensure we don't create sections with filler text. So we will include sections: About the role, Responsibilities, Required Qualifications, Preferred Qualifications, Benefits, Pay, Schedule. Possibly combine Required and Preferred into Requirements? But instruction: use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have separate Required Qualifications and Preferred Qualifications under Qualifications? Could do Qualifications heading with sub-sections? But simpler: Use Requirements heading for required qualifications, and Preferred Qualifications heading for preferred. Or combine both under Qualifications. The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So we can have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. But we have both required and preferred qualifications; we could put required under Requirements, preferred under Qualifications. That seems fine.
We need to preserve all substantive information: So we need to include the required qualifications list items, and preferred qualifications list items.
We also need to include the work model, sponsorship, relocation info under Schedule? Or maybe under About the role? The schedule section should contain hybrid work model, location, no sponsorship, no relocation. We'll put that.
Benefits: mention core and optional employee benefits, link.
Pay: include salary range and note about compensation varying, bonus, etc.
We must not include boilerplate like EEO, etc. We'll omit the equal opportunity paragraph, the COVID vaccination note, the company description paragraphs (maybe those are boilerplate? They are about company mission; could be considered substantive? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description paragraphs are not explicitly listed as boilerplate, but they are generic marketing. Might be considered boilerplate? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. The company description may be considered substantive? It's about the company; but it's not specific to the role. It might be considered boilerplate but not explicitly listed. Safer to keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It does not say to remove company description. However earlier: "Prefer a few substantive sections over many thin ones." The company description is not specific to the role; could be considered filler. I'd lean to omit it to keep focused on role. But we need to be careful not to remove substantive info. The company description is not about the role; it's generic. I'd omit.
Also we need to drop duplicated lines: there may be duplicated lines like "Boston Scientific transforms lives..." etc. We'll omit.
Now construct HTML.
We'll start with About the role
then
About the role
thenwith the prose from About The Role section (the paragraph after "About The Role"). Then
Responsibilities
then- each responsibility line.
Then
Requirements
then- each required qualification.
Then
Qualifications
then- each preferred qualification.
Then
Benefits
thenabout core and optional employee benefits link. Then
Pay
thenwith salary range and notes about compensation varying, bonus, long-term incentives, etc. Then
Schedule
thenwith hybrid work model, location list, no sponsorship, no relocation. We must not include Job ID/requisition numbers as headings; we can drop them. Check for any list of duties/requirements/benefits: we have lists. Now ensure we don't include filler like "commensurate with experience" etc. In Pay section we have note: "Compensation will be commensurate with demonstrable level of experience and training, pertinent education including licensure and certifications, among other relevant business or organizational needs." That's somewhat filler but it's actual content from posting. It's not a placeholder like "commensurate with experience" but it's a phrase. It's okay. We also have "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. We also have variable compensation details. Now ensure we don't include any duplicated lines. Let's extract the exact text. About The Role paragraph: "Boston Scientific was recognized as a Glassdoor Best Place to Work in 2026, ranking No. 15 on the Top 100 list, reflecting the culture our employees experience every day. Boston Scientific is seeking an experienced Principal Technical Writer to join the Global Quality Systems organization. In this highly visible role, you will lead the development, governance and continuous improvement of enterprise-level procedures, work instructions, training materials and knowledge resources that support Corrective and Preventive Action (CAPA), Product Inquiry Reports (PIR), Nonconformance Event Process (NCEP) and related Global Quality System processes. This incumbent will collaborate with global process stewards, quality leaders, business analysts and digital teams to ensure quality system documentation is clear, compliant, user-focused and audit-ready. In addition, you will own the Corporate CAPA, PIR, NCEP and Nonconforming Material (NCM) SharePoint knowledge environment, establishing best practices for content governance, knowledge management and enterprise-wide communication. This role also plays a critical part in supporting enterprise eQMS implementation activities, Project Guardian initiatives and ongoing Global Quality Systems transformation efforts." That's the prose. Responsibilities list (from "Your Responsibilities Will Include"): - Author, revise and maintain global procedures, work instructions, guidance documents, templates and job aids supporting Global Quality Systems. - Develop documentation that complies with FDA Quality Management System Regulation (QMSR), 21 CFR Part 820, ISO 13485, EU MDR and other applicable regulatory and internal quality system requirements. - Drive consistency in terminology, documentation standards, process flows and procedural structure across Corporate Quality processes. - Partner with global process stewards, business analysts, information technology teams and subject matter experts to develop future-state procedures and user guidance supporting enterprise eQMS implementation. - Support Project Guardian initiatives by creating standardized work instructions, execution guidance and documentation that enables sustainable corrective actions. - Own and maintain the Corporate CAPA, PIR, NCEP and NCM SharePoint knowledge environment, ensuring content is accurate, current, accessible and governed according to established standards. - Develop and maintain learning content and knowledge resources that support adoption of new quality processes, systems and technologies. - Collaborate with Quality Systems leaders and process stewards to communicate procedural updates and ensure organizational awareness of process changes. - Identify opportunities to improve documentation quality, usability and efficiency through standardization and continuous improvement. Required Qualifications list: - Minimum Bachelor's degree in Technical Communications, Quality, Engineering, Life Sciences, Regulatory Affairs or a related discipline. - Minimum of 8 years' experience in technical writing within a regulated industry. - Experience authoring and maintaining controlled procedures, work instructions and quality system documentation. - Demonstrated ability to translate complex technical concepts into clear, concise and user-focused documentation. - Strong document management, editing and technical writing skills. - Proven experience administering SharePoint sites and managing enterprise knowledge content. - Strong collaboration and communication skills with the ability to work effectively across cross-functional, global teams. Preferred Qualifications list: - Demonstrated experience supporting CAPA, nonconformance, complaint handling, field action or other quality management system processes. - Demonstrated experience supporting enterprise system implementations, including eQMS, PLM, ERP or similar platforms. - Proven experience using Microsoft Visio, Microsoft 365 applications and learning management systems. - Familiarity with change management principles and organizational learning methodologies. - Knowledge of document governance, knowledge management best practices and continuous improvement methodologies. - Proven experience supporting regulatory inspections or internal and external quality audits. Benefits: The sentence: "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." We can put that in Benefits section. Pay: We have Minimum Salary: $85000 Maximum Salary: $161500. Also note: "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'll include all that. Schedule: "Work
- each preferred qualification.
Then
- each required qualification.
Then