Sr. Manager, Product Management

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Qualifications), Benefits, Pay, Schedule. Use

for each heading. Use

• for lists. Use

  for prose. Do not repeat job title. Do not include Job ID. Remove boilerplate. Include only sections with real content. We need to parse the posting. First part: introductory paragraph about PitchBook culture. That's not a section heading; we can include as a

  before sections? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other

  content outside sections. Probably we can include a brief intro paragraph before sections. Then "About The Role" heading: we have content after that: description of Navigator team, role, etc. Should be placed under

  About the role

  with paragraphs. Then "Primary Job Responsibilities": list of responsibilities bullet points. Use

  Responsibilities

  with
  • . Then "Basic Qualifications" and "Preferred Qualifications": combine into Requirements/Qualifications. Could have

    Requirements

    with two sub-sections? But instruction: use headings for section headings like Requirements, Qualifications, Skills. We could have

    Qualifications

    and inside list basic and preferred? Might be better to have

    Requirements

    with two lists: Basic Qualifications (Basic) and Preferred? But they said use headings for section headings; we can have multiple headings. Probably we should output

    Basic Qualifications

    and

    Preferred Qualifications

    as separate headings? The instruction list includes "Requirements, Qualifications, Skills". It doesn't forbid using Basic Qualifications heading. Safer to follow the given examples: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those exact headings if content exists. We have content for Basic Qualifications and Preferred Qualifications; we could combine into a single

    Qualifications

    with two sub-lists labeled Basic and Preferred using

    or . But we must not invent placeholder text. We can include a

    stating "Basic Qualifications:" then list, then another

    for "Preferred Qualifications:" then list. That's fine. Then Benefits: we have a Benefits + Compensation section with details. We'll make

    Benefits

    with list. Pay: we have compensation: Annual base salary: $190,000-$235,000; Target annual bonus percentage: 20%. So we can make

    Pay

    with

    containing that. Schedule: we have Working Conditions: expectation to be in office 5 days a week, standard office setting, etc. So we can make

    Schedule

    with

    describing. We must not include sections like Skills if not present. We have no explicit Skills section; we can omit. We must not include boilerplate like EEO, etc. The posting includes some encouragement to apply etc. That's near end: "We are excited to get to know you..." and "Concerned that you might not meet every requirement? We encourage you to still apply..." That's basically application instructions / encouragement. Should we remove? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove the final paragraphs that are application instructions. So we stop before that. Thus final HTML: start with maybe an intro

    about PitchBook culture (the first paragraph). Then

    About the role

    with paragraphs describing Navigator team and role. Then

    Responsibilities

    with
    • each responsibility. Then

      Qualifications

      with

      Basic Qualifications:

      ... and

      Preferred Qualifications:

      ... Then

      Benefits

      with
      ... Then

      Pay

      with

      ... Then

      Schedule

      with

      ... Make sure to preserve all substantive information. Let's extract details. Intro paragraph: "At PitchBook, a Morningstar company, we are always looking forward. We continue to innovate, evolve, and invest in ourselves to bring out the best in everyone. We’re deeply collaborative and thrive on the excitement, energy, and fun that reverberates throughout the company. Our extensive learning programs and mentorship opportunities help us create a culture of curiosity that pushes us to always find new solutions and better ways of doing things. The combination of a rapidly evolving industry and our high ambitions means there’s going to be some ambiguity along the way, but we excel when we challenge ourselves. We’re willing to take risks, fail fast, and do it all over again in the pursuit of excellence. If you have a good attitude and are willing to roll up your sleeves to get things done, PitchBook is the place for you." That's fine. About the role: after "About The Role". Content: "The Navigator team sits within PitchBook's product organization and is the primary driver of the company's Integrated AI Platform strategy. The team is building the foundational experience layer through which all AI-native workflows will be delivered: a persistent workspace, an agent routing engine, and a growing suite of workflow agents that serve sourcing, portfolio, and research use cases. We are seeking a product management leader to lead strategy, execution, and the team responsible for Navigator, PitchBook's AI platform experience. This leader owns the product strategy and roadmap — including the conversational interface, agent routing architecture, persistent workspace, and the specialist agents that serve user workflows from end to end. You will manage and develop a team of product managers, partner closely with Engineering, Design, Data Science, and Commercial teams, and serve as a key voice in PitchBook's broader AI strategy. This role requires a rare combination of AI product intuition, private markets domain knowledge, and the leadership presence to drive a high-velocity, high-stakes initiative across a large cross-functional organization." We'll put that as paragraphs. Responsibilities: list bullet points from "Primary Job Responsibilities". Let's extract each bullet: - Own Navigator product strategy and vision. Define and communicate a compelling multi-quarter vision and roadmap for Navigator's agentic platform — including the conversational interface and various workflow agents - Lead and grow a high-performing Product Management team. Hire, mentor, and manage a team of product managers, fostering a culture of customer empathy, data-driven decision-making, and continuous improvement. Evaluate Product Manager quality and develop role expectations as the team scales - Drive delivery of complex, cross-functional roadmaps. Partner with Engineering, AI/ML, Design, and Data leaders to execute against roadmap commitments with speed and quality. Remove blockers, manage dependencies, and maintain clarity and momentum across a large, distributed team - Define and measure business outcomes. Own clear success metrics for Navigator engagement, retention, and competitive differentiation. Build and interpret performance dashboards, validate impact post-launch, and continuously improve prioritization based on evidence - Shape PitchBook's AI product narrative. Act as a subject matter expert and internal thought leader for Navigator and agentic AI product strategy. Represent Navigator's direction to across internal and external stakeholders with clarity and conviction - Drive cross-functional alignment and stakeholder management. Build strong relationships with Commercial, Customer Success, Engineering, and Data leadership. Proactively communicate priorities, manage trade-offs, and maintain trust across a broad set of senior stakeholders - Contribute to team culture and organizational health. Support the vision and values of the company through role modeling, encouraging desired behaviors, and participating in hiring, onboarding, and team-building efforts We'll make each as

      • . Qualifications: Basic Qualifications: - Bachelor’s degree in Computer Science, Math, Statistics, Finance, or Accounting - 8+ years of product management experience within SaaS, enterprise, or cloud-based solutions - 4+ years managing product managers - Must be authorized to work in the United States without the need for visa sponsorship now or in the future Preferred Qualifications: - Demonstrated track record delivering AI/ML or conversational AI products in B2B SaaS environment - Understanding of agentic AI system architectures — including LLM orchestration, retrieval-augmented generation, and multi-agent patterns — sufficient to make sound technical trade-offs and credibly partner with engineering leadership - Passionate about or experienced in private capital markets — including VC, PE, M&A, or related financial services — with an understanding of how dealmakers source, diligence, and monitor investments - Experience influencing senior leadership through data-driven insights - Strong fluency with data: ability to build dashboards, interpret behavioral analytics, define success metrics, and validate product impact (e.g., Mixpanel, Snowflake, or equivalent) - Proven ability to define and communicate compelling product vision and roadmaps across multi-quarter, multi-team initiatives - Excellent communication and narrative skills: ability to craft and deliver clear, compelling presentations to executive leadership, commercial partners, and engineering teams alike - Experience leading and developing Product Management teams in fast-paced, high-ambiguity product environments - Proficiency with the Microsoft Office suite and modern product/collaboration tooling (Jira, Confluence, Figma, etc.) We'll output as lists. Benefits: The posting has "Benefits + Compensation at PitchBook:" then bullet categories: Physical Health, Emotional Health, Social Health, Financial Health. We'll extract each bullet. Physical Health: - Comprehensive health benefits - Additional medical wellness incentives - STD, LTD, AD&D, and life insurance Emotional Health: - Paid sabbatical program after four years - Paid family and paternity leave - Annual educational stipend - Ability to apply for tuition reimbursement - CFA exam stipend - Robust training programs on industry and soft skills - Employee assistance program - Generous allotment of vacation days, sick days, and volunteer days Social Health: - Matching gifts program - Employee resource groups - Subsidized emergency childcare - Dependent Care FSA - Company-wide events - Employee referral bonus program - Quarterly team building events Financial Health: - 401k match - Shared ownership employee stock program - Monthly transportation stipend Also note there is a sentence: "Please be aware the above PitchBook benefit and perk offerings are subject to corresponding plan and policy documents and may change during the course of your employment." That's a disclaimer; we could include as a

        after list, but it's not boilerplate? It's a note about benefits; we can keep as a

        . Pay: "Compensation Annual base salary: $190,000-$235,000Target annual bonus percentage: 20%" There's missing space; we'll format as "$190,000–$235,000" and "Target annual bonus percentage: 20%". We'll put in

        . Schedule: Working Conditions paragraph: "At the heart of our company is a belief in the power of in-person collaboration. Being together in the office fuels our creativity, strengthens our connections, and drives the innovation that sets us apart. Our culture is built on spontaneous moments—those hallway conversations, whiteboard brainstorms, and shared celebrations in each of our global offices—that simply can’t be replicated remotely. This role is expected to be in the office 5 days a week. The job conditions for this position are in a standard office setting. Employees in this position use PC and phone on an on-going basis throughout the day. Limited corporate travel may be required to remote offices or other business meetings and events." We