Senior Program Manager
Siemens Healthineers · Palo Alto, CA · 1 mo ago
Project Management$167k–$230k/yrFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also must not create sections with filler like "commensurate with experience". Must include Pay and Benefits only if posting actually states them. The posting includes Base Pay Range and benefits list. So we can include Pay and Benefits sections. Schedule? Not mentioned. So omit Schedule.
We need sections: About the role (intro paragraph), Responsibilities (list), Requirements (maybe education/experience?), Qualifications (maybe required knowledge/skills?), Skills (maybe desired skills?), Benefits, Pay.
We need to decide mapping. The posting includes: "Join us in pioneering breakthroughs..." that's about company culture; could be About the role? Actually "About the role" could be description of role: The Senior Program Manager will lead technical program execution... That's role description. So we can put that in About the role.
Responsibilities: there is a big block with headings: Supplier & Technical Alignment, Program Execution & Coordination, Risk & Issue Management, Communication & Leadership, Strategic Governance and Leadership... We need to list duties as
- . Should we keep subheadings? Probably just list each bullet as a duty. Could preserve subheadings as part of li text.
Requirements: maybe "Required Knowledge/Skills, Education, And Experience" block. That includes bullet-like sentences. We'll put as
- .
Qualifications: maybe not separate; but we could treat "Other Desired Skills And Knowledge" as Skills or Qualifications. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which content goes where.
We have: Required Knowledge/Skills, Education, And Experience -> could be Requirements (education/experience) and also Qualifications (skills). But we have also "Other Desired Skills And Knowledge" -> could be Skills.
We also have "What Success Looks Like (First 6–12 Months)" maybe could be part of About the role? But it's specific expectations; maybe could be included in Responsibilities? But it's not a duty; it's success metrics. Could be omitted? But we must preserve ALL substantive information; cannot invent or summarize away detail. So we need to include that info somewhere. Could create a section "Expectations" but not allowed headings list only those given. Could put under Responsibilities as additional bullet? Or under About the role? Probably better to add a subsection under Responsibilities? But we must not create new headings beyond allowed list. So we can embed that info within existing sections as paragraphs or list items.
Similarly "Special Job Requirements" (occupational exposure, standing, travel) - that is substantive; need to include. Could be under Requirements or maybe a separate section? Not in allowed headings; but we could put under Requirements as additional bullet.
Also "Who we are:" and "How we work:" is company description; could be part of About the role? Might be considered boilerplate? It's not legal/EEO; it's about company culture. Might be considered substantive but maybe could be omitted? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This company description is not those; it's substantive about the company. Should we keep? Probably yes, as part of About the role.
We also have "The Base Pay Range For This Position Is $167,030 - $229,669 Factors which may affect starting pay within this range may include geography/market, skills, education, experience, and other qualifications of the successful candidate. If this is a commission eligible position the commission eligibility will be in accordance with the terms of the Company's plan. Commissions are based on individual performance and/or company performance." That's Pay section.
Benefits: list: medical insurance, dental insurance, vision insurance, 401(k) retirement plan. life insurance, long-term and short-term disability insurance, paid parking/public transportation, paid time off, paid sick and safe time.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft:
About the role
Join us in pioneering breakthroughs in healthcare. For everyone. Everywhere. Sustainably. Our inspiring and caring environment forms a global community that celebrates diversity and individuality. We encourage you to step beyond your comfort zone, offering resources and flexibility to foster your professional and personal growth, all while valuing your unique contributions. The Senior Program Manager will lead technical program execution with a primary focus on ensuring flawless alignment between Varian and external suppliers. This role is responsible for orchestrating day-to-day technical activities across supplier interfaces and internal engineering teams, ensuring that system-level integration, technical requirements, and deliverables are consistently aligned, executed, and validated. Working closely with Engineering, this role acts as the single point of coordination across supplier technical interfaces, proactively identifying risks, resolving misalignment early, and maintaining program momentum across complex, multi-disciplinary workstreams.
Then Responsibilities: list each duty. We need to capture all responsibilities bullet points from the text. Let's extract: Supplier & Technical Alignment - Accountable for end-to-end technical alignment across Varian and supplier interfaces; owns resolution of any integration misalignment impacting program delivery. - Own technical alignment between Varian and external suppliers, ensuring requirements clarity, traceability, and execution consistency - Drive interface management across hardware, software, and system integration boundaries - Establish and enforce technical governance with suppliers (reviews, design checkpoints, issue tracking) - Identify and resolve technical gaps, inconsistencies, and integration risks early Program Execution & Coordination - Lead and coordinate day-to-day technical program execution across internal engineering teams and external suppliers, ensuring alignment to schedule and deliverables. - Translate program objectives into clear technical deliverables and milestones across suppliers - Maintain integrated program plans that reflect both Varian and supplier dependencies - Own the technical decision tracker and ensure all decisions are documented, communicated, and implemented across organizations. Risk & Issue Management - Proactively identify and escalate technical and integration risks - Drive cross-company issue resolution, ensuring rapid decision-making and no loss of momentum - Implement risk mitigation strategies to avoid downstream delays in system integration Communication & Leadership - Serve as the primary interface between Varian and supplier technical leadership - Provide clear, structured updates to internal stakeholders and leadership - Facilitate technical decision-making across organizations, ensuring alignment and accountability Strategic Governance and Leadership of technical program milestones to accelerate schedules and proactively mitigate technical risks for the ARPA project. - (maybe this is a bullet) Actually it's a sentence: "Strategic Governance and Leadership of technical program milestones to accelerate schedules and proactively mitigate technical risks for the ARPA project." We'll treat as a bullet. Also "What Success Looks Like (First 6–12 Months)" details: - Zero ambiguity in supplier technical interfaces and requirements - Early identification and resolution of integration risks - Smooth, predictable execution across supplier-dependent milestones - Strong working relationships and trust established with key suppliers We could include these under Responsibilities as additional bullets. Special Job Requirements: - Occupational exposure to radiation and other occupational hazards pertaining to the operation of a linear accelerator - Standing, sitting, or stooping for extended periods of time. - Periodic travel (domestic or international) as required by project milestones, with a focus on remote coordination where possible. We could put these under Requirements or maybe a separate section but not allowed; we can put under Requirements as additional bullets. Now Requirements (education/experience): - Bachelor’s or master’s degree in engineering, Physics, or related technical field - 8–12+ years of experience in technical program/project management, preferably in medical devices or complex systems - Proven experience working with external suppliers or partners in a technical environment - Strong understanding of system integration, hardware/software interfaces, and engineering development cycles - Demonstrated ability to manage cross-functional and multi-company technical programs - Strong technical acumen with ability to engage deeply with engineering teams - Excellent communication and stakeholder management skills across organizational boundaries - Structured problem-solving and risk management mindset - Ability to operate effectively in complex, fast-paced development environments We could also include special job requirements here. Qualifications: maybe we could treat "Other Desired Skills And Knowledge" as Qualifications or Skills. Let's decide: Qualifications could be the required knowledge/skills/experience (the above). Skills could be the desired other skills. Thus:Requirements
- ... (list above plus special job requirements? maybe separate).
Skills
- Proven experience with FLASH clinical trials.
- Experience with HCM (e.g., Workday), CRM (Salesforce) and ERP (SAP) product and productivity software.
- Strong can do and solution orientated focus.
Benefits
- medical insurance
- dental insurance
- vision insurance
- 401(k) retirement plan
- life insurance
- long-term and short-term disability insurance
- paid parking/public transportation
- paid time off
- paid sick and safe time
Pay
The Base Pay Range For This Position Is $167,030 - $229,669. Factors which may affect starting pay within this range may include geography/market, skills, education, experience, and other qualifications of the successful candidate. If this is a commission eligible position the commission eligibility will be in accordance with the terms of the Company's plan. Commissions are based on individual performance and/or company performance.
We should not include Schedule. Check for any duplicated lines: we have not included EEO etc. We must ensure we didn't include any boilerplate like "Equal Employment Opportunity Statement", "EEO is the Law", "Reasonable Accommodations", "California Privacy Notice", "Export Control", "Data Privacy", "Beware of Job Scams", "To find out more about Siemens Healthineers businesses", etc. We removed those. We kept "Who we are:" and "How we work:"? Actually we omitted them; we included only the initial inspirational paragraph. The "Who we are:" and "How we work:" paragraphs are after the responsibilities etc. We omitted them; is that okay? They are substantive about company but maybe considered boilerplate? Not exactly legal; but they are repetitive of earlier inspirational text. Might be considered duplicated lines? The earlier part already had similar content. To be safe, we could include them in About the role as additional paragraph. But we already have a paragraph about inspiring environment etc. The "Who we are:" paragraph is more about the team size etc. Could be considered substantive. Let's include it as another paragraph in About the role. Similarly "How we work:" paragraph about global team etc. Could be included. We must not repeat the job title as heading; we didn't. Now ensure we didn't include any filler like "commensurate with experience". Not present. Now produce final HTML. Let's craft:About the role
Join us in pioneering breakthroughs in healthcare. For everyone. Everywhere. Sustainably. Our inspiring and caring environment forms a global community that celebrates diversity and individuality. We encourage you to step beyond your comfort zone, offering resources and flexibility to foster your professional and personal growth, all while valuing your unique contributions. The Senior Program Manager will lead technical program execution with a primary focus on ensuring flawless alignment between Varian and
- .
Qualifications: maybe not separate; but we could treat "Other Desired Skills And Knowledge" as Skills or Qualifications. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which content goes where.
We have: Required Knowledge/Skills, Education, And Experience -> could be Requirements (education/experience) and also Qualifications (skills). But we have also "Other Desired Skills And Knowledge" -> could be Skills.
We also have "What Success Looks Like (First 6–12 Months)" maybe could be part of About the role? But it's specific expectations; maybe could be included in Responsibilities? But it's not a duty; it's success metrics. Could be omitted? But we must preserve ALL substantive information; cannot invent or summarize away detail. So we need to include that info somewhere. Could create a section "Expectations" but not allowed headings list only those given. Could put under Responsibilities as additional bullet? Or under About the role? Probably better to add a subsection under Responsibilities? But we must not create new headings beyond allowed list. So we can embed that info within existing sections as paragraphs or list items.
Similarly "Special Job Requirements" (occupational exposure, standing, travel) - that is substantive; need to include. Could be under Requirements or maybe a separate section? Not in allowed headings; but we could put under Requirements as additional bullet.
Also "Who we are:" and "How we work:" is company description; could be part of About the role? Might be considered boilerplate? It's not legal/EEO; it's about company culture. Might be considered substantive but maybe could be omitted? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This company description is not those; it's substantive about the company. Should we keep? Probably yes, as part of About the role.
We also have "The Base Pay Range For This Position Is $167,030 - $229,669 Factors which may affect starting pay within this range may include geography/market, skills, education, experience, and other qualifications of the successful candidate. If this is a commission eligible position the commission eligibility will be in accordance with the terms of the Company's plan. Commissions are based on individual performance and/or company performance." That's Pay section.
Benefits: list: medical insurance, dental insurance, vision insurance, 401(k) retirement plan. life insurance, long-term and short-term disability insurance, paid parking/public transportation, paid time off, paid sick and safe time.
We need to output only HTML fragment, no /, no markdown fences.
Let's craft: