Clinical Program Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting.
Company Description: description of Intuitive.
Job Description: Primary Function of Position, etc.
Roles And Responsibilities: list of responsibilities.
Qualifications: list.
Preferred Qualifications: list.
Additional Information: includes vaccination requirement, EEO, export controls, etc. Many of these are boilerplate legal/EEO. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove EEO statements, export controls, fair chance, preference for certain states, etc. Also remove "Additional Information" if it's mostly boilerplate. However we need to preserve substantive info: vaccination requirement maybe? 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 substantive? It's a requirement. Could keep as a note. But it's not a standard section like Benefits/Pay/Schedule. Could be placed under a short paragraph maybe under "Additional Information" but we might drop that heading if it's just boilerplate. However the vaccination requirement is substantive. We could include it in a
under maybe a heading like "Requirements" or "Additional Info". But we need to follow instruction: include a section ONLY when the posting has real, specific content for it. So we could have a section "Additional Information" with that vaccination note. But we must avoid filler. The vaccination note is specific. So we can include a section maybe "Additional Information" with that note.
But also there is compensation info: Base Salary Range Region 1: $150,500 - $216,500; Region 2: $127,900 - $184,000; Shift: Day; Workplace Type: Onsite - This job is fully onsite. That's Pay and Schedule info. So we should include Pay and Schedule sections.
Benefits: Not explicitly listed besides "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 unless specific. So skip.
Thus sections: About the role? Could be company description? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which sections have content.
We have company description: could be "About the role" or maybe "About the company". But they said About the role as example. We could put company description under "About the role". Or we could have a separate "Company Description" but not in list. Probably better to use "About the role" for the role description (Primary Function). But we also have responsibilities list. So we could have:
About the role
Primary Function of Position: ...
Then responsibilities list under Responsibilities
with .
Then qualifications under Qualifications
with maybe split into required and preferred? Could combine but we can separate: Required Qualifications and Preferred Qualifications. But headings only from list; we could use "Qualifications" for required and maybe "Preferred Qualifications" as a subsection? Not in list but we could still use Preferred Qualifications
if we want. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. Probably we should stick to those. Could incorporate preferred qualifications under Qualifications as part of same list, maybe with a note "Preferred". But better to separate: we could have Qualifications
for required, and then another Preferred Qualifications
(though not in list). Might be okay. But to be safe, we could combine required and preferred into one Qualifications section, marking preferred items with "(Preferred)". That preserves all info.
Pay: Base Salary Range Region 1 and Region 2. Also mention "Shift: Day". So Pay section: include salary ranges. Schedule: Shift: Day, Workplace Type: Onsite - fully onsite. So Schedule section.
We need to avoid filler like "commensurate with experience". Not present.
We need to remove boilerplate: EEO, export controls, fair chance, preference for certain states, etc. Also remove "Additional Information" if it's just those. But we keep vaccination requirement maybe as a short note under Additional Information or under Qualifications? Could be under "Additional Information" heading. But we might drop that heading and just incorporate vaccination note into Qualifications as a requirement: "Proof of vaccination against certain diseases including COVID-19 may be required." That is a requirement. So we can add to Qualifications list.
Thus final HTML:
About the role
Primary Function of Position: The Senior Clinical Program Manager serves as the strategic and operational partner to Clinical Development & Operations leadership, providing integrated program management across the Clinical Development & Operations portfolio from study startup through regulatory submission. The role partners with Clinical Development & Operations leadership to inform Clinical Development & Operations strategy through integrated planning, scenario analysis, governance, and execution insights, translating strategic direction into coordinated cross-functional plans that enable successful program execution. Reporting to the Program Management & Operations organization, the Senior Clinical Program Manager partners across Clinical Development & Operations, Regulatory Affairs, Medical Affairs, CMC, Nonclinical, Quality, Commercial, and external partners to integrate timelines, risks, dependencies, and key decisions into unified program plans. In partnership with Enterprise Program Management, the role establishes Clinical Development & Operations governance and ensures cross-functional risks, dependencies, and decision requests are appropriately elevated through enterprise governance to support informed decision-making and coordinated execution.
Responsibilities
- Support the Program Management & Operations team in creating and implementing Clinical Development & Operations governance processes, including governance forums, operating cadences, decision pathways, program reporting, and the RAID framework.
- Facilitate Clinical Development & Operations & Operations governance by preparing governance materials, maintaining clinical RAID and decision logs, capturing actions and decisions, monitoring follow-through, and escalating cross-functional risks and decision requests through enterprise governance, as appropriate.
- Develop, maintain, and communicate integrated timelines across the clinical portfolio, ensuring alignment of milestones, dependencies, critical path activities, and cross-functional deliverables.
- Coordinate program-level execution across Study Leads, Clinical Operations, Data Management, Biostatistics, Safety, Regulatory Affairs, Medical Writing, Quality, and external partners, providing hands-on project management support to individual studies as needed.
- Monitor portfolio execution, proactively identifying schedule impacts, resource constraints, cross-study dependencies, and operational risks, and facilitate development of mitigation plans.
- Develop executive-ready portfolio reporting that communicates program health, milestone performance, critical path status, key risks, decision requests, and recommended actions.
- Identify portfolio trends and opportunities to strengthen planning, governance, reporting, and operational effectiveness across Clinical Development & Operations.
- Support regular functional-area budget management in coordination with Clinical Development & Operations Functional Area Team Leads and PM&O by tracking actual and forecasted accruals, invoices, purchase orders, and inputs to the Annual Operations Budget Planning Cycle.
- Support CRO and Vendor oversight by: incorporating vendor updates into project plans and governance materials; maintaining visibility and supporting management of purchase orders, change orders, invoices, key contract terms, and performance commitments; and coordinating business reviews and operational follow-up across internal functions.
- Drive adoption of standardized project management tools, templates, dashboards, reporting practices, and workflow automation that improve portfolio visibility, consistency, and execution.
Qualifications
- Bachelor's degree in Pharma/Life Sciences, or a related field (or equivalent experience). An advanced degree is preferred.
- Minimum 10 years of program or project management experience in pharmaceutical, biotechnology, medical device, or CRO industry supporting Clinical Development & Operations through NDA regulatory submissions.
- Demonstrated success leading cross-functional planning and execution across multiple concurrent clinical studies, including integrated planning, critical path management, and dependency management.
- Experience partnering with Clinical Development & Operations, CMC, Regulatory Affairs, and Quality leadership to support governance, portfolio planning, and executive decision-making.
- Experience supporting late-stage Clinical Development & Operations programs and familiarity with Clinical Development & Operations processes from start-up through close-out.
- Expertise in integrated timeline management, risk and issue management, resource coordination, and cross-functional execution.
- Strong executive communication and presentation skills, with the ability to deliver clear, actionable recommendations to senior leadership; High emotional intelligence and the ability to build trusted partnerships across technical and business functions.
- Proficiency with Smartsheet, including integrated project planning, dashboards, reporting, and workflow automation.
- Proof of vaccination against certain diseases including COVID-19 may be required (details vary by role).
- Preferred: Experience working with CROs, vendors, and cross-functional development teams.
- Preferred: PMP or comparable project management certification.
- Preferred: Familiarity with procurement, contract, and financial management systems (e.g., Coupa, iValua, SAP, Ariba, or equivalent).
Pay
- Base Salary Range Region 1: $150,500 - $216,500
- Base Salary Range Region 2: $127,900 - $184,000
Schedule
- Shift: Day
- Workplace Type: Onsite - This job is fully onsite.
We need to ensure no duplicate lines. Also ensure we didn't include any boilerplate like EEO etc. We removed them.
Check that we preserved all substantive info: company description included in About the role? We included Primary Function but not the company description paragraph at start. The company description is separate: "Company Description It started with a simple idea..." That is substantive about the company. Should we include that? The instruction says use headings like About the role, Responsibilities, etc. Could include company description under About the role as well, maybe preceding the Primary Function. So we should incorporate that company description into About the role section. Let's add it as a paragraph before
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Company Description: description of Intuitive. Job Description: Primary Function of Position, etc. Roles And Responsibilities: list of responsibilities. Qualifications: list. Preferred Qualifications: list. Additional Information: includes vaccination requirement, EEO, export controls, etc. Many of these are boilerplate legal/EEO. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should remove EEO statements, export controls, fair chance, preference for certain states, etc. Also remove "Additional Information" if it's mostly boilerplate. However we need to preserve substantive info: vaccination requirement maybe? 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 substantive? It's a requirement. Could keep as a note. But it's not a standard section like Benefits/Pay/Schedule. Could be placed under a short paragraph maybe under "Additional Information" but we might drop that heading if it's just boilerplate. However the vaccination requirement is substantive. We could include it in a
under maybe a heading like "Requirements" or "Additional Info". But we need to follow instruction: include a section ONLY when the posting has real, specific content for it. So we could have a section "Additional Information" with that vaccination note. But we must avoid filler. The vaccination note is specific. So we can include a section maybe "Additional Information" with that note. But also there is compensation info: Base Salary Range Region 1: $150,500 - $216,500; Region 2: $127,900 - $184,000; Shift: Day; Workplace Type: Onsite - This job is fully onsite. That's Pay and Schedule info. So we should include Pay and Schedule sections. Benefits: Not explicitly listed besides "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 unless specific. So skip. Thus sections: About the role? Could be company description? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which sections have content. We have company description: could be "About the role" or maybe "About the company". But they said About the role as example. We could put company description under "About the role". Or we could have a separate "Company Description" but not in list. Probably better to use "About the role" for the role description (Primary Function). But we also have responsibilities list. So we could have:
About the role
Primary Function of Position: ...
Then responsibilities list underResponsibilities
with- .
Then qualifications under
- Support the Program Management & Operations team in creating and implementing Clinical Development & Operations governance processes, including governance forums, operating cadences, decision pathways, program reporting, and the RAID framework.
- Facilitate Clinical Development & Operations & Operations governance by preparing governance materials, maintaining clinical RAID and decision logs, capturing actions and decisions, monitoring follow-through, and escalating cross-functional risks and decision requests through enterprise governance, as appropriate.
- Develop, maintain, and communicate integrated timelines across the clinical portfolio, ensuring alignment of milestones, dependencies, critical path activities, and cross-functional deliverables.
- Coordinate program-level execution across Study Leads, Clinical Operations, Data Management, Biostatistics, Safety, Regulatory Affairs, Medical Writing, Quality, and external partners, providing hands-on project management support to individual studies as needed.
- Monitor portfolio execution, proactively identifying schedule impacts, resource constraints, cross-study dependencies, and operational risks, and facilitate development of mitigation plans.
- Develop executive-ready portfolio reporting that communicates program health, milestone performance, critical path status, key risks, decision requests, and recommended actions.
- Identify portfolio trends and opportunities to strengthen planning, governance, reporting, and operational effectiveness across Clinical Development & Operations.
- Support regular functional-area budget management in coordination with Clinical Development & Operations Functional Area Team Leads and PM&O by tracking actual and forecasted accruals, invoices, purchase orders, and inputs to the Annual Operations Budget Planning Cycle.
- Support CRO and Vendor oversight by: incorporating vendor updates into project plans and governance materials; maintaining visibility and supporting management of purchase orders, change orders, invoices, key contract terms, and performance commitments; and coordinating business reviews and operational follow-up across internal functions.
- Drive adoption of standardized project management tools, templates, dashboards, reporting practices, and workflow automation that improve portfolio visibility, consistency, and execution.
- Bachelor's degree in Pharma/Life Sciences, or a related field (or equivalent experience). An advanced degree is preferred.
- Minimum 10 years of program or project management experience in pharmaceutical, biotechnology, medical device, or CRO industry supporting Clinical Development & Operations through NDA regulatory submissions.
- Demonstrated success leading cross-functional planning and execution across multiple concurrent clinical studies, including integrated planning, critical path management, and dependency management.
- Experience partnering with Clinical Development & Operations, CMC, Regulatory Affairs, and Quality leadership to support governance, portfolio planning, and executive decision-making.
- Experience supporting late-stage Clinical Development & Operations programs and familiarity with Clinical Development & Operations processes from start-up through close-out.
- Expertise in integrated timeline management, risk and issue management, resource coordination, and cross-functional execution.
- Strong executive communication and presentation skills, with the ability to deliver clear, actionable recommendations to senior leadership; High emotional intelligence and the ability to build trusted partnerships across technical and business functions.
- Proficiency with Smartsheet, including integrated project planning, dashboards, reporting, and workflow automation.
- Proof of vaccination against certain diseases including COVID-19 may be required (details vary by role).
- Preferred: Experience working with CROs, vendors, and cross-functional development teams.
- Preferred: PMP or comparable project management certification.
- Preferred: Familiarity with procurement, contract, and financial management systems (e.g., Coupa, iValua, SAP, Ariba, or equivalent).
- Base Salary Range Region 1: $150,500 - $216,500
- Base Salary Range Region 2: $127,900 - $184,000
- Shift: Day
- Workplace Type: Onsite - This job is fully onsite.
Qualifications
with- maybe split into required and preferred? Could combine but we can separate: Required Qualifications and Preferred Qualifications. But headings only from list; we could use "Qualifications" for required and maybe "Preferred Qualifications" as a subsection? Not in list but we could still use
Preferred Qualifications
if we want. The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. Probably we should stick to those. Could incorporate preferred qualifications under Qualifications as part of same list, maybe with a note "Preferred". But better to separate: we could have Qualifications
for required, and then another Preferred Qualifications
(though not in list). Might be okay. But to be safe, we could combine required and preferred into one Qualifications section, marking preferred items with "(Preferred)". That preserves all info.
Pay: Base Salary Range Region 1 and Region 2. Also mention "Shift: Day". So Pay section: include salary ranges. Schedule: Shift: Day, Workplace Type: Onsite - fully onsite. So Schedule section.
We need to avoid filler like "commensurate with experience". Not present.
We need to remove boilerplate: EEO, export controls, fair chance, preference for certain states, etc. Also remove "Additional Information" if it's just those. But we keep vaccination requirement maybe as a short note under Additional Information or under Qualifications? Could be under "Additional Information" heading. But we might drop that heading and just incorporate vaccination note into Qualifications as a requirement: "Proof of vaccination against certain diseases including COVID-19 may be required." That is a requirement. So we can add to Qualifications list.
Thus final HTML:
About the role
Primary Function of Position: The Senior Clinical Program Manager serves as the strategic and operational partner to Clinical Development & Operations leadership, providing integrated program management across the Clinical Development & Operations portfolio from study startup through regulatory submission. The role partners with Clinical Development & Operations leadership to inform Clinical Development & Operations strategy through integrated planning, scenario analysis, governance, and execution insights, translating strategic direction into coordinated cross-functional plans that enable successful program execution. Reporting to the Program Management & Operations organization, the Senior Clinical Program Manager partners across Clinical Development & Operations, Regulatory Affairs, Medical Affairs, CMC, Nonclinical, Quality, Commercial, and external partners to integrate timelines, risks, dependencies, and key decisions into unified program plans. In partnership with Enterprise Program Management, the role establishes Clinical Development & Operations governance and ensures cross-functional risks, dependencies, and decision requests are appropriately elevated through enterprise governance to support informed decision-making and coordinated execution.