Program Director Digital Transformation
Intuitive · Sunnyvale, CA · 1 mo ago
On-siteBusiness Development$217k–$326k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually we have Company Description, Job Description, Key Responsibilities, Qualifications (Required, Preferred), Additional Information (some may be boilerplate). We must not include boilerplate like EEO, legal, etc. Also we must not repeat job title as heading. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content.
We have content: Company Description (intro). Could map to "About the role"? Actually "About the role" could be company description + job description summary. We'll put a section
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content.
We have content: Company Description (intro). Could map to "About the role"? Actually "About the role" could be company description + job description summary. We'll put a section About the role
with paragraphs from Company Description and Job Description (the first paragraph describing role). We must preserve all substantive info, not invent.
We have "Key Responsibilities" list: we can put under Responsibilities
with - each bullet.
We have "Qualifications" with Required and Preferred. Could combine into
Qualifications
with sub-sections? But we only allowed headings from list; we could still include for Required and Preferred inside that section. Or we could split into Requirements and Skills? The list includes Requirements, Qualifications, Skills. We have qualifications (education, experience). Could put under
Qualifications
. We'll include required and preferred as paragraphs.
We have "Additional Information" includes vaccination note, export controls, EEO, etc. Many are boilerplate; we should remove EEO, legal, etc. Vaccination note maybe substantive? It says "Due to the nature of our business and the role, please note that Intuitive and/or your customer(s) may require that you show current proof of vaccination against certain diseases including COVID-19. Details can vary by role." That's specific; we can keep that as a note maybe under a section like "Additional Information" but we don't have that heading in allowed list. Could we put under "Requirements"? Not exactly. Could we put under "Qualifications"? Not ideal. Maybe we can create a after Qualifications for that note. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings. It also says "include a section ONLY when the posting has real, specific content for it". So we can create sections for those headings only if we have content. We have content for About the role, Responsibilities, Qualifications. We might also have Pay: they gave Base Salary Range Region 1 and Region 2. That's specific pay info. So we should include a Pay section. Also Schedule: they gave Shift: Day Workplace Type: Purposeful Onsite - This job requires being onsite for leader-defined events and activities which could be monthly/annually. Onsite frequency may increase based on business need. That's schedule info. So we can include Schedule section.
Benefits: not explicitly listed; they mention "We provide market-competitive compensation packages, inclusive of base pay, incentives, benefits, and equity." That's vague; not specific benefits. So we should not create Benefits section because no specific content.
Skills: not explicitly listed separate from qualifications; we could omit.
Requirements: we could treat qualifications as requirements; but we already have Qualifications section. Could also have Requirements section for required qualifications; but we must not duplicate. Probably better to have Qualifications section covering both required and preferred. The list includes Requirements as possible heading; but we can choose to use Qualifications only. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid using other headings, but says use those for section headings. Likely they expect us to use those headings where appropriate. We have content for Requirements (required qualifications) and maybe Skills (preferred qualifications?). But we can combine.
Let's decide: Use About the role, Responsibilities, Qualifications, Pay, Schedule. That seems sufficient.
We must not include boilerplate like EEO, export controls, etc. Vaccination note maybe considered substantive; we could include it under Additional Information but we don't have that heading. Could we include it under Qualifications? Not really. Could we include it under Responsibilities? No. Could we include it under About the role? Not appropriate. Maybe we can include it as a paragraph after Qualifications but before Pay, without a heading. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid having paragraphs without headings. So we can add a
for vaccination note.
We must remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Also remove "Job Description Job Description" duplication.
Now craft HTML.
Start with
About the role
then paragraphs: combine Company Description and the first part of Job Description (the paragraph describing role). Let's extract:
Company Description: "It started with a simple idea: what if surgery could be less invasive and recovery less painful? Nearly 30 years later, that question still fuels everything we do at Intuitive. As a global leader in robotic-assisted surgery and minimally invasive care, our technologies—like the da Vinci surgical system and Ion—have transformed how care is delivered for millions of patients worldwide. We’re a team of engineers, clinicians, and innovators united by one purpose: to make surgery smarter, safer, and more human. Every day, our work helps care teams perform with greater precision and patients recover faster, improving outcomes around the world. The problems we solve demand creativity, rigor, and collaboration. The work is challenging, but deeply meaningful—because every improvement we make has the potential to change a life. If you’re ready to contribute to something bigger than yourself and help transform the future of healthcare, you’ll find your purpose here."
Job Description first paragraph: "The Program Director Program Director Digital Transformation is a strategic leadership role responsible for driving business process transformation across global operations through the successful design, implementation, adoption, and sustainment of enterprise systems and digital capabilities. This leader serves as the primary bridge between Operations and Technology, ensuring business objectives are translated into scalable processes, system capabilities, and operating models that support growth, compliance, operational excellence, and organizational agility. The ideal candidate possesses deep expertise in manufacturing and operational processes, strong business acumen, and the ability to influence and align stakeholders at all levels of the organization."
Note there is duplicate "Program Director Program Director". We should keep the text but maybe fix duplication? We must preserve ALL substantive information; do not invent or summarize away detail. The duplication is likely a mistake in posting; but we should preserve as is? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we remove duplication, we are summarizing away detail (removing a repeated phrase). Might be considered altering. Safer to keep the text exactly as given, including duplication. However it looks odd. But we must preserve. We'll keep as is.
Now Responsibilities: list each bullet from "Key Responsibilities". Let's extract bullet points:
- Program Leadership: Lead Transformation across global manufacturing operations and functions, ensuring alignment on scope, priorities, timelines and deliverables. Bridge business, process and technology to drive transformation and develop global, scalable processes.
- Business Process Excellence: Lead a cross functional team of Manufacturing, Planning, Quality, Warehouse, Finance and Engineering in the design and optimization of end-to-end processes to establish future-state business capabilities, governance, and process standards aligned to enterprise objectives and industry best practice. Facilitate cross-functional workshops and decision-making forums to establish aligned business processes and scalable operating practices.
- Cross Functional Collaboration: Partner closely with IT, Finance, Global Operations COEs and other related functions to ensure solutions meet business objectives while fostering a culture of collaboration, accountability, and continuous improvement. Drive alignment across cross-functional stakeholders to establish global process templates and governance models.
- Program Leadership & Execution: Oversee the planning and execution of global transformation initiatives across multiple workstreams, establishing effective governance, milestone tracking, and reporting to ensure transparent and reliable delivery. Proactively manage risks, dependencies, and organizational impacts, while driving alignment across interconnected enterprise initiatives and identifying opportunities to maximize business value and resources.
- Stakeholder Engagement, Change Management & Communication: Build strong partnerships with functional leaders, site leadership, IT teams, and executive stakeholders across regions and functions to drive alignment, engagement, and adoption of transformation initiatives. Develop and execute communication and change management strategies that support organizational readiness and business outcomes. Translate complex business, operational, and technical concepts into clear, actionable messages, and deliver executive presentations, steering committee updates, and transformation communications that drive informed decision-making and stakeholder commitment.
- Value Realization: Track realization of success metrics, ROI and operational benefits including productivity, quality, inventory optimization, service levels, compliance, and cost performance. Ensure decisions are data-driven and tied to measurable business outcomes.
We'll put each as - .
Now Qualifications: we have Required Qualifications list and Preferred Qualifications list. We'll include both as paragraphs under Qualifications section.
Required Qualifications bullets:
- Bachelor's degree in Industrial Engineering, Mechanical Engineering, Business Administration or related field.
- 12+ years of progressive experience in Manufacturing, Supply Chain, Operations, Business Transformation, or related disciplines.
- Proven leadership experience delivering large-scale ERP or enterprise transformation programs.
- Deep expertise in manufacturing operations, planning, supply chain, quality, or related operational processes.
- Demonstrated experience leading global cross-functional initiatives.
- Strong understanding of business process design, process governance, and operating model transformation.
- Exceptional communication, facilitation, and executive presentation skills.
- Strong analytical, problem-solving, and decision-making capabilities.
- Ability to influence without direct authority and navigate complex organizational dynamics.
Preferred Qualifications bullets:
- Experience with SAP S/4HANA, SAP ME, or related enterprise platforms.
- Experience implementing global process templates and standardized business models.
- Medical device, or regulated industry experience.
- Lean, Six Sigma, APICS, SCOR, or related certifications.
We'll put each as
- inside Qualifications section? The instruction says use
- for any list of duties/requirements/benefits. So we should use lists for qualifications as well. We'll have two sub-lists maybe with headings? But we cannot add extra headings not in list. Could we just make one combined list? Might lose distinction. Could we make two lists with preceding
indicating Required and Preferred? That's okay.
Now Pay: we have Base Salary Range Region 1:$217,400 - $326,000 Base Salary Range Region 2: $184,800 - $277,100. We'll put as
.
Schedule: we have Shift: Day Workplace Type: Purposeful Onsite - This job requires being onsite for leader-defined events and activities which could be monthly/annually. Onsite frequency may increase based on business need. We'll put as
.
Vaccination note: we can add a
after Qualifications maybe before Pay.
Now ensure we don't include any boilerplate like EEO, export controls, etc. Also remove "Additional Information" heading etc.
Now produce HTML fragment.
Let's craft:
About the role
It started with a simple idea: what if surgery could be less invasive and recovery less painful? Nearly 30 years later, that question still fuels everything we do at Intuitive. As a global leader in robotic-assisted surgery and minimally invasive care, our technologies—like the da Vinci surgical system and Ion—have transformed how care is delivered for millions of patients worldwide. We’re a team of engineers, clinicians, and innovators united by one purpose: to make surgery smarter, safer, and more human. Every day, our work
Qualifications
with sub-sections? But we only allowed headings from list; we could still includefor Required and Preferred inside that section. Or we could split into Requirements and Skills? The list includes Requirements, Qualifications, Skills. We have qualifications (education, experience). Could put under
Qualifications
. We'll include required and preferred as paragraphs. We have "Additional Information" includes vaccination note, export controls, EEO, etc. Many are boilerplate; we should remove EEO, legal, etc. Vaccination note maybe substantive? It says "Due to the nature of our business and the role, please note that Intuitive and/or your customer(s) may require that you show current proof of vaccination against certain diseases including COVID-19. Details can vary by role." That's specific; we can keep that as a note maybe under a section like "Additional Information" but we don't have that heading in allowed list. Could we put under "Requirements"? Not exactly. Could we put under "Qualifications"? Not ideal. Maybe we can create aafter Qualifications for that note. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings. It also says "include a section ONLY when the posting has real, specific content for it". So we can create sections for those headings only if we have content. We have content for About the role, Responsibilities, Qualifications. We might also have Pay: they gave Base Salary Range Region 1 and Region 2. That's specific pay info. So we should include a Pay section. Also Schedule: they gave Shift: Day Workplace Type: Purposeful Onsite - This job requires being onsite for leader-defined events and activities which could be monthly/annually. Onsite frequency may increase based on business need. That's schedule info. So we can include Schedule section.
Benefits: not explicitly listed; they mention "We provide market-competitive compensation packages, inclusive of base pay, incentives, benefits, and equity." That's vague; not specific benefits. So we should not create Benefits section because no specific content.
Skills: not explicitly listed separate from qualifications; we could omit.
Requirements: we could treat qualifications as requirements; but we already have Qualifications section. Could also have Requirements section for required qualifications; but we must not duplicate. Probably better to have Qualifications section covering both required and preferred. The list includes Requirements as possible heading; but we can choose to use Qualifications only. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid using other headings, but says use those for section headings. Likely they expect us to use those headings where appropriate. We have content for Requirements (required qualifications) and maybe Skills (preferred qualifications?). But we can combine.
Let's decide: Use About the role, Responsibilities, Qualifications, Pay, Schedule. That seems sufficient.
We must not include boilerplate like EEO, export controls, etc. Vaccination note maybe considered substantive; we could include it under Additional Information but we don't have that heading. Could we include it under Qualifications? Not really. Could we include it under Responsibilities? No. Could we include it under About the role? Not appropriate. Maybe we can include it as a paragraph after Qualifications but before Pay, without a heading. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid having paragraphs without headings. So we can add a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid having paragraphs without headings. So we can add a
for vaccination note. We must remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Also remove "Job Description Job Description" duplication. Now craft HTML. Start with
About the role
then paragraphs: combine Company Description and the first part of Job Description (the paragraph describing role). Let's extract: Company Description: "It started with a simple idea: what if surgery could be less invasive and recovery less painful? Nearly 30 years later, that question still fuels everything we do at Intuitive. As a global leader in robotic-assisted surgery and minimally invasive care, our technologies—like the da Vinci surgical system and Ion—have transformed how care is delivered for millions of patients worldwide. We’re a team of engineers, clinicians, and innovators united by one purpose: to make surgery smarter, safer, and more human. Every day, our work helps care teams perform with greater precision and patients recover faster, improving outcomes around the world. The problems we solve demand creativity, rigor, and collaboration. The work is challenging, but deeply meaningful—because every improvement we make has the potential to change a life. If you’re ready to contribute to something bigger than yourself and help transform the future of healthcare, you’ll find your purpose here." Job Description first paragraph: "The Program Director Program Director Digital Transformation is a strategic leadership role responsible for driving business process transformation across global operations through the successful design, implementation, adoption, and sustainment of enterprise systems and digital capabilities. This leader serves as the primary bridge between Operations and Technology, ensuring business objectives are translated into scalable processes, system capabilities, and operating models that support growth, compliance, operational excellence, and organizational agility. The ideal candidate possesses deep expertise in manufacturing and operational processes, strong business acumen, and the ability to influence and align stakeholders at all levels of the organization." Note there is duplicate "Program Director Program Director". We should keep the text but maybe fix duplication? We must preserve ALL substantive information; do not invent or summarize away detail. The duplication is likely a mistake in posting; but we should preserve as is? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." If we remove duplication, we are summarizing away detail (removing a repeated phrase). Might be considered altering. Safer to keep the text exactly as given, including duplication. However it looks odd. But we must preserve. We'll keep as is. Now Responsibilities: list each bullet from "Key Responsibilities". Let's extract bullet points: - Program Leadership: Lead Transformation across global manufacturing operations and functions, ensuring alignment on scope, priorities, timelines and deliverables. Bridge business, process and technology to drive transformation and develop global, scalable processes. - Business Process Excellence: Lead a cross functional team of Manufacturing, Planning, Quality, Warehouse, Finance and Engineering in the design and optimization of end-to-end processes to establish future-state business capabilities, governance, and process standards aligned to enterprise objectives and industry best practice. Facilitate cross-functional workshops and decision-making forums to establish aligned business processes and scalable operating practices. - Cross Functional Collaboration: Partner closely with IT, Finance, Global Operations COEs and other related functions to ensure solutions meet business objectives while fostering a culture of collaboration, accountability, and continuous improvement. Drive alignment across cross-functional stakeholders to establish global process templates and governance models. - Program Leadership & Execution: Oversee the planning and execution of global transformation initiatives across multiple workstreams, establishing effective governance, milestone tracking, and reporting to ensure transparent and reliable delivery. Proactively manage risks, dependencies, and organizational impacts, while driving alignment across interconnected enterprise initiatives and identifying opportunities to maximize business value and resources. - Stakeholder Engagement, Change Management & Communication: Build strong partnerships with functional leaders, site leadership, IT teams, and executive stakeholders across regions and functions to drive alignment, engagement, and adoption of transformation initiatives. Develop and execute communication and change management strategies that support organizational readiness and business outcomes. Translate complex business, operational, and technical concepts into clear, actionable messages, and deliver executive presentations, steering committee updates, and transformation communications that drive informed decision-making and stakeholder commitment. - Value Realization: Track realization of success metrics, ROI and operational benefits including productivity, quality, inventory optimization, service levels, compliance, and cost performance. Ensure decisions are data-driven and tied to measurable business outcomes. We'll put each as- inside Qualifications section? The instruction says use
- for any list of duties/requirements/benefits. So we should use lists for qualifications as well. We'll have two sub-lists maybe with headings? But we cannot add extra headings not in list. Could we just make one combined list? Might lose distinction. Could we make two lists with preceding
indicating Required and Preferred? That's okay. Now Pay: we have Base Salary Range Region 1:$217,400 - $326,000 Base Salary Range Region 2: $184,800 - $277,100. We'll put as
. Schedule: we have Shift: Day Workplace Type: Purposeful Onsite - This job requires being onsite for leader-defined events and activities which could be monthly/annually. Onsite frequency may increase based on business need. We'll put as
. Vaccination note: we can add a
after Qualifications maybe before Pay. Now ensure we don't include any boilerplate like EEO, export controls, etc. Also remove "Additional Information" heading etc. Now produce HTML fragment. Let's craft:
About the role
It started with a simple idea: what if surgery could be less invasive and recovery less painful? Nearly 30 years later, that question still fuels everything we do at Intuitive. As a global leader in robotic-assisted surgery and minimally invasive care, our technologies—like the da Vinci surgical system and Ion—have transformed how care is delivered for millions of patients worldwide. We’re a team of engineers, clinicians, and innovators united by one purpose: to make surgery smarter, safer, and more human. Every day, our work
- for any list of duties/requirements/benefits. So we should use lists for qualifications as well. We'll have two sub-lists maybe with headings? But we cannot add extra headings not in list. Could we just make one combined list? Might lose distinction. Could we make two lists with preceding