Senior Program Manager, Architecture & Automation Deployment
- with items summarizing each bullet. Must preserve all substantive info; we can break into multiple
- each covering each bullet's content.
Let's extract each bullet:
Voice of Customer and Tool Strategy:
- Run structured voice-of-customer efforts with engineering teams across divisions to understand where new tools, automation, or AI capabilities would have the most impact.
- Synthesize findings into clear deployment priorities and business cases, partnering with engineering leadership to validate direction.
- Stay current on emerging engineering tools and AI capabilities relevant to hardware and systems engineering workflows.
Architecture and AI Deployment:
- Own end-to-end deployment programs for architecture implementation and AI capabilities across the enterprise, from pilot through full rollout.
- Drive systematization: turning a promising tool or pilot into a repeatable, well-governed capability that scales across divisions.
- Partner with IT, engineering operations, and divisional leads to manage rollout logistics, training, and change management.
- Track adoption and usage post-deployment, and course-correct programs that aren't landing.
Automation Program Execution:
- Lead program management for cross-divisional automation initiatives, including coordination with the China Innovation Center on accelerated engineering projects.
- Build and run program plans, governance cadences, and status reporting that keep divisional teams, strategic marketing, and the hub aligned on scope and timing.
- Manage cross-time zone program cadence with the China Innovation Center, keeping risks and dependencies visible to stakeholders.
Cross-Functional Governance and Reporting:
- Maintain a portfolio view across architecture and automation programs, including status, risks, resourcing, and timelines.
- Partner with divisional program managers and engineering leads to resolve cross-program dependencies.
- Report program health and key decisions to the CTO office and other senior stakeholders on a regular cadence.
Qualifications:
- 10+ years of program or project management experience in a hardware/instrument R&D environment, including experience deploying tools, processes, or capabilities across engineering teams.
- Systems engineering background or hands-on experience working within a systems engineering process strongly preferred.
- Experience running voice-of-customer or internal stakeholder research efforts and translating findings into action.
- Experience with engineering tool rollouts, digital transformation, or AI/automation adoption initiatives strongly preferred.
- Experience running cross-divisional or multi-site programs, ideally including work with an offshore or globally distributed engineering team.
Required Skills And Competencies:
- Strong program and portfolio management fundamentals: scope, schedule, risk, and stakeholder management.
- Comfort operating in a technical environment, able to hold credible conversations with engineering leads about systems-level and architecture workflows.
- Skilled at running voice-of-customer processes and turning qualitative input into a structured plan.
- Ability to build structure and process without slowing teams down, tuned to an engineering audience.
- Strong cross-functional influence and communication, able to align divisional and hub stakeholders without direct authority.
Additional Details:
- This job has a full time weekly schedule.
- It includes the option to work remotely.
- Applications for this job will be accepted until at least September 22, 2026 or until the job is no longer posted.
- The full-time equivalent pay range for this position is $179,931.00 - $315,300.00/yr plus eligibility for bonus, stock and benefits.
- Our pay ranges are determined by role, level, and location. Within the range, individual pay is determined by work location and additional factors, including job-related skills, experience, and relevant education or training.
- During the hiring process, a recruiter can share more about the specific pay range for a preferred location.
- Pay and benefit information by country are available at: https://careers.agilent.com/locations
- Travel Required: 25% of the Time
- Shift: Day
- Duration: No End Date
- Job Function: R&D
We need to include Pay and Schedule sections only if posting actually states them. Pay: yes. Schedule: full time weekly schedule, option to work remotely. Also maybe Travel Required etc but not required. We'll include Schedule section with that info. Benefits not given explicitly (though mentions eligibility for bonus, stock and benefits). Could we include Benefits? The posting mentions "plus eligibility for bonus, stock and benefits." That's a statement about benefits. Could create Benefits section with that line. But rule: only include section when posting has real, specific content for it. It does mention eligibility for bonus, stock and benefits. That's somewhat specific. Could include Benefits section with that sentence. However we also have Pay section already includes mention of bonus, stock and benefits. Might be redundant. Better to keep Pay section includes that phrase. Benefits section maybe not needed.
We must not include boilerplate like EEO, equal opportunity, etc. Also remove application instructions (Applications for this job will be accepted until at least September 22, 2026...). That's substantive? It's about application deadline. The instruction says remove application instructions. So we should drop that line. Also remove "Pay and benefit information by country are available at: ..." maybe considered boilerplate? It's a link; could be considered extra but it's substantive info about where to find pay info. Might be okay to keep? The rule says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to pay info is not exactly those categories, but could be considered navigation? It's a link to external site. Might be considered navigation. Safer to drop it. Also drop "Travel Required: 25% of the Time", "Shift: Day", "Duration: No End Date", "Job Function: R&D" maybe considered metadata but not prohibited. Could keep as part of Schedule? Not exactly schedule. Might be considered extra details. The instruction: "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." So we could fold Travel, Shift, Duration, Job Function into a short
maybe under Additional Details. But we already have Schedule section. Could include those details in Schedule section as a list. Let's decide: We'll create sections:
About the role
with paragraph(s).Responsibilities
with- each bullet.
Qualifications
with- .
Required Skills
with- .
Pay
withcontaining pay range plus eligibility for bonus, stock and benefits.
Schedule
withcontaining full-time weekly schedule, option to work remotely, travel 25%, day shift, no end date, R&D function. We must not include any heading without real content. All sections have content. Now produce HTML fragment only. Check for any duplicated lines: ensure we didn't repeat. Let's craft. About the role paragraph: combine the two paragraphs maybe. Paragraph: "Agilent is looking for a Senior Program Manager to lead the deployment of engineering tools, automation, and AI capabilities across our R&D organization. This role owns the full cycle from understanding what engineers actually need, to rolling out the tools and systems that meet that need, to making adoption stick. You will run internal voice-of-customer efforts with engineering teams across divisions, translate what you learn into deployment programs, and drive the systematization and execution that turns a new tool or capability into something engineers actually use day to day. This role also runs the program management behind Agilent's cross-divisional automation initiatives, including coordination with our China Innovation Center on accelerated engineering projects. You will build and manage the program plans, governance, and reporting that keep divisional teams, the innovation hub, and the CTO office aligned as these initiatives scale. This is a program leadership role built for someone who can move fluidly between listening to engineers, structuring a rollout plan, and running the execution discipline to deliver it. A systems engineering background is highly valued: understanding how engineering tools plug into the product development lifecycle and being able to speak credibly with engineering leads about technical workflows, will make you far more effective than program management experience alone." That's fine. Responsibilities list: we need to capture each bullet exactly. Let's list them: - Run structured voice-of-customer efforts with engineering teams across divisions to understand where new tools, automation, or AI capabilities would have the most impact. - Synthesize findings into clear deployment priorities and business cases, partnering with engineering leadership to validate direction. - Stay current on emerging engineering tools and AI capabilities relevant to hardware and systems engineering workflows. - Own end-to-end deployment programs for architecture implementation and AI capabilities across the enterprise, from pilot through full rollout. - Drive systematization: turning a promising tool or pilot into a repeatable, well-governed capability that scales across divisions. - Partner with IT, engineering operations, and divisional leads to manage rollout logistics, training, and change management. - Track adoption and usage post-deployment, and course-correct programs that aren't landing. - Lead program management for cross-divisional automation initiatives, including coordination with the China Innovation Center on accelerated engineering projects. - Build and run program plans, governance cadences, and status reporting that keep divisional teams, strategic marketing, and the hub aligned on scope and timing. - Manage cross-time zone program cadence with the China Innovation Center, keeping risks and dependencies visible to stakeholders. - Maintain a portfolio view across architecture and automation programs, including status, risks, resourcing, and timelines. - Partner with divisional program managers and engineering leads to resolve cross-program dependencies. - Report program health and key decisions to the CTO office and other senior stakeholders on a regular cadence. Check we didn't miss any: The original also had "Partner with divisional program managers and engineering leads to resolve cross-program dependencies." yes. Now Qualifications list: - 10+ years of program or project management experience in a hardware/instrument R&D environment, including experience deploying tools, processes, or capabilities across engineering teams. - Systems engineering background or hands-on experience working within a systems engineering process strongly preferred. - Experience running voice-of-customer or
- .
- .
- each bullet.