Agile Delivery Lead - Core Platform

We need to output HTML fragment with sections: About the role? The posting includes description paragraphs. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real content. We need to parse the posting: It starts with description about firm and role. Could be "About the role". Then responsibilities listed under "Responsibilities Include". Then qualifications under "Qualifications". Then experience under "Experience". Also there is "Compensation & Benefits" with salary range and benefits. Also maybe "Portfolio Functions And Technologies Include" could be part of responsibilities or qualifications? Probably part of responsibilities. We need to avoid repeating job title. No Job ID. Remove boilerplate: EEO, accommodation, etc. Also remove application instructions lines like "For technical difficulties..." and accommodation email etc. Also remove "Gibson Dunn will consider for employment qualified Applicants with Criminal Histories..." maybe keep? It's a statement about criminal histories; could be considered EEO/boilerplate? Might be considered legal boilerplate; but it's not exactly EEO; but it's a statement about criminal history consideration. Might be considered boilerplate; safer to remove? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This line about criminal histories is likely legal/EEO related. So remove. Also remove the lines about accommodation etc. Thus we keep: firm description, role location, role overview, responsibilities, qualifications, experience, compensation & benefits. We need to decide sections: About the role (summary). Responsibilities (list). Requirements? Could combine qualifications and experience? The posting has "Qualifications" and "Experience". Could treat "Qualifications" as a section, and maybe "Experience" as part of Qualifications? But we can have both Qualifications and Experience sections if they have content. The instruction: Prefer a few substantive sections over many thin ones. But we need to include sections only when posting has real specific content. We have both Qualifications and Experience; they are distinct. Could combine into one "Qualifications" section that includes both bullet lists. But we have to preserve all substantive information; we can merge but not lose detail. It's okay to combine. However the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but not mandatory to use all. We can choose which to include. We have content for About the role, Responsibilities, Qualifications (including experience), Benefits, Pay. No Schedule. No Skills separate (could be part of Qualifications). We'll include About the role, Responsibilities, Qualifications, Benefits, Pay. We need to use

for section headings. Use

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

  for prose. We need to preserve all substantive information; not invent or summarize away detail. So we need to keep the bullet points exactly as in posting? We can rephrase? Must preserve all substantive information; we can keep the same wording but maybe restructure as list items. Should not omit any detail. Let's extract sections. About the role: The first paragraph(s) up to "Based in New York City or Washington, D.C., the Agile Delivery Lead will be responsible for overseeing the planning, execution and delivery of initiatives within the firm’s Core Platform portfolio." Also includes description of firm and role blending etc. We'll capture that as prose. Responsibilities: Under "Responsibilities Include" there are several bullet-like paragraphs each starting with a bold heading? Actually they are sentences: "Delivery & Execution Leadership Lead the delivery lifecycle..." etc. We need to turn each into list items. The content includes multiple sentences per responsibility. We'll keep each responsibility as a list item, preserving the sentences. Let's list them: - Delivery & Execution Leadership Lead the delivery lifecycle for initiatives across the Business Applications portfolio. Drive predictable and transparent execution by facilitating planning, prioritization, and delivery cadence. Serve as Scrum Master or Delivery Lead for priority initiatives, removing impediments and supporting team focus. Promote effective Agile and hybrid delivery practices tailored to the team and project context. Use delivery and flow-based metrics (cycle time, throughput, capacity) to inform planning and drive improvement. - Portfolio Alignment & Visibility Provide visibility into delivery status, risks, milestones, and interdependencies across the portfolio. Support roadmap planning and help ensure alignment with business objectives and technology strategy. Identify opportunities to streamline workflows, eliminate inefficiencies, and strengthen delivery predictability. - Cross Functional Collaboration Partner with business stakeholders to translate needs into actionable backlogs and delivery plans. Collaborate closely with engineering, QA/UAT, infrastructure, and security teams throughout the delivery lifecycle. Communicate goals, progress, decisions, and risks effectively to senior leaders and project sponsors. Coordinate release planning, cutovers, and transition activities for smooth production deployments. - Process Improvement & Governance Develop and refine delivery processes, standards, and templates that promote consistency and quality. Ensure adherence to change management, compliance, and security requirements across delivery efforts. Support application rationalization and optimization efforts to increase overall portfolio value. Champion a culture of continuous improvement within and across delivery teams. - Documentation, Reporting & Communications Create and maintain delivery plans, RAID logs, dashboards, roadmaps, and other key artifacts. Produce executive-level reporting on delivery performance, portfolio health, and strategic risks. Document team operating models, Agile practices, and lifecycle procedures as required. - Stakeholder & Vendor Management Act as a primary liaison for vendors supporting application enhancements, integrations, or upgrades. Monitor vendor performance and coordinate delivery expectations, milestones, and operational handoffs. Facilitate intake, triage, and prioritization of discussions with internal stakeholders and external partners. Contribute to improving vendor tools, processes, and engagement models that support effective delivery. We need to keep all that. Qualifications: The posting has "Qualifications" bullet list (actually sentences). Then "Experience" bullet list. We'll combine maybe under Qualifications section with subheadings? But we cannot add extra headings beyond allowed? We could just list all items as list items under Qualifications. That would mix qualifications and experience; still preserves all info. That's acceptable. Let's extract Qualifications items: - Strong understanding of enterprise applications, integration patterns, and application lifecycle management. - Practical expertise with Agile frameworks (Scrum, Kanban, SAFe) and scalable delivery practices. - Proficiency with delivery and work management tools such as Azure DevOps, Jira, VersionOne, or Rally. - Familiarity with cloud platforms (Azure, AWS), DevOps practices, and CI/CD concepts. - Deep knowledge of change management, release planning, and IT governance. - Exceptional communication, facilitation, and stakeholder engagement abilities. - Strong influencing skills with the ability to work across business and technical teams. - Analytical, adaptable, and able to navigate complex, fast-moving environments. - Proven ability to manage multiple priorities while maintaining delivery focus and quality. Experience items: - Bachelor’s degree in Information Technology, Computer Science, Business, or related field. - 8+ years of experience in application lifecycle management, program/project management, product ownership, or Agile delivery leadership. - Experience leading Agile teams or hybrid teams in a professional services, legal, financial, or similarly regulated environment. - Demonstrated success managing complex application or multi-team delivery environments. - Certifications such as CSM, CSPO, SAFe Agilist, PMI-ACP, or equivalent. - Experience supporting legal-industry applications or working in a law-firm environment. - Familiarity with ITIL or service management frameworks. - Experience with application rationalization and data-driven prioritization techniques. We'll combine. Benefits: Under "Compensation & Benefits": Benefits offered for this position include health care; retirement benefits; paid days off, including sick time, and vacation time; parental leave; basic life insurance; Flexible Spending Accounts; as well as discretionary, performance-based bonuses. Pay: The annual compensation range for this position is $175,000 – 210,000. The salary offered within this range will depend upon qualifications and other operational considerations. We need separate sections for Benefits and Pay. Use

  Benefits and

  Pay. We should not include Schedule. Now produce HTML fragment. We need to ensure we don't include any extra text outside HTML. Let's craft:

  About the role

  Gibson Dunn is a leading global law firm, advising clients on significant transactions and disputes. Our exceptional teams craft and deploy creative legal strategies that are meticulously tailored to every matter, however complex or high-stakes. The firm’s work is distinguished by a unique combination of precision and vision. Based in New York City or Washington, D.C., the Agile Delivery Lead will be responsible for overseeing the planning, execution and delivery of initiatives within the firm’s Core Platform portfolio. This role blends Agile delivery leadership, process optimization, cross team coordination and portfolio visibility to ensure applications and services are delivered predictably, aligned to strategy and continuously optimized. This role requires strong technical fluency to support decision-making and stakeholder alignment, as well as strong delivery discipline, experience guiding Agile teams, and the ability to influence without direct authority across business and technical functions.

  Then responsibilities list.

  Responsibilities

  • Delivery & Execution Leadership Lead the delivery lifecycle for initiatives across the Business Applications portfolio. Drive predictable and transparent execution by facilitating planning, prioritization, and delivery cadence. Serve as Scrum Master or Delivery Lead for priority initiatives, removing impediments and supporting team focus. Promote effective Agile and hybrid delivery practices tailored to the team and project context. Use delivery and flow-based metrics (cycle time, throughput, capacity) to inform planning and drive improvement.
  • Portfolio Alignment & Visibility Provide visibility into delivery status, risks, milestones, and interdependencies across the portfolio. Support roadmap planning and help ensure alignment with business objectives and technology strategy. Identify opportunities to streamline workflows, eliminate inefficiencies, and strengthen delivery predictability.
  • Cross Functional Collaboration Partner with business stakeholders to translate needs into actionable backlogs and delivery plans. Collaborate closely with engineering, QA/UAT, infrastructure, and security teams throughout the delivery lifecycle. Communicate goals, progress, decisions, and risks effectively to senior leaders and project sponsors. Coordinate release planning, cutovers, and transition activities for smooth production deployments.
  • Process Improvement & Governance Develop and refine delivery processes, standards, and templates that promote consistency and quality. Ensure adherence to change management, compliance, and security requirements across delivery efforts. Support application rationalization and optimization efforts to increase overall portfolio value. Champion a culture of continuous improvement within and across delivery teams.
  • Documentation, Reporting & Communications Create and maintain delivery plans, RAID logs, dashboards, roadmaps, and other key artifacts. Produce executive-level reporting on delivery performance, portfolio health, and strategic risks. Document team operating models, Agile practices, and lifecycle procedures as required.
  • Stakeholder & Vendor Management Act as a primary liaison for vendors supporting application enhancements, integrations, or upgrades. Monitor vendor performance and coordinate delivery expectations, milestones, and operational handoffs. Facilitate intake, triage, and prioritization of discussions with internal stakeholders and external partners. Contribute to improving vendor tools, processes, and engagement models that support effective delivery.
  Qualifications section:

  Qualifications

  • Strong understanding of enterprise applications, integration patterns, and application lifecycle management.
  • Practical expertise with Agile frameworks (Scrum, Kanban, SAFe) and scalable delivery practices.
  • Proficiency with delivery and work management tools such as Azure DevOps, Jira, VersionOne, or Rally.
  • Familiarity with cloud platforms (Azure, AWS), DevOps practices, and CI/CD concepts.