Staff Technical Program Manager, Monetization Data Science

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We need to extract content from posting. We need sections: About the role (intro paragraph). Responsibilities (list of duties). Requirements (maybe qualifications). Skills (maybe specific skills). Benefits (maybe mention equity, etc). Pay (salary range). Schedule (in-office requirement). Also maybe Qualifications separate? The instruction says use headings for those categories; we can combine Requirements and Qualifications? Probably separate but we need to include only if content. Let's parse posting: Intro: "About Pinterest Millions of people..." That's about company, not role. Then "The Team ..." then "What You’ll Do" (responsibilities). Then "What We’re Looking For" (requirements/skills). Then "Bachelor’s degree ..." (qualification). Then "Relocation Statement", "In-Office Requirement Statement", "At Pinterest we believe..." (culture). Then "In an effort to provide greater transparency, we are sharing the base salary range for this position." Then salary range. Then "Our Commitment To Inclusion" (EEO) - remove boilerplate. Also "Visit our PinFlex page..." etc. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So remove the EEO paragraph, the "Visit our PinFlex page..." maybe not boilerplate but it's about working model; could be considered part of schedule? It mentions relocation not eligible, and PinFlex page. Might be considered metadata; we can fold into short p. We need to preserve all substantive information. Let's extract: About the role: maybe a paragraph summarizing role: "The Team Pinterest helps people find inspiration and take action on it—connecting pinners with ideas and products they love. Within EPD, the Monetization org builds the ads and merchant ecosystem that funds Pinterest’s business while protecting long-term user experience. This Staff TPM role sits in Monetization as the TPM lead for Monetization Data Science, at the center of a highly cross-functional network (Product, Engineering, Design, Sales, PMM, Core, Platforms, Data). What’s exciting is the team’s explicit shift toward a “data-driven monetization engine”: unifying fragmented data into a trusted SSOT, building an end-to-end input metrics funnel, enabling advanced segmentation, and democratizing analytics so teams can move faster and make better decisions with shared context." That seems appropriate for About the role. Responsibilities: bullet list from "What You’ll Do". Each sentence starting with a verb. We'll make

• items. List items: - Lead the Monetization DS execution roadmap: drive the integrated plan across the four strategic pillars (SSOT + funnel, segmentation, input-metrics cadence, democratized analytics) with clear milestones and success measures. - Productionalize our DS strategy: coordinate Platforms/Data Eng + Monetization Eng + DS to productionalize core tables, governance, reliability, and scale beyond DS-owned pipelines. - Enable new instrumentation: partner with Engineering to close observability gaps (especially delivery funnel instrumentation) so full-funnel survivability can be analyzed reliably. - Drive workflow automation: reduce manual human intervention in recurring data workflows and program operations; build durable mechanisms for monitoring, alerting, and dependency tracking. - Scale self-serve and democratization: deliver partner-facing tooling (dashboards / analytics surfaces) that makes staples the common language and supports fast diagnostics and opportunity mining. - Operationalize input metrics: establish/upgrade business review cadences so teams set goals and are accountable for moving controllable input metrics (not just reporting revenue outcomes). - Drive targeted deep dives: structure and execute cross-functional deep-dive programs (e.g., influencer population, auction density/demand) with clear hypotheses, decision asks, and downstream action plans. - Use GenAI as the default operating model for EP PgM execution—producing AI-assisted first drafts of core program artifacts, modernizing high-toil workflows into AI-first mechanisms (e.g., intake triage, status synthesis, action/decision extraction, risk & dependency tracking), and synthesizing signals to proactively surface risks, decision/trade-offs, and escalation paths. - Prototype solutions to augment decisions through data (e.g. dashboards, data analysis) or simplify processes (e.g. process and workflow helpers, or internal tools) using AI coding assistants (“vibe coding”). - Follow Pinterest AI guidance for risk, governance, and safety-by-design: appropriately handle sensitive data, validate AI-generated outputs, document assumptions/limits, and ensure AI-assisted workflows meet applicable policy/compliance expectations before broad adoption. That's many items; okay. Requirements/Qualifications/Skills: "What We’re Looking For" includes many bullet-like sentences. We need to split into Requirements (maybe core qualifications) and Skills (specific abilities). Could combine but better to separate: Requirements: Staff-level TPM scope and behaviors, Deep cross-functional leadership, Data platform + metrics judgment, Mechanism builder, Excellent risk and dependency management, AI-first execution mindset, Workflow design, AI fluency, data & insights orientation, Safety-by-design AI fluency, Bachelor’s degree. Skills: maybe the specific abilities like "proven ability to independently own multi-team, multi-quarter technical programs", etc. But those are similar. Could treat the list as Requirements and Skills combined? The instruction says we can have sections for Requirements, Qualifications, Skills. We need to decide what goes where. Qualifications: Bachelor’s degree in Computer Science, Engineering, a related field or equivalent experience. Requirements: the list of competencies (Staff-level TPM scope..., Deep cross-functional leadership..., Data platform + metrics judgment..., Mechanism builder..., Excellent risk and dependency management..., AI-first execution mindset..., Workflow design, AI fluency, data & insights orientation..., Safety-by-design AI fluency). Skills: maybe the specific abilities like "proven ability to independently own multi-team, multi-quarter technical programs, including resolving ambiguity, driving decisions, and delivering outcomes through influence." etc. But those are essentially the same as requirements. Might be redundant. Given the instruction to prefer a few substantive sections over many thin ones, we could combine Requirements and Skills into one section called Requirements (or Qualifications). But we have separate headings allowed; we could include Requirements and Skills if they have distinct content. Let's see if we can differentiate: Requirements list includes high-level competencies; Skills list includes more concrete abilities like "experience building trusted metrics/SSOT and operational cadences", "track record of creating durable operating systems", "experience turning repeatable program work into durable, low-toil mechanisms". Those are similar. Maybe we can treat "What We’re Looking For" as Requirements, and the Bachelor's degree as Qualifications. Skills maybe not needed. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule. Benefits: mention equity eligibility, maybe also mention "eligible for equity". Also "Visit our PinFlex page to learn more about our working model." Could be considered benefit? Not really. Benefits could be equity and maybe mention "eligible for equity". Also maybe mention "relocation not eligible" is not a benefit. So we can include Benefits: equity eligibility. Pay: salary range. Schedule: In-office requirement: 1-2 times every 6 months, can be situated anywhere in the country. Also mention relocation not eligible. Let's craft. We must not include boilerplate like "Our Commitment To Inclusion", "Visit our PinFlex page..." maybe we keep as part of Schedule? It's about working model; could be considered schedule/flexibility. We'll include a short p under Schedule: "This role is not eligible for relocation assistance. Visit our PinFlex page to learn more about our working model." Now produce HTML fragment. Structure:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • Staff-level TPM scope and behaviors: proven ability to independently own multi-team, multi-quarter technical programs, including resolving ambiguity, driving decisions, and delivering outcomes through influence.
  • Deep cross-functional leadership: strong partnership with Product and Engineering plus ability to align Design, Sales, PMM, Core, Platforms, and Data on sequencing, tradeoffs, and adoption.
  • Data platform + metrics judgment: experience building trusted metrics/SSOT and operational cadences that shift org behavior toward leading indicators and fast diagnosis.
  • Mechanism builder, not “process administrator”: track record of creating durable operating systems (cadence, dashboards, decision logs, RACI/DRIs) that reduce toil and increase velocity.
  • Excellent risk and dependency management: anticipates cross-org failure modes, keeps stakeholders aligned with crisp comms, and escalates with clear options and recommendations.
  • AI-first execution mindset: demonstrated ability to use GenAI to accelerate planning, program operations, and stakeholder communications—starting with AI drafts and applying strong judgment to validate, refine, and drive decisions.
  • Workflow design, AI fluency, data & insights orientation: experience turning repeatable program work into durable, low-toil mechanisms and improving decision-making by using GenAI (e.g., strong prompting, vibe coding lightweight scripts/tools, dashboards, data analysis and leveraging agents where appropriate).
  • Safety-by-design AI fluency: experience operating within AI governance expectations (risk assessment, data handling, model/output validation, auditability/traceability) and proactively identifying where AI use is not appropriate or requires additional controls.

  Qualifications

  Bachelor’s degree in Computer Science, Engineering, a related field or equivalent experience.

  Benefits

  Eligible for equity.

  Pay

  US based applicants only $145,747—$300,067 USD

  Schedule

  This role will need to be in the office for in-person collaboration 1-2 times every 6-months and therefore can be situated anywhere in the country. This position is not eligible for relocation assistance. Visit our PinFlex page to learn more about our working model.

  Check for any repeated content: Ensure we didn't include any boilerplate like EEO. We omitted. Check for any placeholder like "commensurate with experience" - none. Check for any duplicated lines: we have not. Check that we didn't invent content: all from posting. Check that we didn't miss any substantive info: The "What You’ll Do" list we captured all bullet points. The "What We’re Looking For" we captured all bullet points as requirements. The Bachelor's degree we captured. The equity mention we captured. Salary range captured. In-office requirement captured. Relocation statement captured. PinFlex page captured. We omitted the "The Team ..." part? Actually we included that in About the role. Good. We omitted the initial "About Pinterest Millions of people..." which is generic company description; maybe not needed for About the role? Could be considered part of About the role but it's generic; but we could include it as part of About the role. However the instruction says preserve ALL substantive information; that is substantive about company mission. Might be considered part of About the role. But we already have a paragraph about the team and role; we could prepend the company mission paragraph. Let's include it. Thus About the role paragraph: combine the company mission and team description. Let's craft: "Millions of people around the world come to our platform to find creative ideas, dream about new possibilities and plan for memories that will last a lifetime. At Pinterest, we’re on a mission to bring everyone the inspiration to create a life they love, and that starts with the people behind the product. Discover a career where you ignite innovation for millions, transform passion into growth opportunities, celebrate each other’s