Staff Product Manager, Connections

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Pinterest" paragraph, then description of role, responsibilities, what we're looking for, qualifications, benefits/pay, schedule, etc. We must not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only when posting has real specific content. So we need to parse. Content: - Intro about Pinterest (mission). Could be "About the role"? Actually "About Pinterest" is company description. Could be placed under "About the role"? Probably "About the role" heading with description of role and mission. But we have "About Pinterest" paragraph describing mission. Then "As a Staff Product Manager for Connections..." describing role. Then "What You’ll Do" list of responsibilities. Then "What We’re Looking For" list of qualifications/requirements. Then "Nice to have:" etc. Then "Bachelor’s degree..." qualification. Then relocation statement etc. Then "In-Office Requirement Statement" schedule info. Then "At Pinterest we believe..." etc. Then salary range. Then benefits mention: "Information regarding the culture at Pinterest and benefits available for this position can be found here." Not specific benefits listed. So we cannot create Benefits section unless specific benefits listed. There's no explicit benefits like health, 401k, etc. So we should not create Benefits section. Pay: we have salary range: "$164,695—$339,078 USD". Also mention equity eligibility. So we can create Pay section with that. Schedule: we have in-office requirement: "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." Also mention remote? It says can be situated anywhere in the country. So schedule: hybrid, 1-2 days per quarter in office. So we can create Schedule section. Requirements: we have "What We’re Looking For" bullet list of qualifications. Also "Bachelor’s degree in a relevant field such as Computer Science, or equivalent experience." That's a qualification. Also "US based applicants only". That's a requirement (location). Also relocation statement not eligible for relocation assistance. That's maybe a note but not a requirement. We'll include under Requirements. Skills: maybe we can extract skills from "What We’re Looking For": technical and analytical depth, communication and storytelling, user-centric empathetic approach, etc. Could be separate Skills section. But we might combine Requirements and Skills? The instruction says use headings for those categories if content exists. We have content for Requirements (what we're looking for) and Skills (technical and analytical depth, communication, etc). Could split. Qualifications: maybe education requirement (Bachelor's degree). Could be separate Qualifications section. We need to avoid filler like "commensurate with experience". Not present. We must preserve all substantive information, not invent or summarize away detail. So we need to keep details. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. We must not include boilerplate like EEO, equal-opportunity, scam-warning, cookie/navigation/legal, duplicated lines, application instructions. So we need to remove the long EEO statement, the commitment to inclusion, the statement about false statements, etc. Also remove "Visit our PinFlex page to learn more about our working model." That's maybe not boilerplate but could be considered navigation? It's a link to internal page; but it's not a list item; it's a sentence. Might be considered part of description but maybe we can keep? It's not a list; it's a sentence about working model. Could keep under About the role? But it's not essential? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The PinFlex page is not exactly those; it's a link to working model. Might be okay to keep. However it's a sentence that could be considered navigation? I'd keep it as part of About the role. Also "Information regarding the culture at Pinterest and benefits available for this position can be found here." That's a link to benefits/culture; we can't list benefits, but we can keep as a sentence maybe under About the role? It's not a list; it's a reference. Might be okay. We must not create Benefits section unless specific benefits listed. So we will not create Benefits heading. Now produce HTML. Structure:

  About the role

  About Pinterest ... mission ... As a Staff Product Manager for Connections ... (the description). Also include the sentence about PinFlex and culture/benefits link maybe.

  Then responsibilities:

  Responsibilities

  • Support the end‑to‑end Connections strategy and roadmap, leading core experiences and systems that help Pinners connect with people and communities they trust, and translating that into measurable product impact.
  • Shape how social shows up on Pinterest by making connection experiences feel distinctly “Pinterest”: safe, personal, low‑pressure, and grounded in shared interests.
  • Create cohesive cross‑surface experiences by partnering with other Core product teams, so our connection features are consistent, useful, and help Pinners stay in the loop without feeling overwhelmed.
  • Drive alignment across a broad product area by bringing together senior leaders and cross‑functional partners (Engineering, Data Science, Design, Product Marketing, Policy, Research, and others) around a clear strategy, success measures, and execution plan for Connections, and by enabling teams to build on shared components and patterns.
  • Provide product leadership and mentorship across the Connections PM group, helping PMs sharpen strategy, execution, and product craft, and fostering a culture of experimentation and accountability to impact.
  • Champion safety, wellbeing, and trust by partnering with Policy, Trust & Safety, and Wellbeing to ensure connection experiences uphold Pinterest’s values, and by supporting guardrails and controls that let Pinners connect on their own terms and manage how they’re discovered, contacted, and notified.
  • Make Connections insight‑driven by defining how you’ll assess the health and impact of connection experiences with Data Science, and using quantitative and qualitative insights to guide prioritization, refine the roadmap, and communicate progress.
  • Represent Connections across Pinterest by serving as a senior product leader and key point of contact for the area, aligning the roadmap with company priorities, articulating the role of connections in Pinner value and business outcomes, and ensuring the work is understood and leveraged across adjacent teams.
  Then Requirements (what we're looking for):

  Requirements

  • Demonstrated track record of driving engagement and growth, leading high‑impact product work that improved user engagement and long‑term use, and clearly articulating your role in the strategy, metrics, and execution.
  • Experience setting roadmaps, and building healthy, high‑performing teams in ambiguous spaces.
  • AI forward experience with agentic tools to inform product strategy, roadmap, communication, and prototyping.
  • Strength in horizontal leadership and alignment, bringing together multiple product surfaces, infrastructure teams, and senior stakeholders around a shared plan, and making thoughtful tradeoffs and sequencing decisions.
  • Technical and analytical depth, including comfort with concepts like: recommendations, social graphs, messaging, large‑scale experimentation, and the ability to dive into data independently, and use insights to reshape the roadmap.
  • Communication and storytelling skills, with the ability to frame a clear narrative about Pinterest’s role in helping people feel connected, communicate complex ideas to diverse audiences, and generate buy‑in from executives, peers, and cross‑functional partners.
  • A user‑centric, empathetic approach to building products, especially in emotionally sensitive spaces like relationships, community, and belonging, and a track record of turning research and qualitative insights into thoughtful, differentiated product experiences.
  • Bachelor’s degree in a relevant field such as Computer Science, or equivalent experience.
  • US based applicants only.
  • Relocation Statement: This position is not eligible for relocation assistance.
  But relocation statement maybe not a requirement but a note; still we can include. Qualifications: maybe education already covered; but we could have Qualifications heading for Bachelor's degree. However we already included that in Requirements. To avoid duplication, maybe we keep Qualifications separate for education only. But we already have Bachelor's degree in Requirements. Could move it to Qualifications. Let's decide: We'll have Qualifications for education. Thus:

  Qualifications

  Bachelor’s degree in a relevant field such as Computer Science, or equivalent experience.

  But then we have duplicate if we also list in Requirements. Better to keep Requirements as the list of expectations (excluding education) and Qualifications for education. Let's adjust Requirements list to exclude Bachelor's degree. So Requirements list includes all bullet points except the Bachelor's degree. Then Qualifications section includes Bachelor's degree. Skills: we could extract technical and analytical depth, communication and storytelling, user-centric empathetic approach as skills. But those are already in Requirements list. Might be redundant. However we could create Skills section for those specific skill items. But we already have them in Requirements; we could keep them there and not create Skills. The instruction: Prefer a few substantive sections over many thin ones. So we can combine. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule. Pay section:

  Pay

  The base salary range for this position is $164,695—$339,078 USD. The position is also eligible for equity. Final salary is based on a number of factors including location, travel, relevant prior experience, or particular skills and expertise.

  Schedule section:

  Schedule

  This role requires in‑person collaboration 1‑2 times per quarter and can be situated anywhere in the country (hybrid).

  We should also include the sentence about "Visit our PinFlex page to learn more about our working model." and "Information regarding the culture at Pinterest and benefits available for this position can be found here." Where to place? Could be under About the role as extra prose. Thus About the role paragraph includes: "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. Each month, the Growth organization helps over 600M people around the world come back to Pinterest, discover new inspiration, and go deeper on the ideas they love. Connections is a key area within Growth focused on how people connect with others they care about on Pinterest — from close friends and family to trusted communities that share their interests. The Connections team builds products that make those relationships feel natural, safe, and uniquely “Pinterest.” As a Staff Product Manager for Connections, one of our