Director, Technical Program Management

We need to output HTML fragment with sections: About the role? Actually the posting includes description paragraphs. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes description: company overview, role description, responsibilities (What you'll do), requirements (Who you are). No explicit Benefits, Pay, Schedule. So we should not create those sections. We need to include sections: About the role (maybe summary), Responsibilities (What you'll do), Requirements (Who you are). Possibly Qualifications? The "Who you are" includes qualifications. Could map to Qualifications. But we need to decide: The instruction says use those headings if content exists. We have content for Responsibilities (What you'll do). For Requirements/Qualifications/Skills we have "Who you are" which includes experience, domain expertise, etc. Could split into Requirements and Qualifications and Skills? Better to have one section "Requirements" or "Qualifications". Since we have both experience and skills, we could put under "Requirements". Or we could have "Qualifications". The instruction: prefer a few substantive sections over many thin ones. So maybe just two sections: Responsibilities and Requirements (or Qualifications). Also we could include an "About the role" section summarizing the role overview (the first paragraphs). That seems appropriate. Thus sections: About the role, Responsibilities, Requirements. We need to use

for each heading. Then content:

for prose,

• for lists. We must preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not include boilerplate like EEO, privacy, etc. Must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the equal opportunity employer paragraph, privacy policy, AI tools note, etc. We need to keep all substantive info: company description, role description, responsibilities bullet points (under What you'll do), requirements bullet points (under Who you are). Also note about ad tech domain expertise being hard requirement. We need to format lists appropriately. Let's extract content. Company overview: "Samba is a media intelligence company. We know what the world is watching, reading, and thinking about — in real time, at scale, across every screen. Our data exists with the consent of over a billion people, organized into the most complete picture of consumer attention ever built. The biggest brands in the world use that picture to make smarter decisions. We think it’s the most interesting data asset on the planet, because it’s the most culturally relevant." Then role description: "We are looking for a Director of Technical Program Management to lead and grow our TPM function at a critical inflection point in the company's expansion. This is not a pure execution role — it is a strategic leadership position. You will be a peer to VPs and Sr. Directors across Engineering, Product, Data Science, and Executive Leadership, owning how we plan, execute, and govern complex programs that span the full ad tech stack: data collection, identity, audience platforms, measurement solutions, and third-party integrations. You will own, build and develop a small but high-impact team of TPMs, establish the frameworks and operating model that scale with the organization, and personally drive the most complex, cross-functional programs. The right candidate brings deep engineering discipline, ad tech domain knowledge a plus, proven people leadership, and the organizational instincts to operate credibly at the senior leadership level." Then "WHAT YOU'LL DO" with subheadings: Organizational Leadership, Program Strategy & Execution, Cross-functional Influence & Stakeholder Management, Process, Tooling & Governance. Under each bullet points. We need to convert those into a list under Responsibilities. We should preserve the bullet points as list items. Let's extract each bullet: Organizational Leadership: - Lead, mentor, and grow a team of 2–4 TPMs, setting a high bar for program ownership, communication, and technical credibility. - Define the TPM team's operating model — how programs are staffed, governed, escalated, and reported — and evolve it as the organization scales. - Act as the senior-most TPM voice in leadership forums, representing program health, risk posture, and execution capacity to the CTO, SVP of Engineering and cross-functional peers. - Drive hiring decisions, performance development, and career growth for the TPM team. Program Strategy & Execution: - Own the end-to-end program execution strategy for the technology organization's most complex, cross-functional initiatives — from annual planning through delivery. - Define and enforce program governance frameworks: scope, milestones, dependency management, risk registers, and earned value tracking. - Partner with Engineering, Product, and Data Science leadership to align program roadmaps with business priorities, capacity constraints, and strategic objectives. - Drive the shift from bespoke, one-off execution to scalable, repeatable program infrastructure — ensuring teams build for hundreds of integrations, not one at a time. - Personally lead the highest-stakes programs when complexity, risk, or organizational span demands senior TPM ownership. Cross-functional Influence & Stakeholder Management: - Operate as a credible peer to VPs and Sr. Directors — not just a coordinator, but a strategic partner with a clear point of view on tradeoffs, priorities, and risk. - Communicate program status, risks, and strategic dependencies to the CTO,SVP of Engineering and executive leadership with clarity, precision, and appropriate urgency. - Build and maintain alignment across Engineering, Product, Legal, Data, and Operations on programs that cut across organizational boundaries. - Surface and resolve cross-functional blockers that cannot be handled at the team level — escalating with a recommended resolution, not just a flag. Process, Tooling & Governance: - Use of AI tools and skills for acceleration of automations from the perspective of TPM artifacts. Claude / Gemini / Cursor / Codex preferred - Establish and continuously improve the standard TPM toolkit: program templates, RAID frameworks, status reporting cadences, and planning rituals. - Champion Agile and scaled Agile (SAFe) practices across engineering teams, partnering with Engineering Managers to ensure methodology serves delivery — not the other way around. - Ensure programs reflect regulatory and compliance requirements (GDPR, CCPA, privacy-by-design) as first-class planning inputs, not afterthoughts. - Stay current on industry trends in ad tech, programmatic advertising, and digital measurement — bringing external perspective into internal planning. Now "WHO YOU ARE" section with bullet points (numbered list). Let's extract: - 10+ years of experience in technical program management, with at least 5+ years in a senior or lead TPM role. - Demonstrated experience managing and developing a team of TPMs — hiring, coaching, setting standards, and building a high-performance culture. - Deep domain expertise in ad tech — including programmatic advertising, audience data platforms, measurement and attribution solutions, identity, and/or data product delivery. This is a hard requirement; candidates without ad tech context will not be considered. - Proven track record operating as a peer to VPs and Sr. Directors — influencing strategic decisions, representing program risk at the executive level, and driving alignment across senior leadership. - Expertise in Agile, Scrum, and SAFe methodologies with hands-on experience driving adoption across engineering organizations. - Strong command of program governance: earned value metrics, dependency management, risk mitigation, and structured escalation frameworks. - Exceptional written and verbal communication — able to adapt from engineering deep-dives to executive briefings without losing precision or credibility. - Experience managing programs that span regulatory or compliance constraints (GDPR, CCPA, or similar privacy frameworks). - Background in software engineering, computer science, or a related technical field — prior hands-on engineering experience gives strong credibility with technical teams. - Experience with cloud-based data platforms, big data technologies, and/or real-time data pipeline infrastructure. - Familiarity with ACR (Automatic Content Recognition), connected TV data, or OEM-level data collection. - Experience managing TPM functions during periods of rapid organizational growth, M&A integration, or geographic expansion. - MBA or advanced technical degree — valued but not required where equivalent experience is clear. We need to output as
  • for any list of duties/requirements/benefits. So we can have a
    under Responsibilities containing all those bullet points (maybe grouped by subheadings? The instruction says use
    • for any list of duties/requirements/benefits. It doesn't forbid headings inside list? Probably we can keep subheadings as

      or

      ? But we only allowed

      for section headings. Could we use

      for subheadings? Probably we can just flatten list without subheadings, but that loses some structure. However we could keep subheadings as

      (plain paragraph) before the list. That's acceptable: we have section heading

      Responsibilities, then maybe a

      Organizational Leadership, then

      list. That seems okay. Similarly for Requirements: we can have

      Requirements, then maybe a

      (or just list). Could also break into subheadings like Experience, Skills, etc. But we can just list all items. We must not include sections like Benefits, Pay, Schedule because no info. We must not include boilerplate: equal opportunity employer, privacy policy, AI tools note (though AI tools mention appears in Process, Tooling & Governance bullet: "Use of AI tools and skills for acceleration of automations from the perspective of TPM artifacts. Claude / Gemini / Cursor / Codex preferred". That's part of responsibilities, not boilerplate, so we keep it. We must remove duplicated lines: none. Now produce HTML fragment. Let's craft:

      About the role

      Samba is a media intelligence company. We know what the world is watching, reading, and thinking about — in real time, at scale, across every screen. Our data exists with the consent of over a billion people, organized into the most complete picture of consumer attention ever built. The biggest brands in the world use that picture to make smarter decisions. We think it’s the most interesting data asset on the planet, because it’s the most culturally relevant.

      We are looking for a Director of Technical Program Management to lead and grow our TPM function at a critical inflection point in the company's expansion. This is not a pure execution role — it is a strategic leadership position. You will be a peer to VPs and Sr. Directors across Engineering, Product, Data Science, and Executive Leadership, owning how we plan, execute, and govern complex programs that span the full ad tech stack: data collection, identity, audience platforms, measurement solutions, and third-party integrations. You will own, build and develop a small but high-impact team of TPMs, establish the frameworks and operating model that scale with the organization, and personally drive the most complex, cross-functional programs. The right candidate brings deep engineering discipline, ad tech domain knowledge a plus, proven people leadership, and the organizational instincts to operate credibly at the senior leadership level.

      Responsibilities

      Organizational Leadership

      • Lead, mentor, and grow a team of 2–4 TPMs, setting a high bar for program ownership, communication, and technical credibility.
      • Define the TPM team's operating model — how programs are staffed, governed, escalated, and reported — and evolve it as the organization scales.
      • Act as the senior-most TPM voice in leadership forums, representing program health, risk posture, and execution capacity to the CTO, SVP of Engineering and cross-functional peers.
      • Drive hiring decisions, performance development, and career growth for the TPM team.

      Program Strategy & Execution

      • Own the end-to-end program execution strategy for the technology organization's most complex, cross-functional initiatives — from annual planning through delivery.
      • Define and enforce program governance frameworks: scope