Director, Global Enterprise Solutions

We need to output HTML fragment with sections: h3 headings for sections that have content: About the role? The posting includes "At a Glance" description. Could treat that as "About the role". Also "What You Will Do" => Responsibilities. "What You Need" => Requirements/Qualifications/Skills. "What We Offer" => Benefits. Pay and Schedule not present (they say compensation varies, not specific). So we omit Pay and Schedule sections. Also location and work type could be minor metadata: we can put in a short p. Also we need to preserve all substantive info, not invent. Remove boilerplate like EEO etc. We'll keep location and work type in a p. We need to use

for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can combine Requirements, Qualifications, Skills into one section? The instruction: use those headings for section headings. It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can decide which sections to include based on content. We have content for About the role (At a Glance). Responsibilities (What You Will Do). Requirements/Qualifications/Skills (What You Need). Benefits (What We Offer). We'll not include Pay or Schedule. We need to use

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

  for prose. We need to preserve all substantive info; not invent or summarize away detail. So we need to keep the bullet points from responsibilities etc. The responsibilities are a long paragraph with semicolons separating items. We need to turn them into list items. The posting uses semicolons and colon. We need to extract each duty as separate

• . Must not lose any detail. Similarly for requirements: list of knowledge areas etc. We'll turn each bullet into
• . Also "What We Offer" list of benefits. We need to ensure we don't repeat job title as heading. Not include Job ID. We'll output only HTML fragment. Let's parse sections. First, location and work type: "Location: Tulsa, OK Work Type: Onsite". We'll put in a

  maybe:

  Location: Tulsa, OK | Work Type: Onsite

  Or just plain text. Use

  . Now About the role: The "At a Glance" paragraph: "The Director, Global Enterprise Solutions is responsible for the global delivery, operation, and support of H&P's enterprise business applications and data, translating business needs into solutions that deliver measurable value. Leading teams across the Western and Eastern Hemispheres, the Director owns the enterprise application portfolio, including ERP operations and support (Oracle E-Business Suite / Fusion and SAP), custom and low-code application development and integration, data engineering and analytics, and business-facing application functional support. The role partners with Global ERP Strategy on ERP strategy and migrations while owning steady-state operations, and will continue to integrate and standardize the combined H&P and KCA Deutag application and data estate. In doing so, the Director ensures Global IT delivers reliable, secure, cost-efficient, and scalable business applications and an AI-ready data foundation that support financial close, supply-chain execution, employee productivity, data-driven decision-making, and H&P's global growth, while empowering business and functional units with the right tools at the right cost." We'll put that in

  under

  About the role

  . Responsibilities: The "What You Will Do" section includes a preamble: "The following items represent the essential functions and accountabilities for this position. This description is not meant to be all inclusive nor to prevent other duties from being assigned when necessary. Responsibilities may change at any time with or without notice. Regular and reliable attendance is essential and required in performance of the job. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions of the job." Then list items separated by semicolons after colon? Actually after that paragraph, there is a list starting with "Strategic business solutions: partner with business units ..." and each item ends with a semicolon, then next item starts with capital letter. We need to split each item into
• . We'll keep the preamble as a

  before the

  . Then each duty as
  • . Let's extract items: 1. Strategic business solutions: partner with business units across Finance and Accounting, Supply Chain, Human Resources, Maintenance, and Operations to understand needs and translate them into enterprise application solutions that deliver measurable business value; own the enterprise solutions roadmap in alignment with corporate strategy and Global IT priorities. 2. Service transformation and simplification: transform and simplify what and how we deliver IT Services at H&P through the global operating model and adoption of AI and automation. 3. Business enablement: empower business and functional units with the right tools at the right cost. 4. Enterprise application portfolio: own the global operation, support, and enhancement of H&P's enterprise business applications, including ERP (Oracle E-Business Suite / Fusion and SAP), custom applications, and low-code / Power Platform solutions. 5. ERP operations and support: ensure ERP platforms are available, performant, and well supported for finance, supply chain, HR, and maintenance through functional analysis, development, configuration, and administration; partner with Global ERP Strategy, which owns ERP strategy, consolidation, and migrations, while owning steady-state operations and providing hypercare support during go-lives. 6. Business-critical process enablement: ensure business-critical processes such as financial close and supply-chain transaction processing run reliably, including coverage around period-end and other event-critical windows. 7. Application development and integration: lead custom and low-code application development, integrations, and workflow across the application estate, applying consistent SDLC, Agile, release, and change-management practices. 8. Data engineering and analytics: own trusted data platforms, business intelligence, dashboards, and reporting that provide the business with reliable data for decision-making. 9. AI-ready data foundation: deliver a scalable and easily accessible data repository to power AI models, tools, and products. Engage data engineering, application developers, and business analysts to assist in the art of the possible for AI solutions. 10. Application functional support: provide cross-functional application support that bridges IT and the business, resolving issues, managing enhancements, and improving how business teams use enterprise applications. 11. Solution and application architecture: set application architecture direction, standards, and governance; guide solution design, technology selection, and reuse in partnership with the enterprise architecture team. 12. Delivery governance: sponsor and govern application projects and enhancements, ensuring business case, scope, funding, resourcing, risk management, testing, acceptance criteria, and benefits realization are sufficient before and during execution. 13. Global delivery model: run a global delivery model across Tulsa, Aberdeen, and India, with clear role clarity, handoffs, and coverage for period-end and major incidents. 14. Major-incident leadership and executive communication: serve as the primary enterprise solutions leader during major application incidents; translate technical issues into business impact, coordinate response, and communicate clearly to IT and business leadership in business language rather than unnecessary technical detail. 15. Governance, risk, and compliance: partner with Information Security and Governance, Risk & Compliance on application access, segregation of duties, change control, audit readiness, and regulatory obligations relevant to financial and business systems. 16. Post-merger integration and standardization: continue to integrate, rationalize, and standardize the combined H&P and KCA Deutag application and data estate toward a single global operating model. 17. MSP and vendor oversight: manage application and data managed service providers and technology partners to defined SLAs and performance standards; partner with Supply Chain, which executes vendor negotiations and vendor management, providing the technical and performance requirements that inform sourcing and renewals. 18. People leadership: lead, develop, and organize a global, multi-site team of managers, functional analysts, developers, and data engineers across the Western and Eastern Hemispheres; build bench strength, succession, and leadership standards consistent with H&P's job-architecture levels (for example P4, M2, M3, and M4). 19. Financial stewardship: partner with IT Business Operations on the enterprise solutions budget, forecast, and savings across software licensing, MSP labor, internal labor, and functional support, running the function with disciplined spend-to-value optimization. We need to ensure each
  • ends with a period? Keep as is. Now Requirements/Qualifications/Skills: The "What You Need" section includes a paragraph: "This level of knowledge is normally acquired through a Bachelor's Degree in Computer Science, Information Systems, Engineering, Business, or a related field or 12 or more years of progressive enterprise applications and delivery experience, including significant" then a list of knowledge areas each on new line starting with "Advanced knowledge of ..." etc. We'll treat the first sentence as a

    maybe. Then list items as

    • . Let's extract items: - Advanced knowledge of enterprise business applications and ERP (Oracle E-Business Suite / Fusion and/or SAP) - Advanced knowledge of application development and integration, including custom development and low-code / Power Platform - Advanced knowledge of data engineering, business intelligence, and analytics - Advanced knowledge of SDLC, Agile / DevOps, release, and change management - Advanced knowledge of application and solution architecture, standards, and governance - Strong understanding of core business processes: financial close and record-to-report, procure-to-pay and supply chain, HR and payroll, and maintenance / EAM - Experience running business-critical applications to defined availability and period-end commitments - Experience managing managed service providers (MSPs) and technology partners to SLAs, including executive escalation and roadmap alignment - Experience with global delivery and center-of-excellence models, including India-anchored delivery - Experience with post-merger application rationalization and integration preferred - Knowledge of application security, segregation of duties, and audit and regulatory requirements for financial systems - Financial acumen: software licensing, MSP labor, internal labor, and functional support cost management (FinOps) - Excellent executive communication, interpersonal, and stakeholder-management skills - Ability to travel domestically and internationally (passport required) Also there is a line "Work Experience 12 or more years of progressive experience in enterprise applications, ERP (Oracle E-Business Suite / Fusion and/or SAP), application development, and data and analytics, including significant experience leading global delivery teams, managed-service partners, and business-facing functional support. Experience in oil and gas or another asset-intensive industry is strongly preferred, as is experience with post-merger application integration, SDLC and Agile delivery, and functional support to Finance, Supply Chain, HR, and Maintenance. Experience managing multimillion-dollar application budgets and MSP portfolios is expected." We could treat that as additional requirements/experience. Could be part of Requirements section. We'll include as list items as well. Thus we will have a

      Requirements

      maybe combine Qualifications and Skills? The instruction says we can use those headings. We could have separate headings for Requirements, Qualifications, Skills if we have content. But we have mixed content. To keep few substantive sections, we could just use one heading "Requirements" and include all. Or we could split into Requirements (education/experience), Qualifications (knowledge), Skills (skills). But that may create thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So better to combine into one section, maybe "Requirements". Use

      Requirements

      . Then include all items as list. Now Benefits: "What We Offer" list: Comprehensive medical, dental, vision, and life insurance; Flexible Spending or Health Savings Accounts; 401k match; Paid Leave Plans; Parental & Adoption Benefits; Disability Coverage; Employee Assistance Program; Educational Assistance; Learning & Development Opportunities; Flex-scheduling available for qualifying positions to achieve work-life integration. We'll put each as
    • under

      Benefits

      . Now we need to