Staff Product Manager, Retail Media & Audiences

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting: It includes "About Pinterest" description, then mission, etc. Then details about role: "You, as the lead for PMNC and audience marketplace, will grow our RMN offerings and build the audience marketplace business from the ground up." Then "What You’ll Do" bullet list. Then "What We’re Looking For" bullet list. Then "In-Office Requirement Statement", "Relocation Statement", "At Pinterest we believe..." etc. Then salary range: "$193,759—$339,078 USD". Also mention equity eligibility. Benefits? Not explicit benefits listed. There's mention of equity, but not benefits like health etc. So we may not create Benefits section unless specific content. There's no explicit benefits list. So we skip Benefits. Pay section: we have salary range. Also mention equity eligibility. Could include that. Schedule: In-office requirement: 1-2 times/quarter in office, can be anywhere. So schedule: hybrid with occasional in-office. We'll include Schedule section. Now sections: - About the role: Could be the introductory description about Pinterest and the role context. The posting starts with "About Pinterest" then mission etc. That's about company, not role. But we can treat as About the role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. "About the role" could be the description of the role and mission. We'll include a paragraph summarizing the role: leading PMNC and audience marketplace, etc. - Responsibilities: from "What You’ll Do" list. - Requirements: maybe from "What We’re Looking For" list (experience, communication, etc.) plus location requirement? Could be Requirements. - Qualifications: maybe education: Bachelor's degree. - Skills: maybe analytical mindset, attention to detail, etc. But we might combine. We need to avoid duplication. Let's extract substantive content: About Pinterest (company description) maybe not needed for role but could be included in About the role? The instruction says do not repeat job title as heading, but we can include company overview as part of About the role? Might be okay. But we need to preserve ALL substantive information; we cannot omit company description if it's substantive. However, we could put it under About the role as a paragraph. Let's list all substantive paragraphs: 1. About Pinterest: "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 unique experiences and embrace the flexibility to do your best work. Creating a career you love? It’s Possible. At Pinterest, AI isn't just a feature, it's a powerful partner that augments our creativity and amplifies our impact, and we’re looking for candidates who are excited to be a part of that. To get a complete picture of your experience and abilities, we’ll explore your foundational skills and how you collaborate with AI. Through our interview process, what matters most is that you can always explain your approach, showing us not just what you know, but how you think. You can read more about our AI interview philosophy and how we use AI in our recruiting process here." 2. Problem statement: "Billions of dollars flow through Retail Media Networks (RMNs) onto advertising platforms like Pinterest every year, but it can be a sub-par experience for the RMN, the brand advertiser, and for Pinterest. The RMN’s fees are hidden, campaign setup and management is manual and slow, and Pinterest gets left out of most of the relationship. Pinterest Media Network Connect (PMNC) is Pinterest’s solution to this problem, with complete transparency and self-service capabilities. Pinterest was the first to do this style of solution to the problem, and it is being copied by larger adverting platforms as a result, so we know we’re on the right path. But changing the retail media network business is not enough. We have ambitions to support a fully transparent, fully self-service audience marketplace, where anyone can transact with anyone else to empower their campaigns with audiences that enhance their performance and reach." 3. Role description: "You, as the lead for PMNC and audience marketplace, will grow our RMN offerings and build the audience marketplace business from the ground up. Leading these products involves collaborating with a dynamic, motivated, and expert team of cross functional partners to build brand new systems, develop relationships with partners, automate processes, and champion our solutions internally. Your success will depend on leading the company through significant process changes, having deep empathy for our partners and advertisers, partnering with many stakeholders internally and externally." 4. What You’ll Do (list): - Grow and lead our PMNC business to a billion+ dollars of revenue. - Build a new audience marketplace offering from scratch into an industry-leading solution. - Lead product vision, strategy, technical development, and execution for PMNC and our audience marketplace business. - Develop a deep understanding of the business’s workflows, and automate what will make the business run better and faster. - Design and build billing user interfaces – both internal and external – for delightful experiences. - Translate insights into clear product requirements and collaborate with engineering, design, data analytics, marketing, research, and other product teams to drive measurable impact. - Communicate your strategy internally to ensure alignment, secure resources, and champion the roadmap’s vision. - Leverage AI to turbo-charge your own work, from writing to design to prototyping, and more. 5. What We’re Looking For (list): - Experience with retail media network solutions, audience marketplaces is a big plus. - Excellent communication and stakeholder alignment skills. - Proven ability to shepherd large cross-functional teams in a fast-paced, collaborative environment. - Strong analytical mindset, using data to guide decisions and optimize workflows. - Extreme attention to detail and meticulous design sense. - Track record of rapidly delivering user-focused solutions in a cross-functional setting. - Location around SF, NYC, or Palo Alto. - Bachelor’s degree in a relevant field such as Computer Science, or equivalent experience 6. In-Office Requirement Statement: "We recognize that the ideal environment for work is situational and may differ across departments. What this looks like day-to-day can vary based on the needs of each organization or role. This role will need to be in the office for in-person collaboration 1-2 times/quarter and therefore can be situated anywhere in the country." 7. Relocation Statement: "Relocation Statement: This position is not eligible for relocation assistance. Visit our PinFlex page to learn more about our working model." 8. At Pinterest we believe... (EEO etc) - boilerplate to remove. 9. Salary: "US based applicants only $193,759—$339,078 USD Our Commitment To Inclusion ..." Actually salary line: "US based applicants only $193,759—$339,078 USD". Also mention equity: "The position is also eligible for equity." Thus we have Pay section: salary range and equity eligibility. Schedule: In-office requirement: 1-2 times/quarter. Now we need to output HTML with

headings and appropriate content. We should not include sections with no specific content: Benefits (none), maybe Skills (we could extract skills from What We’re Looking For: communication, stakeholder alignment, analytical mindset, attention to detail, etc.) But we already have Requirements and Qualifications; Skills could be separate but we might combine. The instruction: prefer a few substantive sections over many thin ones. So we could merge Skills into Requirements or Qualifications. But we need to follow headings list; we can omit Skills if not substantive distinct. However we have communication, analytical, attention to detail - those are skills. Could put them under Skills. But we also have experience and education under Qualifications. Let's decide: - About the role: company mission + role description. - Responsibilities: What You’ll Do list. - Requirements: What We’re Looking For list (experience, communication, etc.) plus location? Might be better as Requirements. - Qualifications: Bachelor's degree or equivalent experience. - Skills: maybe we could extract specific skills like communication, stakeholder alignment, analytical mindset, attention to detail, track record of delivering solutions. But that overlaps with Requirements. To avoid thin sections, we could combine Requirements and Qualifications into one section? But headings list includes both; we could still include both but ensure they have content. Let's assign: Requirements: experience with RMN/audience marketplace, communication/stakeholder alignment, ability to shepherd cross-functional teams, analytical mindset, attention to detail, track record of delivering user-focused solutions, location preference (SF/NYC/Palo Alto). That's a list. Qualifications: Bachelor's degree in relevant field or equivalent experience. Skills: maybe we could list specific skills like communication, stakeholder alignment, analytical, attention to detail, but that duplicates. Could instead list "Excellent communication and stakeholder alignment skills, Strong analytical mindset, Extreme attention to detail and meticulous design sense." That's still similar. Given the instruction to prefer few substantive sections, we could omit Skills and put those under Requirements. But we must include headings only when posting has real specific content for it. If we omit Skills, that's fine. We'll not create a Skills heading. Similarly Benefits: none, omit. Pay: include salary range and equity eligibility. Schedule: include in-office requirement. Now we need to ensure we don't include boilerplate like EEO, relocation statement (we can include relocation statement as part of Schedule? Actually relocation statement is separate but not a heading; we can fold minor metadata into a short

or drop it. The relocation statement says not eligible for relocation assistance. That's minor metadata; we can include in a

under Schedule or maybe under About the role? Better to drop it as it's minor. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can drop relocation statement. In-office requirement is schedule info, not minor; we keep. Now we need to preserve all substantive information: we must not lose any substantive info. Let's list all substantive info we identified and ensure we include them. Substantive info blocks: - About Pinterest paragraph (mission, AI, etc.) - Problem statement (RMN, PMNC, audience marketplace ambitions) - Role description (lead for PMNC, grow RMN offerings, build audience marketplace, collaborate, lead company through process changes, empathy, partner with stakeholders) - What You’ll Do list (8 items) - What We’re Looking For list (8 items) - In-Office Requirement Statement (1-2 times/quarter office, can be anywhere) - Salary range ($193,759—$339,078 USD) - Equity eligibility (position eligible for equity) - Location around SF, NYC, or Palo Alto (already in What We’re Looking For) - Bachelor’s degree requirement (in What We’re Looking For) - Maybe also mention "US based applicants only" (we can include in Pay section) Now we need to map to sections. About the role: Could combine About Pinterest paragraph + problem statement + role description. That's a lot but okay. Responsibilities: What You’ll Do list. Requirements: What We’re Looking For list (excluding education and location? Actually location and education are part of that list; we could keep them there). But we might want to separate education into Qualifications. Thus Requirements list: experience with RMN/audience marketplace, communication/stakeholder