Senior Staff Technical Program Manager
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, not invent or summarize away detail. So we need to keep details like bullet points? The posting has paragraphs; we can convert to
. For lists we need to detect bullet-like content: The "What You Get To Do In This Role" includes a series of sentences each starting with a verb; could be turned into
- . Similarly Ongoing Activities includes bullet-like items. Qualifications list includes bullet-like items.
We must not repeat job title as heading. No Job ID.
We must output only HTML fragment.
Let's extract content:
Company Description: It all started when engineer Fred Luddy wrote code that automated a tedious task for his coworker, Phyllis. She cried tears of joy. That moment inspired Fred to build a company that could do that for everyone—freeing people from busywork so they could focus on meaningful work. Today, ServiceNow is the AI control tower for business reinvention. Our ServiceNow AI platform brings together any AI, any data, and any workflow— helping 85% of the Fortune 500® work smarter, faster, and better. We're building an AI-native culture where technology and talent are unstoppable together. And we're just getting started. Join us to put AI to work for people.
Team Description: The Data and Analytics Product team comprises three major product pillars: Workflow Data Fabric, Workflow Data Management and Workflow Data Apps/Analytics. The team is focused on helping our customers connect, understand and act on their enterprise data. We build solutions for our customers that power workflows and agentic AI with internal and external data to unlock exponential customer value.
Role Description: As a Senior Staff Technical Program Manager, you will work with the Data and Analytics Product team and cross-functional partners to deliver world-class products and applications. In addition, you will support the execution of our strategy across key operational cadences. Our teams span the globe and require program managers to keep the big picture in focus. It will be your responsibility to orchestrate and navigate across a fast moving company as we strive toward our goal of becoming the Defining Enterprise Software Company of the 21st Century.
What You Get To Do In This Role:
- Lead cross-functional programs with Product, Engineering, Experience, Marketing, Sales, and Customer Success Teams.
- Align programs with business goals to achieve strategic outcomes.
- Organize complex problems into milestones, deliverables, risks, dependencies, and success criteria.
- Convert business objectives into execution strategies and lead implementation.
- Collaborate with stakeholders to maintain focus, plans, deliverables, and success criteria.
- Establish regular cadences and ensure accountability within the program.
- Provide ongoing reports on program developments to communicate objectives, status, risks, and results to stakeholders while resolving blockers.
- Lead and conduct executive meetings and large cross-functional events.
- Identify and mitigate risks to meet program objectives.
- Execute change management for effective process adoption.
- Develop necessary processes, templates, and materials.
- Analyze trends and data to provide leadership insights.
- Use AI to enhance program efficiency, decision-making, communication, and risk management.
Ongoing Activities Include Executive Coordination & Reporting:
- Coordinate Data and Analytics Executive SteerCos; define and set agenda with cross-functional stakeholders.
- Deliver key content and track action items to completion.
- Establish, collect, and enable the reporting of key product and business metrics to executives, organizational leaders and teams to drive business decisions.
- Prepare executive updates for D&A Leadership Team to make informed decisions.
- Collaborate with cross-functional team on key business cadences including Quarterly Product Reviews (QPRs), bi-annual Product Roadmap Reviews (PRRs) and annual Summer Strategy.
- Establish governance frameworks and lead executive-level meetings and cross-functional events; serve as the go-to source of leadership, transparency, and visibility — clearly communicating objectives, status, risks, and results while ensuring surgical execution and handoffs across workstreams
Data And Analytics Go-to-Market Execution:
- Define and execute Data and Analytics go-to-market readiness plans for new and existing products, working with cross functional teams.
- Proactively identify and manage program level go-to-market issues.
- Communicate and collaborate among cross-functional teams to resolve critical path issues and challenges.
- Maintain NPI Team process governance: enforce standards, templates, tooling, and compliance across product lines.
- Develop and drive Data and Analytics Product Advisory Council (PAC) activities.
Qualifications Required skills:
- Experience in leveraging or critically thinking about how to integrate AI into work processes, decision-making, or problem-solving. This may include using AI-powered tools, automating workflows, analyzing AI-driven insights, or exploring AI's potential impact on the function or industry.
- Minimum of 10 years technical program management experience on a global scale with at least 3 years of experience running large go- to-market and product delivery programs.
- Enterprise software/SaaS industry domain expertise with the ability to understand complex technology problems is a plus.
- Proven experience collaborating with Product, Engineering, Sales, Marketing, Customer Success, Support, Legal and other go-to-market teams.
- Exceptional communication skills, both written and verbal, with the ability to present complex business and technical concepts clearly and effectively to both technical and non-technical stakeholders.
- Ability to crisply communicate at the executive level.
- Excellent organizational skills with the ability to manage multiple priorities and deadlines and efficiently context switch amongst multiple initiatives.
- Strong collaboration and influence skills, able to work effectively with diverse teams across a fast paced, matrix environment and guide without direct authority.
- Excellent facilitation skills in leading planning meetings, reviews, and retrospectives, including the ability to concisely and accurately communicate with team members and senior leadership (i.e. VP/SVP).
- Process-driven with propensity to create and employ repeatable processes to complete tasks more efficiently.
- Professional certification, such as Project Management Professional (PMP) or equivalent.
Additional Information (we need to decide what to keep). The "Work Personas" paragraph: "Work Personas We approach our distributed world of work with flexibility and trust. Work personas (flexible, remote, or required in office) are categories that are assigned to ServiceNow employees depending on the nature of their work and their assigned work location. Learn more here. To determine eligibility for a work persona, ServiceNow may confirm the distance between your primary residence and the closest ServiceNow office using a third-party service." This is substantive info about work flexibility; could be included maybe under a section "Work Arrangement" but we have no heading for that; we could include as a
under maybe "Additional Information". However instruction says prefer few substantive sections over many thin ones. Could we incorporate this into a general "About the role" paragraph? Might be okay to keep as a
after Qualifications, maybe under a heading "Work Arrangement". But we need to decide if we should create a section for it. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The Work Personas content is specific, not filler. So we could add a section heading like "Work Arrangement" (though not in the prescribed list of headings; the list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we should use those headings if applicable. But we can also use other headings? The examples are just examples; but likely they expect those headings. However we have no Benefits, Pay, Schedule. We have About the role (maybe company description?), Responsibilities (what you get to do), Requirements (qualifications), Skills (maybe part of qualifications). We could map: About the role -> Company Description + Team Description + Role Description? Or maybe About the role is a brief summary. Responsibilities -> What You Get To Do + Ongoing Activities. Requirements -> Qualifications. Skills maybe not needed.
Thus we can produce sections: About the role, Responsibilities, Requirements. Possibly also Skills if we want to separate skills from qualifications but we can keep within Requirements.
We must not repeat job title as heading. So we will not have a heading for Senior Staff Technical Program Manager.
We'll output:
About the role
Company description paragraph(s) + Team description + Role description.
We need to preserve all substantive information: combine company description, team description, role description into one or multiple
? Probably multiple
okay.
Then
Responsibilities
- ... list items from What You Get To Do and Ongoing Activities combined? Could separate into two
but maybe one list.
We need to preserve all items; we can combine them.
Then Requirements
- ... qualifications list.
We might also include a
for Work Personas after Requirements? Could be part of About the role? Not really. Could be its own section maybe "Work Arrangement" but not in list. Might be okay to add as a
after Requirements without heading? But instruction says use
for section headings (e.g...). It doesn't forbid other headings but suggests using those. Safer to stick to those three sections and incorporate Work Personas into About the role? It's about work flexibility; could be considered part of About the role (company culture). We could add a sentence about flexible work arrangements.
Thus About the role paragraph can include company description, team description, role description, and work persona info.
Let's craft:
About the role:
It all started when engineer Fred Luddy wrote code that automated a tedious task for his coworker, Phyllis. She cried tears of joy. That moment inspired Fred to build a company that could do that for everyone—freeing people from busywork so they could focus on meaningful work. Today, ServiceNow is the AI control tower for business reinvention. Our ServiceNow AI platform brings together any AI, any data, and any workflow— helping 85% of the Fortune 500® work smarter, faster, and better. We're building an AI-native culture where technology and talent are unstoppable together. And we're just getting started. Join us to put AI to work for people.
The Data and Analytics Product team comprises three major product pillars: Workflow Data Fabric, Workflow Data Management and Workflow Data Apps/Analytics. The team is focused on helping our customers connect, understand and act on their enterprise data. We build solutions for our customers that power workflows and agentic AI with internal and external data to unlock exponential customer value.
for prose. We need to preserve all substantive information, not invent or summarize away detail. So we need to keep details like bullet points? The posting has paragraphs; we can convert to
. For lists we need to detect bullet-like content: The "What You Get To Do In This Role" includes a series of sentences each starting with a verb; could be turned into
- . Similarly Ongoing Activities includes bullet-like items. Qualifications list includes bullet-like items.
We must not repeat job title as heading. No Job ID.
We must output only HTML fragment.
Let's extract content:
Company Description: It all started when engineer Fred Luddy wrote code that automated a tedious task for his coworker, Phyllis. She cried tears of joy. That moment inspired Fred to build a company that could do that for everyone—freeing people from busywork so they could focus on meaningful work. Today, ServiceNow is the AI control tower for business reinvention. Our ServiceNow AI platform brings together any AI, any data, and any workflow— helping 85% of the Fortune 500® work smarter, faster, and better. We're building an AI-native culture where technology and talent are unstoppable together. And we're just getting started. Join us to put AI to work for people.
Team Description: The Data and Analytics Product team comprises three major product pillars: Workflow Data Fabric, Workflow Data Management and Workflow Data Apps/Analytics. The team is focused on helping our customers connect, understand and act on their enterprise data. We build solutions for our customers that power workflows and agentic AI with internal and external data to unlock exponential customer value.
Role Description: As a Senior Staff Technical Program Manager, you will work with the Data and Analytics Product team and cross-functional partners to deliver world-class products and applications. In addition, you will support the execution of our strategy across key operational cadences. Our teams span the globe and require program managers to keep the big picture in focus. It will be your responsibility to orchestrate and navigate across a fast moving company as we strive toward our goal of becoming the Defining Enterprise Software Company of the 21st Century.
What You Get To Do In This Role:
- Lead cross-functional programs with Product, Engineering, Experience, Marketing, Sales, and Customer Success Teams.
- Align programs with business goals to achieve strategic outcomes.
- Organize complex problems into milestones, deliverables, risks, dependencies, and success criteria.
- Convert business objectives into execution strategies and lead implementation.
- Collaborate with stakeholders to maintain focus, plans, deliverables, and success criteria.
- Establish regular cadences and ensure accountability within the program.
- Provide ongoing reports on program developments to communicate objectives, status, risks, and results to stakeholders while resolving blockers.
- Lead and conduct executive meetings and large cross-functional events.
- Identify and mitigate risks to meet program objectives.
- Execute change management for effective process adoption.
- Develop necessary processes, templates, and materials.
- Analyze trends and data to provide leadership insights.
- Use AI to enhance program efficiency, decision-making, communication, and risk management.
Ongoing Activities Include Executive Coordination & Reporting:
- Coordinate Data and Analytics Executive SteerCos; define and set agenda with cross-functional stakeholders.
- Deliver key content and track action items to completion.
- Establish, collect, and enable the reporting of key product and business metrics to executives, organizational leaders and teams to drive business decisions.
- Prepare executive updates for D&A Leadership Team to make informed decisions.
- Collaborate with cross-functional team on key business cadences including Quarterly Product Reviews (QPRs), bi-annual Product Roadmap Reviews (PRRs) and annual Summer Strategy.
- Establish governance frameworks and lead executive-level meetings and cross-functional events; serve as the go-to source of leadership, transparency, and visibility — clearly communicating objectives, status, risks, and results while ensuring surgical execution and handoffs across workstreams
Data And Analytics Go-to-Market Execution:
- Define and execute Data and Analytics go-to-market readiness plans for new and existing products, working with cross functional teams.
- Proactively identify and manage program level go-to-market issues.
- Communicate and collaborate among cross-functional teams to resolve critical path issues and challenges.
- Maintain NPI Team process governance: enforce standards, templates, tooling, and compliance across product lines.
- Develop and drive Data and Analytics Product Advisory Council (PAC) activities.
Qualifications Required skills:
- Experience in leveraging or critically thinking about how to integrate AI into work processes, decision-making, or problem-solving. This may include using AI-powered tools, automating workflows, analyzing AI-driven insights, or exploring AI's potential impact on the function or industry.
- Minimum of 10 years technical program management experience on a global scale with at least 3 years of experience running large go- to-market and product delivery programs.
- Enterprise software/SaaS industry domain expertise with the ability to understand complex technology problems is a plus.
- Proven experience collaborating with Product, Engineering, Sales, Marketing, Customer Success, Support, Legal and other go-to-market teams.
- Exceptional communication skills, both written and verbal, with the ability to present complex business and technical concepts clearly and effectively to both technical and non-technical stakeholders.
- Ability to crisply communicate at the executive level.
- Excellent organizational skills with the ability to manage multiple priorities and deadlines and efficiently context switch amongst multiple initiatives.
- Strong collaboration and influence skills, able to work effectively with diverse teams across a fast paced, matrix environment and guide without direct authority.
- Excellent facilitation skills in leading planning meetings, reviews, and retrospectives, including the ability to concisely and accurately communicate with team members and senior leadership (i.e. VP/SVP).
- Process-driven with propensity to create and employ repeatable processes to complete tasks more efficiently.
- Professional certification, such as Project Management Professional (PMP) or equivalent.
Additional Information (we need to decide what to keep). The "Work Personas" paragraph: "Work Personas We approach our distributed world of work with flexibility and trust. Work personas (flexible, remote, or required in office) are categories that are assigned to ServiceNow employees depending on the nature of their work and their assigned work location. Learn more here. To determine eligibility for a work persona, ServiceNow may confirm the distance between your primary residence and the closest ServiceNow office using a third-party service." This is substantive info about work flexibility; could be included maybe under a section "Work Arrangement" but we have no heading for that; we could include as a
under maybe "Additional Information". However instruction says prefer few substantive sections over many thin ones. Could we incorporate this into a general "About the role" paragraph? Might be okay to keep as a
after Qualifications, maybe under a heading "Work Arrangement". But we need to decide if we should create a section for it. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". The Work Personas content is specific, not filler. So we could add a section heading like "Work Arrangement" (though not in the prescribed list of headings; the list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we should use those headings if applicable. But we can also use other headings? The examples are just examples; but likely they expect those headings. However we have no Benefits, Pay, Schedule. We have About the role (maybe company description?), Responsibilities (what you get to do), Requirements (qualifications), Skills (maybe part of qualifications). We could map: About the role -> Company Description + Team Description + Role Description? Or maybe About the role is a brief summary. Responsibilities -> What You Get To Do + Ongoing Activities. Requirements -> Qualifications. Skills maybe not needed. Thus we can produce sections: About the role, Responsibilities, Requirements. Possibly also Skills if we want to separate skills from qualifications but we can keep within Requirements. We must not repeat job title as heading. So we will not have a heading for Senior Staff Technical Program Manager. We'll output:
About the role
Company description paragraph(s) + Team description + Role description.
We need to preserve all substantive information: combine company description, team description, role description into oneor multiple
? Probably multiple
okay. Then
Responsibilities
- ... list items from What You Get To Do and Ongoing Activities combined? Could separate into two
- but maybe one list.
We need to preserve all items; we can combine them.
Then
- ... qualifications list.
We might also include a
for Work Personas after Requirements? Could be part of About the role? Not really. Could be its own section maybe "Work Arrangement" but not in list. Might be okay to add as a
after Requirements without heading? But instruction says use
for section headings (e.g...). It doesn't forbid other headings but suggests using those. Safer to stick to those three sections and incorporate Work Personas into About the role? It's about work flexibility; could be considered part of About the role (company culture). We could add a sentence about flexible work arrangements. Thus About the role paragraph can include company description, team description, role description, and work persona info. Let's craft: About the role:
It all started when engineer Fred Luddy wrote code that automated a tedious task for his coworker, Phyllis. She cried tears of joy. That moment inspired Fred to build a company that could do that for everyone—freeing people from busywork so they could focus on meaningful work. Today, ServiceNow is the AI control tower for business reinvention. Our ServiceNow AI platform brings together any AI, any data, and any workflow— helping 85% of the Fortune 500® work smarter, faster, and better. We're building an AI-native culture where technology and talent are unstoppable together. And we're just getting started. Join us to put AI to work for people.
The Data and Analytics Product team comprises three major product pillars: Workflow Data Fabric, Workflow Data Management and Workflow Data Apps/Analytics. The team is focused on helping our customers connect, understand and act on their enterprise data. We build solutions for our customers that power workflows and agentic AI with internal and external data to unlock exponential customer value.
Requirements
- ... qualifications list.
We might also include a
- ... list items from What You Get To Do and Ongoing Activities combined? Could separate into two