Data Engineer, VP - Systems and Data Engineering

We need to output HTML fragment with sections: About the role? The posting includes description about Blackstone and role. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We have responsibilities (Key Responsibilities with subpoints). We have Qualifications (Required and Preferred). We have Benefits (Additional compensation and benefits). We have Pay (Expected annual base salary range). We have Schedule? Not mentioned. So omit Schedule. Skills? Could be derived but not explicit separate section; maybe we can include Skills if there is content like "Experience with Snowflake, ETL/ELT, etc." but that's part of qualifications. Better to not create Skills unless explicit. The instruction: "Prefer a few substantive sections over many thin ones." So we can have About the role (intro paragraph), Responsibilities, Qualifications, Benefits, Pay. Possibly also include "About the role" summarizing the description about Blackstone and role overview. That seems appropriate. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, accommodation, securities license, application instructions. Also remove navigation/footer etc. Keep substantive info. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like responsibilities bullet points, qualifications details, benefits list, pay range. We must use

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

  for prose. We need to format headings with

  . For each section, we put heading then content. Let's extract content. About the role: The first paragraphs: "Blackstone is the world’s largest alternative asset manager. Blackstone seeks to deliver compelling returns for institutional and individual investors by strengthening the companies in which the firm invests. Blackstone’s over $1.3 trillion in assets under management include global investment strategies focused on real estate, private equity, credit, infrastructure, life sciences, growth equity, secondaries and hedge funds. Further information is available at www.blackstone.com. Follow @blackstone on LinkedIn, X (Twitter), and Instagram. The Vice President, Data Engineering will be a key senior technical contributor to the engineering, delivery, reliability, and operational excellence of BXTI's enterprise data platforms and pipelines. This role provides technical leadership and hands-on expertise across Snowflake, data engineering, data quality, data operations, and platform support functions. The successful candidate will help advance engineering best practices, operational excellence, platform reliability, and continuous improvement while partnering closely with business stakeholders, application development teams, architecture, infrastructure, security, and data governance functions. This individual will operate as a senior hands-on technical leader and trusted contributor, offering architectural guidance, engineering direction, and operational expertise across multiple teams and initiatives without direct people management responsibility." We can keep that as prose in

  . Possibly split into multiple paragraphs but one is fine. Responsibilities: The "Key Responsibilities" section with subheadings: Technical Leadership, Snowflake Platform Leadership, Data Engineering, ETL, and Pipelines, Data Quality and Governance, Data Operations and Reliability, On-Call and Incident Management, Cross-Functional Partnership. Each has bullet-like sentences. We need to turn each duty into

  . Could group under a single

  with all responsibilities, or separate subheadings? The instruction: use

  for section headings; use

  • for any list of duties/requirements/benefits. It doesn't forbid having subheadings inside a list? Probably better to keep a single Responsibilities section with a
    containing each duty as
    • . We need to preserve all detail; we can keep the subheadings as part of the
    • text (maybe bold? but we cannot add extra tags besides

      ,

      ,

      ,
      • . We could embed the subheading as plain text within
      • . Eg: "
      • Technical Leadership: ..." but strong is not allowed? The instruction only says use those tags; doesn't forbid other tags but says output ONLY the HTML fragment — no /, no markdown code fences. It didn't restrict other tags, but to be safe we can stick to allowed tags. However we can still include other tags like maybe okay but not required. Safer to just use plain text. We'll create
      • items each starting with the responsibility title colon then description. List items: - Technical Leadership: Contribute as a senior technical leader to enterprise data engineering initiatives. Help establish engineering standards, design patterns, and best practices across data platforms and services. Provide technical leadership and mentorship to engineering teams across BXTI. Participate in architectural reviews and help guide key technology decisions related to data platforms and services. Partner with technology and business stakeholders to translate strategic requirements into scalable and supportable solutions. Lead investigations into Production incidents involving the data platform. - Snowflake Platform Leadership: Contribute technical and operational leadership for Snowflake-based data platforms. Support platform scalability, performance, security, resiliency, and cost optimization initiatives. Collaborate with various internal teams to ensure alignment with firm standards. - Data Engineering, ETL, and Pipelines: Contribute to the design and evolution of enterprise data ingestion, transformation, orchestration, and delivery platforms. Establish standards for ETL/ELT development, metadata management, lineage, observability, and automation. Drive adoption of engineering practices that improve reliability, maintainability, and operational efficiency. Promote reusable frameworks and common services that accelerate delivery and reduce operational risk. - Data Quality and Governance: Help define and champion enterprise data quality standards and controls. Drive implementation of automated data validation, monitoring, and remediation processes. Partner with technical and business teams to improve lineage, stewardship, consistency, and trust in critical datasets. Establish metrics and reporting to measure data quality and platform effectiveness. - Data Operations and Reliability: Provide technical oversight of production support, operational readiness, and platform reliability in partnership with the broader team. Contribute to efforts to improve monitoring, alerting, observability, and operational automation. Support root cause analysis and remediation activities for significant production incidents. Define and track service level objectives, operational metrics, and platform health indicators. - On-Call and Incident Management: Participate in the data engineering on-call rotation. Help support coverage, escalation procedures, and incident response processes in collaboration with the broader organization. Act as a senior escalation point during critical production events. Promote operational excellence through proactive risk management, resilience engineering, and continuous improvement. - Cross-Functional Partnership: Build strong partnerships across engineering, infrastructure, cybersecurity, governance, architecture, and business teams. Influence technology direction through collaboration, technical expertise, and strong delivery partnership. Communicate complex technical concepts effectively to both technical and non-technical stakeholders. Contribute to strategic planning, roadmap development, and platform investment decisions. Qualifications: There's "Qualifications Required" and "Preferred". Also "Success Measures". We could combine Required and Preferred into a single Qualifications section with two sublists? Or separate Required and Preferred as subheadings inside
        ? Probably better to have a Qualifications section with two
        lists: Required and Preferred. But we need headings for sub-sections? Not required; we can just have paragraphs describing required and preferred. However we need to use
        • for any list of duties/requirements/benefits. So we should list each qualification as
        • . We'll separate Required and Preferred maybe with a

          intro then

          . Required items: - 10+ years of experience in data engineering, platform engineering, or related disciplines. - Significant hands-on experience with Snowflake in large-scale enterprise environments. - Deep expertise in ETL/ELT architectures, data integration technologies, orchestration frameworks, and modern data platforms. - Experience supporting business-critical production systems operating in a 24x7 environment. - Strong background in data quality, observability, monitoring, and operational excellence. - Experience contributing to major incident response efforts and helping drive operational improvements. - Demonstrated experience influencing engineering organizations through technical leadership rather than direct authority. Preferred items: - Bachelor's degree in Computer Science, Engineering, Information Systems, or a related field. - Experience supporting analytics, reporting, AI, and machine learning platforms. - Experience with Infrastructure as Code, CI/CD, DevOps, and platform automation practices. - Familiarity with data governance, lineage, metadata management, and regulatory requirements within financial services. - Experience working across globally distributed engineering organizations. Success Measures: Could be considered as part of Qualifications or separate section? It's more like performance expectations. Could be included under Qualifications as additional list, but maybe better to include as a separate section "Success Measures" but not in allowed headings list. The allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Success Measures not listed; we could incorporate into Qualifications or Requirements. Probably better to add as a

          under Qualifications after lists. But we must not invent sections; we can include a paragraph describing success measures as part of Qualifications. Benefits: "Additional compensation and benefits offered in connection with the role consist of comprehensive health benefits, including but not limited to medical, dental, vision, and FSA benefits; paid time off; life insurance; 401(k) plan; and discretionary bonuses. Certain employees may also be eligible for equity and other incentive compensation at Blackstone’s sole discretion." We need to use

          • for list of benefits. So list each benefit. Pay: "Expected annual base salary range: $160,000 - $225,000 Actual base salary within that range will be determined by several components including but not limited to the individual's experience, skills, qualifications and job location. For roles located outside of the US, please disregard the posted salary bands as these roles will follow a separate compensation process based on local market comparables." We need to include Pay section with that info as prose (

            ). Should we include the note about outside US? Yes it's part of pay info. Schedule: Not present, omit. We must remove boilerplate: EEO, accommodation, securities license, application instructions. Also remove "The duties and responsibilities described here are not exhaustive..." etc. Also remove "Note: The above list is not the exhaustive list..." etc. Also remove "To submit your application please complete the form below." etc. Now construct HTML. We'll start with

            About the role

            then

            ...

            Then

            Responsibilities

            then
            • ...
            Then

            Qualifications

            then maybe

            Required:

            then
            ... then

            Preferred:

            then
            ... then

            Success Measures:

            then
            ... or we could just include success measures as

            prose. But we need to use

            • for any list; success measures is a list, so we should use
              • . Let's do that. Success measures list: - Reliable and scalable operation of Snowflake and enterprise data platforms. - High-quality delivery of data engineering solutions aligned to BXTI priorities. - Improved data quality, platform observability, and operational metrics. - Reduced incident volume and faster recovery from production issues. - Consistent adoption of engineering standards and best practices across teams. - Effective technical leadership and influence across the Systems and Data Engineering organization. We'll put that under Qualifications after Preferred maybe as a separate

                Success Measures:

                then
                . Now Benefits:

                Benefits

                • comprehensive health benefits, including but not limited to medical, dental, vision, and FSA benefits
                • paid time off
                • life insurance
                • 401(k) plan
                • discretionary bonuses
                • eligible for equity and other incentive compensation at Blackstone’s sole discretion
                Pay:

                Pay

                Expected annual base salary