Staff Technical Program Manager, Ad Technology

We need to output HTML fragment with sections: About the role? Actually we have sections: Who We Are (company description) maybe not needed? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include sections only when posting has real specific content. The posting includes: Who We Are (company overview) - could be considered "About the role"? Actually "Who We Are" is about company, not role. Could map to "About the role"? Might be better to have "About the role" as a heading summarizing role description. But we have "How You’ll Make An Impact" and "What You’ll Do" etc. We need to decide sections. We have content: "Who We Are" (company description) - maybe not needed as it's not about role. Could be omitted? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says include a section ONLY when the posting has real, specific content for it. So we need to map content to those headings. We have: - How You’ll Make An Impact: could be "About the role" or maybe "Responsibilities"? Actually it's about impact. - What You’ll Do: list of duties -> Responsibilities. - What You’ll Need: qualifications/requirements -> Requirements or Qualifications. - Compensation: base salary range -> Pay. - Benefits: not explicitly mentioned besides discretionary incentives; maybe not enough. - Schedule: not mentioned. - Skills: maybe part of qualifications. We need to avoid boilerplate like EEO, legal, etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to include the details from each section. We need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

About the role

...

But we need to decide content for About the role: maybe combine Who We Are and How You’ll Make An Impact? However "Who We Are" is company overview, not role. Could we make a section "About the company"? Not in allowed headings. Probably we should not include Who Are as a heading because not in list; but we could incorporate into About the role? 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 suggests those as examples. Safer to stick to those. Thus we need to map content: - About the role: maybe a brief summary of the role: "As a strategic and adaptable Staff Technical Program Manager, Ad Technology, you will own the strategy and delivery of large-scale, cross-organizational initiatives across Ads Engineering..." That's from How You’ll Make An Impact and maybe first paragraph. - Responsibilities: the bullet list under What You’ll Do (Enterprise Program Strategy & Delivery, Technical Leadership & Systems Thinking, Roadmap Alignment & Program Strategy, Organizational Effectiveness & Governance, Cross-Functional Collaboration & Executive Communication). We'll need to turn each into

• items. - Requirements/Qualifications: What You’ll Need section includes many items: minimum experience, degree, demonstrated experience owning enterprise program strategy, significant experience in advertising technology, proficient architectural literacy, executive-level communication skills, proven ability to drive delivery, experience with Agile/Jira, experience with automation/AI tools, relationship building, experience in digital audio/media platforms preferred, vendor/third-party tech integrations preferred, high-availability real-time systems preferred, platform transformation preferred, legal right to work in US. Also note about compensation? That's Pay. We need to decide whether to split Requirements and Qualifications. Could combine into one section "Requirements". Or have both Requirements and Qualifications if distinct. The posting lumps them; we could put all under Requirements. - Pay: base salary range $150,100 to $179,000, plus discretionary short-term and long-term incentives. - Benefits: not explicitly given besides incentives; maybe we could include short-term and long-term incentives under Benefits? But they said discretionary short-term and long-term incentives. Could be considered Benefits. However we need real specific content; we have that. So we can create Benefits section mentioning discretionary short-term and long-term incentives. - Schedule: not mentioned, so omit. - Skills: maybe part of Requirements; we could omit separate Skills section. We must not repeat job title as heading. Not include Job ID. We must remove boilerplate: EEO, legal, equal opportunity, scam warning, etc. Also remove "At SiriusXM, we carefully consider..."? That's part of compensation description; we can keep compensation details but remove the sentence about considering factors? It says "At SiriusXM, we carefully consider a wide range of factors when determining compensation, including your background and experience. These considerations can cause your compensation to vary." That's somewhat boilerplate but still part of compensation description. Might be okay to keep but it's generic. Safer to keep only the concrete range and incentives. Also remove "We encourage all interested candidates to apply." etc. Also remove "Our goal at SiriusXM is to provide and maintain a work environment..." etc. Also remove "The requirements and duties described above may be modified..." etc. Also remove "R-2026-05-63" (Job ID). Now craft HTML. We'll need to ensure proper nesting. Let's draft:

  About the role

  As a strategic and adaptable Staff Technical Program Manager, Ad Technology, you will own the strategy and delivery of large-scale, cross‑organizational initiatives across Ads Engineering. This role is critical to driving execution of high‑impact programs spanning ad‑serving systems, data platforms, monetization workflows, and cross‑program integrations with Pandora and broader SiriusXM systems. You will partner directly with engineering and product leadership to shape multi‑year roadmaps, co‑own program strategy, streamline org‑wide governance, and deliver outcomes that materially impact platform scalability, monetization performance, and global platform capabilities.

  Responsibilities

  • Establish and own the strategy and end‑to‑end delivery of large, cross‑organizational Ads Engineering initiatives (e.g., broadcast ads digitization and modernization, ad insertion, consolidation across SiriusXM and Pandora tech stacks), from intake through launch.
  • Function as Workstream lead for select cross‑organizational initiatives spanning multiple engineering teams – from planning through launch.
  • Maintain roadmap and delivery commitments for multiple teams within the Ad Technology organization, aligning Product, Engineering and GTM on execution plans, ROIs and outcomes (e.g., latency/SLAs, yield/monetization lift, reliability, rollout readiness).
  • Coordinate program structure, milestones, sequencing, interdependencies, and success metrics in close partnership with engineering and product leadership.
  • Proactively identify, forecast, and mitigate delivery risks and issues, communicating mitigation plans and status clearly to stakeholders.
  • Use data to drive sustainable planning and transparent tradeoff discussions for new work or conflicting priorities.
  • Provide portfolio‑level visibility and structured analysis to advise on prioritization and resource allocation decisions.
  • Drive high‑stakes tradeoff decisions (scope, sequencing, resourcing, risk) with Director/VP level engineering and product leadership and be directly accountable for program‑level outcomes and delivery across multiple teams.
  • Apply proficient architectural literacy across ad‑serving, real‑time bidding, data pipelines, monetization platforms, and distributed infrastructure.
  • Guide teams toward scalable, aligned technical solutions by deeply understanding platform constraints and cross‑program tradeoffs.
  • Review system designs, challenge assumptions, and proactively solve downstream impacts across tightly coupled Ads and platform integrations.
  • Manage capacity, risks, technical debt, velocity, and operational readiness.
  • Anticipate long‑term platform risks and scalability constraints, including across globally distributed systems.
  • Serve as the go‑to Technical Program Manager and subject matter expert for complex cross‑program integrations, major platform constraints, and critical cross‑domain dependency resolution.
  • Influence roadmap alignment across Ads, Pandora, and related programs.
  • Own program‑level strategy across multiple teams, including dependency mapping, sequencing, and integration planning for complex, ambiguous initiatives where outcomes and constraints evolve.
  • Co‑own Ads Technology program strategy, shaping roadmap prioritization based on business impact, technical feasibility, and cross‑program dependencies.
  • Advocate for program(s) health and long‑term strategy.
  • Define and institutionalize Ads TPM org‑wide program governance standards, operating models, and best practices, elevating execution rigor across the entire Ads Engineering organization.
  • Mentor and uplevel other TPMs, and cross‑functional partners by creating playbooks, templates, and coaching that improve execution quality beyond your immediate scope.
  • Continuously improve governance and delivery processes to increase predictability, execution quality, and program health over time.
  • Establish and facilitate team‑level ceremonies including daily standups, sprint planning, backlog refinement, retrospectives, and/or other meetings needed to ensure smooth execution and team alignment.
  • Partner with TPM leadership to run program level ceremonies like intake and refinement if required.
  • Define, instrument, and socialize delivery and operational health metrics (e.g., predictability, cycle time, throughput, readiness, and post‑launch outcomes) to drive transparent decision‑making and continuous improvement.
  • Build formal cross‑functional networks across Product, Engineering, Data, Infrastructure, and partner programs to drive alignment and coordinated execution; influence roadmap and investment tradeoffs with senior leadership.
  • Serve as the connective layer between Engineering, Product, Quality, Operations, and external stakeholders.
  • Present clear, scenario‑based decision paths to engineering and business leadership, driving consensus through clarity.
  • Resolve conflict and maintain alignment across directors, tech leads, and cross‑functional partners with authority and credibility.

  Requirements

  • Minimum of 7 years of related experience with a Bachelor’s degree; or 5 years and a Master’s degree; or a PhD with 4 years experience; or equivalent experience leading complex, enterprise‑scale initiatives.
  • Bachelor's degree in Computer Science, Engineering, or equivalent work experience.
  • Demonstrated experience owning enterprise program strategy — including multi‑year roadmap partnership, portfolio‑level decision support, and org‑wide process improvement — not just execution.
  • Significant experience in advertising technology, including ad‑serving systems, real‑time bidding, monetization platforms, data pipelines, and analytics systems.
  • Proficient architectural literacy across multiple platform programs; ability to guide teams toward scalable solutions and evaluate cross‑program constraints and tradeoffs.
  • Executive‑level communication skills; ability to craft scenario‑based decision paths for senior engineering and business leadership and drive consensus through clarity.
  • Proven ability to drive delivery across tightly coupled, interdependent systems at scale.
  • Demonstrated ability to operate with minimal oversight across ambiguous, high‑stakes programs.
  • Experience working across multiple Agile methodologies; proficiency with Jira and related program management tooling.
  • Experience with automation and/or AI tools such as chatGPT, Gemini, etc.
  • Strong propensity toward relationship building and influencing without authority.
  • Experience in digital audio or media platforms preferred.
  • Experience managing vendor or third‑party technology integrations, including global or multi‑region platforms preferred.
  • Experience in high‑availability, real‑time systems environments preferred.
  • Experience leading platform transformation or cross‑organizational