Manager, Engineering, Enterprise Data Platform

We need to output HTML fragment with sections: About the role (but note they said do NOT repeat the job title as a heading; we can have About the role heading). Use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. Include sections only when posting has real specific content. Must include sections: About the role (the description after "About The Role" paragraph). Responsibilities (list of primary job responsibilities). Requirements (maybe combine Basic Qualifications and Preferred Qualifications? They said use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have: - About The Role: paragraph(s) describing role. - Primary Job Responsibilities: list of responsibilities. - Basic Qualifications: list (Bachelor's/Master's, 8+ years, 2+ years leadership, work auth). - Preferred Qualifications: list (experience, SQL/Python, etc.) - Benefits + Compensation at PitchBook: includes benefits categories (Physical Health, Emotional Health, Social Health, Financial Health) and then Compensation: Annual base salary range, Target annual bonus percentage. - Working Conditions: description about office 5 days a week, standard office setting, PC/phone, limited travel. We need to decide headings: About the role (h3). Responsibilities (h3). Requirements (maybe combine Basic and Preferred? Could have Requirements heading for basic qualifications, and Preferred Qualifications maybe under Skills? Or we could have Requirements and Qualifications separate. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include multiple of those as appropriate. We need to include Benefits, Pay sections if posting actually states them. Yes, we have benefits and compensation. So we should have Benefits (h3) and Pay (h3) maybe. Also Schedule (h3) if posting states schedule: "This role is expected to be in the office 5 days a week." That's schedule info. So we can include Schedule. We should not include sections with filler like "commensurate with experience". Not needed. We must not repeat job title as heading. Not include Job ID etc. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting. We need to format lists with

  • . For prose use

    . We need to avoid boilerplate like EEO etc. Not present. We need to remove duplicated lines. Not seeing duplicates. We need to output only HTML fragment, no /, no markdown fences. Let's craft. Structure:

    About the role

    ... (the paragraph(s) from About The Role). There are two paragraphs? Actually after "About The Role" there is a paragraph describing team, then "As a Data Engineering Manager..." That's also part of About the role? The heading "About The Role" then a paragraph about team, then "As a Data Engineering Manager..." continues. We'll combine into one

    maybe multiple

    but we can keep as multiple

    for readability. The instruction: use

    for prose. So we can have multiple

    elements. We'll extract the prose: "As a member of the Product and Engineering team at PitchBook, you will be part of a team of big thinkers, innovators, and problem solvers who strive to deepen the positive impact we have on our customers and our company every day. We value curiosity and the drive to find better ways of doing things. We thrive on customer empathy, which remains our focus when creating excellent customer experiences through product innovation. We know that greatness is achieved through collaboration and diverse points of view, so we work closely with partners around the globe. As a team, we assume positive intent in each other’s words and actions, value constructive discussions, and foster a respectful working environment built on integrity, growth, and business value. We invest heavily in our people, who are eager to learn and constantly improve. Join our team and grow with us!" Then second paragraph: "As a Data Engineering Manager within the Enterprise Data Platform team at PitchBook, you will lead a team of skilled data engineers responsible for building and optimizing data pipelines, managing large-scale data models, and ensuring the quality, availability, and performance of enterprise data assets. This leadership role combines technical depth, strategic thinking, and people management to enable PitchBook’s data-driven decision-making and analytics capabilities. You’ll collaborate closely with cross-functional partners across Technology & Engineering, Product, Sales, Marketing, Research, Finance, and Administration to deliver robust, scalable data solutions. The ideal candidate is a hands-on leader with a strong background in modern data platforms, cloud architecture, and team development—someone passionate about empowering teams and improving data capabilities across the organization. This is both a strategic and hands-on leadership role: you will guide architectural decisions, mentor engineers, collaborate with cross-functional leaders, and contribute to building next-generation data and AI capabilities at PitchBook. You will exhibit a growth mindset, be willing to solicit feedback, engage others with empathy, and help create a culture of belonging, teamwork, and purpose. If you love leading a team of passionate data engineers, building data-centric solutions, strive for excellence every day, are adaptable and focused, and believe work should be fun, come join us!" We'll put each as separate

    . Next section Responsibilities: we have list of responsibilities bullet points. We'll output

    Responsibilities

    then
    • each. List: - Lead, mentor, and retain top talent and develop a team of data engineers, fostering a culture of excellence, accountability, and continuous improvement - Define and drive the data engineering roadmap aligned with enterprise data strategy and business objectives - Collaborate with senior technology and business leaders to define data platform priorities, architecture, and long-term vision - Promote a culture of innovation, operational rigor, and customer empathy within the data organization - Oversee the design, development, and maintenance of high-quality data pipelines and ELT/ETL workflows across enterprise systems and PitchBook’s platform - Ensure scalable, secure, and reliable data architectures using modern cloud technologies (e.g., Snowflake, Airflow, Kafka, Docker) - Lead AI learning initiatives and integrate AI/ML-driven solutions into data products to enhance automation, predictive insights, and decision intelligence - Champion data quality, governance, lineage, and compliance standards across the enterprise data ecosystem - Partner with engineering and infrastructure teams to optimize data storage, compute performance, and cost efficiency - Support career development through mentoring, skill-building, and performance feedback - Support the vision and values of the company through role modeling and encouraging desired behaviors - Participate in various company initiatives and projects as requested We'll keep exactly. Next section Requirements: we could have Basic Qualifications as Requirements. Use

      Requirements

      then list. List: - Bachelor’s or Master’s degree in Computer Science or Engineering - 8+ years of experience in data engineering - 2+ years of leadership experience managing technical teams - Must be authorized to work in the United States without the need for visa sponsorship now or in the future We could also include Preferred Qualifications under a separate heading like "Preferred Qualifications" or "Skills". The instruction includes Skills heading. We could put Preferred Qualifications under Skills. But we need to preserve all substantive information. So we can have

      Preferred Qualifications

      (or Skills). The instruction says we can use Skills heading. Let's use

      Preferred Qualifications

      as a heading (though not in the example list but it's okay). Or we could use

      Skills

      and list them. But better to keep as Preferred Qualifications to avoid losing nuance. The instruction says "use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive. So we can use Preferred Qualifications. We'll output

      Preferred Qualifications

      then list. List: - Proven experience designing and maintaining large-scale data architectures, pipelines, and data models in cloud environments (e.g., Snowflake, AWS, Azure, or GCP) - Advanced proficiency in SQL and Python for data manipulation, transformation, and automation - Deep understanding of ETL/ELT frameworks, data orchestration tools (e.g., Airflow), and distributed messaging systems (e.g., Kafka) - Strong knowledge of data governance, quality, and compliance frameworks - Experience working with enterprise data sources (CRM, ERP, Marketing Automation, Financial Systems, etc.) is preferred - Hands-on experience with AI/ML platforms, model deployment, or data-driven automation is a strong plus - Excellent communication and stakeholder management skills with the ability to translate complex data concepts into business value - Demonstrated ability to build high-performing teams and lead through change Next Benefits: we have Benefits + Compensation at PitchBook: includes categories. We'll create

      Benefits

      then maybe subheadings? But we only allowed

      for section headings; we could still use

      for prose and

      • for lists. We could list each benefit category as
      • with subtext. But we need to preserve all detail. Could do
        • Physical Health: Comprehensive health benefits, Additional medical wellness incentives, STD, LTD, AD&D, and life insurance
        etc. That preserves details. Let's extract: 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: "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 note; we should preserve it as prose. We'll put that as a

        after the list. Next Pay: we have Compensation: Annual base salary: $225,000-$260,000; Target annual bonus percentage: 15%. We'll put

        Pay

        then

        Annual base salary: $225,000-$260,000

        Target annual bonus percentage: 15%

        maybe combine. Next Schedule: we have Working Conditions: "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'll put

        Schedule

        then

        ... maybe combine into one

        or multiple. We'll keep as one

        containing all. We should not include sections like "Qualifications" separate from Requirements; we already have Requirements and