Principal Technical Writer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements heading and then list required qualifications and maybe preferred qualifications as list items? Or separate Qualifications and Skills? The instruction says we can use those headings if content exists. We have qualifications (required and preferred). Could have a Requirements section with two sub-lists? But we must not create empty sections. We'll include a Requirements section with required qualifications list, and maybe a Qualifications section for preferred? But that might be redundant. Better: Use Requirements for required qualifications, and Qualifications for preferred qualifications. Or combine both under Requirements with subheadings? The instruction says only use those headings; we can have multiple headings. Let's do:
About the role
...
Responsibilities
- ...
Requirements
- ... required qualifications ...
Qualifications
- ... preferred qualifications ...
with that. Schedule: Work model: hybrid requiring at least three days per week in assigned local office. Also location list. So we can include Schedule section with that. Benefits: The posting mentions core and optional employee benefits but does not list specifics. It says "see www.bscbenefitsconnect.com". No specific benefits listed. So we should NOT create Benefits section because no specific content. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Benefits not stated specifically, so omit. We also have location list: Additional Location(s) and work model location list. That's part of Schedule. We need to remove boilerplate: EEO, diversity statements, legal, etc. Also remove "Additional Location(s): ..."? Actually location is relevant for schedule; we can incorporate location info into schedule paragraph. We must preserve all substantive information. So we need to include the location list and work model. Let's extract: About the role: paragraphs after "About The Role". It includes: "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." We'll put that in
. Responsibilities list: bullet points after "Your Responsibilities Will Include". Let's capture each: - 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. We'll put each as
with that info. Schedule: Work model: hybrid requiring employees to be in their assigned local office at least three days per week. This position may be based in our Arbor Lakes, Arden Hills or Maple Grove, Minnesota; Marlborough, Massachusetts; or Spencer, Indiana. Also note relocation assistance not available, sponsorship not offered. That's also schedule/location info. We'll include a
with that. We must not repeat job title as heading. Already not. We must not include Job ID/requisition numbers as headings; we can drop them or fold into short
. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." We can include a short
with Requisition ID: 631193 maybe at end? But it's minor metadata; we could drop it. Safer to drop it. The instruction says preserve ALL substantive information; is Requisition ID substantive? Probably not; it's metadata. Could drop. We'll drop. We also need to remove boilerplate: diversity statement, EEO, legal, etc. Also remove "Learn more at www.bostonscientific.com and follow us on LinkedIn." etc. Also remove COVID vaccination statements etc. Also remove "Boston Scientific transforms lives..." etc. Also remove "As a global medical technology leader..." etc. Also remove "Boston Scientific Corporation has been and will continue to be an equal opportunity employer." etc. Also remove "Please be advised that certain US based positions..." etc. Also remove "Boston Scientific continues to evaluate its policies..." etc. We must keep the substantive content about role, responsibilities, qualifications, pay, schedule. Now produce HTML fragment:
About the role
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.
Responsibilities
- 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.
Requirements
- 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.
Qualifications
- 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