Director, Group Delivery Lead

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the job description. First, job title: Director, Group Delivery Lead. Not to repeat as heading. We need sections: About the role (maybe from first paragraph). Responsibilities (list of duties). Requirements/Qualifications (education, experience). Skills (maybe capabilities). Benefits (if present). Pay (if present). Schedule (if present). Also maybe "About Us" and "About The Team" but those are not in list; we should not create sections for them unless they map to allowed headings? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings. Other info like About Us, About The Team, Awards, etc. Should we include? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." But also "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use those for section headings. Likely we should map content to those headings where appropriate, and maybe include other headings like "About Us" if needed? But they said "e.g." implying those are examples, not exclusive. However they also say "Prefer a few substantive sections over many thin ones." So we could combine About Us and About The Team into maybe "About the company" but not in list. Safer to stick to the given headings. We need to extract content: About the role: The initial paragraphs describing role, location, opportunity, ideal candidate, impact. Could be under "About the role". We'll put that as prose

. Responsibilities: The bullet list after "In this role, you’ll make an impact in the following ways:" followed by items. Those are responsibilities. Use

• . Requirements/Qualifications: The "To be successful in this role, we’re seeking the following:" list includes education, experience, capabilities. Could split into Requirements (education, experience) and Qualifications (skills). But we can combine maybe under Requirements and Qualifications both. However we need to decide. We have: Bachelor’s degree or equivalent work experience... Advanced degree and/or relevant professional certifications... Typically 12-15 years of experience Preferred 9+ years of experience in delivery leadership... Strong planning, execution, and portfolio management capabilities... Experience driving end-to-end delivery... Demonstrated ability to bring structure to ambiguity... Strong data literacy... Demonstrated ability to influence... Excellent communication... Understanding of enterprise SDLC processes is a plus; exposure to AI/ML-enabled solutions... That's a mix of qualifications and skills. We could make a "Requirements" section for education and experience, and a "Skills" section for capabilities. But the instruction says we can use both headings if content exists. Let's extract: Requirements (education & experience): - Bachelor’s degree or equivalent work experience in a related discipline (e.g., Engineering, Business, Information Systems, or related field). - Advanced degree and/or relevant professional certifications in project/program management, agile or product delivery frameworks preferred. - Typically 12-15 years of experience - Preferred 9+ years of experience in delivery leadership, strategy, business management, operations, program management, portfolio management, or a similar role supporting senior leadership in a complex environment. Qualifications/Skills: - Strong planning, execution, and portfolio management capabilities, ideally within AI/ML, data, technology, or transformation-focused organizations. - Experience driving end-to-end delivery across cross-functional teams, with practical knowledge of agile delivery methods, backlog management, dependency management, milestone tracking, and delivery metrics. - Demonstrated ability to bring structure to ambiguity, manage competing priorities, and support disciplined follow-through across complex initiatives. - Strong data literacy, including experience defining KPIs and OKRs, building executive-level reporting, and using analytics and visualization to inform decisions and improve outcomes. - Demonstrated ability to influence across a matrixed organization and build credibility with senior stakeholders through clear communication, sound judgment, and disciplined execution. - Excellent communication, analytical, and executive presentation skills, with the ability to synthesize complex information into clear action plans and practical recommendations. - Understanding of enterprise SDLC processes is a plus; exposure to AI/ML-enabled solutions or agentic AI operating models is beneficial. We could put those under "Skills". Or we could have "Qualifications" for education/experience and "Skills" for capabilities. Let's do that. Benefits: The posting includes a section "Our Benefits And Rewards" with description of compensation, benefits, wellbeing programs, flexible resources, health, paid leaves, 401(k), medical/dental/vision/life insurance, other benefits. Also mentions base salary info in Job Info section (not given). So we have benefits content. We'll create a Benefits section with that prose. Pay: The posting mentions "The expected base salary for this position when employment commences can be found in the Job Info section at the bottom of the posting." No actual number given. So we should NOT create a Pay section because no specific pay info. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have, so we can include Benefits. Pay we do not have specific numbers, so omit. Schedule: No mention of schedule (full-time, part-time, remote). Not given, so omit. Now we need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes EEO statement: "BNY is an Equal Employment Opportunity/Affirmative Action Employer - Underrepresented racial and ethnic groups/Females/Individuals with Disabilities/Protected Veterans." Also statements about at-will employment, etc. Those are boilerplate; we should remove them. Also the "About Us", "About The Team", awards maybe we can keep as part of About the role? But they are not under allowed headings. However we might keep them as part of "About the role" or maybe we could create an "About Us" section but not in list. Safer to incorporate relevant info into About the role? The About Us and About The Team are descriptive of company culture, awards. Could be considered part of "About the role" context. But we might just keep them as separate paragraphs under "About the role" or maybe we could create a section "About the company" but not required. The instruction: "Prefer a few substantive sections over many thin ones." So we could combine About Us and About The Team into a paragraph under About the role. Thus final HTML:

  About the role

  ... (combined description)

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Skills

  • ...
  ...

  Benefits

  ...

  Make sure no extra whitespace? It's fine. Now craft the content. About the role paragraph: combine initial description: "We’re seeking a future team member for the role of Director, Group Delivery Lead to join our AI Hub team. This role is located in New York City. This is a strong opportunity for an experienced delivery leader who can partner closely with AI/ML Engineering leadership to drive planning, prioritization, portfolio execution, stakeholder alignment, and operating rigor across a complex and evolving portfolio. The role is ideal for a highly organized operator and communicator who can connect strategy to delivery, create visibility across priorities, and enable disciplined execution across senior stakeholders and cross-functional teams. The successful candidate will bring structure to ambiguity, help leadership manage competing priorities, translate strategy into actionable plans, and strengthen how the organization plans, operates, and delivers across a broad AI/ML Engineering agenda. In this role, you’ll make an impact in the following ways:" Actually the responsibilities list follows; we could keep the introductory sentence before list as part of About the role. But we already have Responsibilities section for the list. So About the role can be everything before the list (including location, opportunity, ideal candidate, impact). We'll exclude the "In this role, you’ll make an impact..." as that leads into responsibilities; maybe we keep that as part of About the role but not list. Let's include up to "strengthen how the organization plans, operates, and delivers across a broad AI/ML Engineering agenda." Then responsibilities list. Thus About the role paragraph: "We’re seeking a future team member for the role of Director, Group Delivery Lead to join our AI Hub team. This role is located in New York City. This is a strong opportunity for an experienced delivery leader who can partner closely with AI/ML Engineering leadership to drive planning, prioritization, portfolio execution, stakeholder alignment, and operating rigor across a complex and evolving portfolio. The role is ideal for a highly organized operator and communicator who can connect strategy to delivery, create visibility across priorities, and enable disciplined execution across senior stakeholders and cross-functional teams. The successful candidate will bring structure to ambiguity, help leadership manage competing priorities, translate strategy into actionable plans, and strengthen how the organization plans, operates, and delivers across a broad AI/ML Engineering agenda." Now Responsibilities list items: - Drive planning across business priorities, AI/ML initiatives, resource needs, delivery commitments, and priority management to support execution against strategic goals. - Create portfolio visibility across strategic programs, including prioritization, dependency tracking, milestone management, executive reporting, and follow-through on key decisions. - Support executable roadmaps, backlogs, and planning cadences by aligning demand, capacity, sequencing, and delivery commitments across teams and partners. - Translate leadership strategy into actionable execution plans, helping ensure priorities are clearly defined, resourced, sequenced, and tracked. - Build strong relationships across engineering, product, business, risk, finance, operations, and delivery stakeholders to align priorities, resolve dependencies, and accelerate execution. - Orchestrate leadership forums, decision cadences, status reviews, and follow-up actions to support timely decision-making, transparency, and operational discipline. - Help strengthen governance, delivery discipline, control effectiveness, and operating efficiency through metrics, analytics, process improvements, and clear communication of risks, dependencies, and tradeoffs. - Facilitate engagement with risk, governance, and control partners while helping clarify business, commercial, and delivery needs. - Prepare executive-level materials, insights, and recommendations that synthesize complex information into clear action plans and practical decisions. Now Requirements list: - Bachelor’s degree or equivalent work experience in a related discipline (e.g., Engineering, Business, Information Systems, or related field). - Advanced degree and/or relevant professional certifications in project/program management, agile or product delivery frameworks preferred. - Typically 12-15 years of experience - Preferred 9+ years of experience in delivery leadership, strategy, business management, operations, program management, portfolio management, or a similar role supporting senior leadership in a complex environment. Now Skills list: - Strong planning, execution, and portfolio management capabilities, ideally within AI/ML, data, technology, or transformation-focused organizations. - Experience driving end-to-end delivery across cross-functional teams, with practical knowledge of agile delivery methods, backlog management, dependency management, milestone tracking, and delivery metrics. - Demonstrated ability to bring structure to ambiguity, manage competing priorities, and support disciplined follow-through across complex initiatives. - Strong data literacy, including experience defining KPIs and OKRs, building executive-level reporting, and using analytics and visualization to inform decisions and improve outcomes. - Demonstrated ability to influence across a matrixed organization and build credibility with senior stakeholders through clear communication, sound judgment, and disciplined execution. - Excellent communication, analytical, and executive presentation skills, with the ability to synthesize complex information into clear action plans and practical recommendations. - Understanding of enterprise SDLC processes is a plus; exposure to AI/ML-enabled solutions or agentic AI operating models is beneficial.