Sr. Data Governance & Quality Systems Lead
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the job description.
Job Title: Sr. Data Governance & Quality Systems Lead (but we must not repeat job title as heading). So we start with content.
We need sections: About the role (maybe from "Your Role" paragraph). Responsibilities (maybe from bullet list of duties). Requirements (maybe from "You're The Right Fit If You have acquired..."). Qualifications (maybe degree etc). Skills (maybe list of skills). Benefits (maybe from Philips Total Rewards). Pay (pay range). Schedule (maybe from "How We Work Together" about in-person 3 days per week). Also maybe "About Philips" could be about company but not required; we can include as "About the company" but not in list; but we only need sections from given list.
We must preserve all substantive info, not invent or summarize away detail. Use - for any list of duties/requirements/benefits. Use
for prose.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Philips Transparency Details" maybe part of Pay/Benefits. Also remove "Additional Information" maybe not needed but includes US work auth etc - that's substantive? Might be considered metadata but maybe we can drop as not required? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can drop minor metadata like US work auth, relocation benefits, etc. But we need to preserve all substantive information. Is work authorization substantive? Probably yes but maybe considered minor metadata. However they said "fold minor metadata into a short
or drop it." So we could include a short
for that info. But we also have to not create sections unless there is real specific content. So we could include a short
under maybe "Additional Information" but not a heading. Safer to drop it? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep US work auth etc. But we can put them in a
without a heading.
Similarly, "Philips Transparency Details" includes pay range and benefits; we already have Pay and Benefits sections.
We also have "About Philips" description; could be included as a
maybe under "About the company" but not required heading. Could be omitted? It's substantive about company mission. Might be considered boilerplate? It's not legal/EEO. It's about company. Might keep as a
without heading.
We need to avoid creating sections with filler like "commensurate with experience". Not present.
Let's extract content.
Sections:
- About the role: from "Your Role" paragraph(s). The text: "Establish and improve the IGT Devices R&D data-governance and QMS framework for software, AI, hardware-generated, and experimental data. Define common standards, decision rights, federated stewardship, metadata, lineage, and quality.Lead the governance and QMS workstream for hospitals, research-sites, vendors, and cross-business-unit data arrangements through controlled release. With clinical and partnership leads and Legal, Privacy, Quality, Security, and Procurement, define intended use, data rights, residency, cross-border constraints, controls, approvals, and obligations.Embed approved requirements in data intake and processing through de-identification, access, data contracts, metadata, lineage, quality checks, release gates, regional or federated processing, retention, and deletion. Enable compliant reuse for software and AI.Operate stewardship, training, metrics, controlled documentation, and audit readiness; coordinating evidence, remediation, and continuous improvement for audits and medical-device inspections."
We can turn into
or maybe bullet list? It's prose; we can keep as
.
- Responsibilities: maybe same as above? Actually "Your Role" is responsibilities. Could treat as Responsibilities section. But we also have "Your Role" heading in text. We could map that to Responsibilities. However we need to follow instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both About the role and Responsibilities if content distinct. But we have only one block describing role. Could split: About the role = overview paragraph maybe first sentence? Responsibilities = detailed duties list. But we don't have clear separation. Safer to have one section: About the role (or Responsibilities). Choose About the role as per instruction list includes both. We could put About the role as overview, Responsibilities as bullet list of duties. Let's parse duties as bullet list:
- Establish and improve the IGT Devices R&D data-governance and QMS framework for software, AI, hardware-generated, and experimental data.
- Define common standards, decision rights, federated stewardship, metadata, lineage, and quality.
- Lead the governance and QMS workstream for hospitals, research-sites, vendors, and cross-business-unit data arrangements through controlled release.
- With clinical and partnership leads and Legal, Privacy, Quality, Security, and Procurement, define intended use, data rights, residency, cross-border constraints, controls, approvals, and obligations.
- Embed approved requirements in data intake and processing through de-identification, access, data contracts, metadata, lineage, quality checks, release gates, regional or federated processing, retention, and deletion.
- Enable compliant reuse for software and AI.
- Operate stewardship, training, metrics, controlled documentation, and audit readiness; coordinating evidence, remediation, and continuous improvement for audits and medical-device inspections.
That seems good.
- Requirements: from "You're The Right Fit If You have acquired 5+ years of experience with a bachelor's degree (or 3+ years with a master's degree) leading data governance and QMS processes in medical devices, healthcare, life sciences, or another regulated environment, including federated stewardship, controlled documentation, training, and audit/inspection readiness."
We can make bullet list? It's a sentence. Could be
.
- Qualifications: from "You have a bachelor’s or master’s degree in data management, informatics, engineering, computer science, quality, regulatory, privacy, or a related field or 9+ years of related experience in lieu of a degree. HITRUST de-identification training or CIPP, CIPM, CIPT, CDMP, CRISC, or ISO/IEC 27559 certifications are a plus."
We can bullet list.
- Skills: from "Your skills include: Strong understanding and application of HIPAA and GDPR, including data residency, localization, cross-border transfer, regional processing, de-identification or anonymization, and re-identification risk. Expertise leading dataset-level privacy-risk assessments and translating findings into documented release decisions, permitted uses, and technical controls. Ability to translate governance and QMS requirements into technical controls and audit evidence; experience with AI/ML data governance required, with AI governance or risk management experience preferred. You’re an effective communicator with strong written and verbal skills and a demonstrated ability to influence and align stakeholders across functions without direct authority."
We can bullet list.
- Benefits: from Philips Total Rewards: "Employees are eligible to participate in our comprehensive Philips Total Rewards benefits program, which includes a generous PTO, 401k (up to 7% match), HSA (with company contribution), stock purchase plan, education reimbursement and much more." Also maybe mention "generous PTO". We'll bullet list.
- Pay: from "The pay range for this position in MN is $129,000 to $205,000. The actual base pay offered may vary within the posted ranges depending on multiple factors including job-related knowledge/skills, experience, business needs, geographical location, and internal equity. In addition, other compensation, such as an annual incentive bonus, sales commission or long-term incentives may be offered." We'll put as
.
- Schedule: from "How We Work Together We believe that we are better together than apart. For our office-based teams, this means working in-person at least 3 days per week. Onsite roles require full-time presence in the company’s facilities. Field roles are most effectively done outside of the company’s main facilities, generally at the customers’ or suppliers’ locations. This is an office role." So schedule: in-person at least 3 days per week, office role. We'll bullet list maybe.
Now we need to output HTML fragment only, no /, no markdown fences.
We'll include headings
for each section we have content.
Order: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We must not repeat job title as heading.
We must not include Job ID etc.
We may include a short
for minor metadata like US work auth etc. But we could drop as minor. However instruction: preserve ALL substantive information; do NOT invent or summarize away detail. US work auth is substantive? Might be considered a requirement. But we could include it under Requirements as a bullet? It says "US work authorization is a precondition of employment. The company will not consider candidates who require sponsorship for a work-authorized visa, now or in the future." That's a requirement. So we should include it. Could add to Requirements bullet list.
Also "Company relocation benefits will not be provided for this position. For this position, you must reside in or within commuting distance to Plymouth, MN." That's also requirement/location. Could add to Requirements.
Also "#ConnectedCare" maybe ignore.
Also "This requisition is expected to stay active for 45 days but may close earlier if a successful candidate is selected or business necessity dictates. Interested candidates are encouraged to apply as soon as possible to ensure consideration." That's application instruction; we should remove.
Also "Philips is an Equal Employment and Opportunity Employer including Disability/Vets and maintains a drug-free workplace." That's EEO boilerplate; remove.
Also "Learn more about our business.Discover our rich and exciting history.Learn more about our purpose.Learn more about our culture." That's promotional; maybe we can keep as a short
under About Philips? Not required heading. Could drop as boilerplate? It's not legal/EEO but it's promotional. Might be considered filler. Safer to drop.
Thus we keep substantive content: role description, responsibilities, requirements, qualifications, skills, benefits, pay, schedule, plus maybe location/work auth.
We'll add location/work auth under Requirements as bullet items.
Now craft HTML.
We'll use
About the role
then maybe a brief overview? But we already have Responsibilities bullet list covering duties. Could keep About the role as a short paragraph summarizing: "As the Sr. R&D Data Governance & QMS Manager, you will establish the data readiness, governance, and quality processes that serve as the foundation for scalable AI innovation, ensuring datasets, partnerships, and platforms are compliant, reusable, and ready to support growth across multiple programs worldwide." That's from first paragraph of job description. We'll keep that as About the role.
Responsibilities: bullet list as above.
Requirements: bullet list:
- 5+ years of experience with a bachelor's degree (or 3+ years with a master's degree) leading data governance and QMS processes in medical devices, healthcare, life sciences, or another regulated environment, including federated stewardship, controlled documentation, training, and audit/inspection readiness.
- US work authorization is a precondition of employment; the company will not consider candidates who require sponsorship for a work-authorized visa, now or in the future.
- Must reside in or within commuting distance to Plymouth, MN; relocation benefits not provided.
Qualifications: bullet list:
- Bachelor’s or master’s degree in data management, informatics, engineering
for prose. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Philips Transparency Details" maybe part of Pay/Benefits. Also remove "Additional Information" maybe not needed but includes US work auth etc - that's substantive? Might be considered metadata but maybe we can drop as not required? The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can drop minor metadata like US work auth, relocation benefits, etc. But we need to preserve all substantive information. Is work authorization substantive? Probably yes but maybe considered minor metadata. However they said "fold minor metadata into a short
or drop it." So we could include a short
for that info. But we also have to not create sections unless there is real specific content. So we could include a short
under maybe "Additional Information" but not a heading. Safer to drop it? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep US work auth etc. But we can put them in a
without a heading. Similarly, "Philips Transparency Details" includes pay range and benefits; we already have Pay and Benefits sections. We also have "About Philips" description; could be included as a
maybe under "About the company" but not required heading. Could be omitted? It's substantive about company mission. Might be considered boilerplate? It's not legal/EEO. It's about company. Might keep as a
without heading. We need to avoid creating sections with filler like "commensurate with experience". Not present. Let's extract content. Sections: - About the role: from "Your Role" paragraph(s). The text: "Establish and improve the IGT Devices R&D data-governance and QMS framework for software, AI, hardware-generated, and experimental data. Define common standards, decision rights, federated stewardship, metadata, lineage, and quality.Lead the governance and QMS workstream for hospitals, research-sites, vendors, and cross-business-unit data arrangements through controlled release. With clinical and partnership leads and Legal, Privacy, Quality, Security, and Procurement, define intended use, data rights, residency, cross-border constraints, controls, approvals, and obligations.Embed approved requirements in data intake and processing through de-identification, access, data contracts, metadata, lineage, quality checks, release gates, regional or federated processing, retention, and deletion. Enable compliant reuse for software and AI.Operate stewardship, training, metrics, controlled documentation, and audit readiness; coordinating evidence, remediation, and continuous improvement for audits and medical-device inspections." We can turn into
or maybe bullet list? It's prose; we can keep as
. - Responsibilities: maybe same as above? Actually "Your Role" is responsibilities. Could treat as Responsibilities section. But we also have "Your Role" heading in text. We could map that to Responsibilities. However we need to follow instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both About the role and Responsibilities if content distinct. But we have only one block describing role. Could split: About the role = overview paragraph maybe first sentence? Responsibilities = detailed duties list. But we don't have clear separation. Safer to have one section: About the role (or Responsibilities). Choose About the role as per instruction list includes both. We could put About the role as overview, Responsibilities as bullet list of duties. Let's parse duties as bullet list: - Establish and improve the IGT Devices R&D data-governance and QMS framework for software, AI, hardware-generated, and experimental data. - Define common standards, decision rights, federated stewardship, metadata, lineage, and quality. - Lead the governance and QMS workstream for hospitals, research-sites, vendors, and cross-business-unit data arrangements through controlled release. - With clinical and partnership leads and Legal, Privacy, Quality, Security, and Procurement, define intended use, data rights, residency, cross-border constraints, controls, approvals, and obligations. - Embed approved requirements in data intake and processing through de-identification, access, data contracts, metadata, lineage, quality checks, release gates, regional or federated processing, retention, and deletion. - Enable compliant reuse for software and AI. - Operate stewardship, training, metrics, controlled documentation, and audit readiness; coordinating evidence, remediation, and continuous improvement for audits and medical-device inspections. That seems good. - Requirements: from "You're The Right Fit If You have acquired 5+ years of experience with a bachelor's degree (or 3+ years with a master's degree) leading data governance and QMS processes in medical devices, healthcare, life sciences, or another regulated environment, including federated stewardship, controlled documentation, training, and audit/inspection readiness." We can make bullet list? It's a sentence. Could be
. - Qualifications: from "You have a bachelor’s or master’s degree in data management, informatics, engineering, computer science, quality, regulatory, privacy, or a related field or 9+ years of related experience in lieu of a degree. HITRUST de-identification training or CIPP, CIPM, CIPT, CDMP, CRISC, or ISO/IEC 27559 certifications are a plus." We can bullet list. - Skills: from "Your skills include: Strong understanding and application of HIPAA and GDPR, including data residency, localization, cross-border transfer, regional processing, de-identification or anonymization, and re-identification risk. Expertise leading dataset-level privacy-risk assessments and translating findings into documented release decisions, permitted uses, and technical controls. Ability to translate governance and QMS requirements into technical controls and audit evidence; experience with AI/ML data governance required, with AI governance or risk management experience preferred. You’re an effective communicator with strong written and verbal skills and a demonstrated ability to influence and align stakeholders across functions without direct authority." We can bullet list. - Benefits: from Philips Total Rewards: "Employees are eligible to participate in our comprehensive Philips Total Rewards benefits program, which includes a generous PTO, 401k (up to 7% match), HSA (with company contribution), stock purchase plan, education reimbursement and much more." Also maybe mention "generous PTO". We'll bullet list. - Pay: from "The pay range for this position in MN is $129,000 to $205,000. The actual base pay offered may vary within the posted ranges depending on multiple factors including job-related knowledge/skills, experience, business needs, geographical location, and internal equity. In addition, other compensation, such as an annual incentive bonus, sales commission or long-term incentives may be offered." We'll put as
. - Schedule: from "How We Work Together We believe that we are better together than apart. For our office-based teams, this means working in-person at least 3 days per week. Onsite roles require full-time presence in the company’s facilities. Field roles are most effectively done outside of the company’s main facilities, generally at the customers’ or suppliers’ locations. This is an office role." So schedule: in-person at least 3 days per week, office role. We'll bullet list maybe. Now we need to output HTML fragment only, no /, no markdown fences. We'll include headings
for each section we have content. Order: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We must not include Job ID etc. We may include a short
for minor metadata like US work auth etc. But we could drop as minor. However instruction: preserve ALL substantive information; do NOT invent or summarize away detail. US work auth is substantive? Might be considered a requirement. But we could include it under Requirements as a bullet? It says "US work authorization is a precondition of employment. The company will not consider candidates who require sponsorship for a work-authorized visa, now or in the future." That's a requirement. So we should include it. Could add to Requirements bullet list. Also "Company relocation benefits will not be provided for this position. For this position, you must reside in or within commuting distance to Plymouth, MN." That's also requirement/location. Could add to Requirements. Also "#ConnectedCare" maybe ignore. Also "This requisition is expected to stay active for 45 days but may close earlier if a successful candidate is selected or business necessity dictates. Interested candidates are encouraged to apply as soon as possible to ensure consideration." That's application instruction; we should remove. Also "Philips is an Equal Employment and Opportunity Employer including Disability/Vets and maintains a drug-free workplace." That's EEO boilerplate; remove. Also "Learn more about our business.Discover our rich and exciting history.Learn more about our purpose.Learn more about our culture." That's promotional; maybe we can keep as a short
under About Philips? Not required heading. Could drop as boilerplate? It's not legal/EEO but it's promotional. Might be considered filler. Safer to drop. Thus we keep substantive content: role description, responsibilities, requirements, qualifications, skills, benefits, pay, schedule, plus maybe location/work auth. We'll add location/work auth under Requirements as bullet items. Now craft HTML. We'll use
About the role
thenmaybe a brief overview? But we already have Responsibilities bullet list covering duties. Could keep About the role as a short paragraph summarizing: "As the Sr. R&D Data Governance & QMS Manager, you will establish the data readiness, governance, and quality processes that serve as the foundation for scalable AI innovation, ensuring datasets, partnerships, and platforms are compliant, reusable, and ready to support growth across multiple programs worldwide." That's from first paragraph of job description. We'll keep that as About the role. Responsibilities: bullet list as above. Requirements: bullet list: - 5+ years of experience with a bachelor's degree (or 3+ years with a master's degree) leading data governance and QMS processes in medical devices, healthcare, life sciences, or another regulated environment, including federated stewardship, controlled documentation, training, and audit/inspection readiness. - US work authorization is a precondition of employment; the company will not consider candidates who require sponsorship for a work-authorized visa, now or in the future. - Must reside in or within commuting distance to Plymouth, MN; relocation benefits not provided. Qualifications: bullet list: - Bachelor’s or master’s degree in data management, informatics, engineering