ERP/AI Lead

We need to output HTML fragment with sections: About the role (General Summary), Responsibilities (Essential Job Accountabilities), Requirements (Education, Work Experience, Knowledge, Skills, And Abilities, Additional Requirements/Skills maybe), Benefits (Our Benefits At a Glance), Pay (Base Salary Range). Also maybe Schedule not present, so omit. Also include any other sections like Qualifications? Not needed. We must not repeat job title. No Job ID. Remove boilerplate: navigation, EEO, legal, etc. Remove "About Granite Construction Incorporated", "Drug-Free Workplace", etc. Also remove "Notice to Staffing Agencies". Also remove "Physical Demands"? It's substantive? It's about physical demands; maybe include under Requirements? But it's not a typical section; but we could include as part of Requirements? The instruction: include a section ONLY when posting has real, specific content for it. Physical Demands is specific content; we could create a section maybe "Physical Demands". However the allowed headings list includes: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Physical Demands not in list; we should not create new headings beyond those. So we should fold Physical Demands into Requirements or maybe Skills? Probably Requirements. Also "Additional Requirements/Skills" can be merged into Requirements or Skills. We need to use

for section headings. Use

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

  for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like bullet points. We need to extract content: General Summary paragraph: "This position provides hands-on leadership for the ERP team responsible for delivering and supporting Granite's JD Edwards EnterpriseOne (E1) platform and the business processes it enables. The role balances people leadership, direct technical contribution, delivery execution, and stakeholder partnership to ensure ERP solutions are reliable, secure, well-governed, and aligned with enterprise and business priorities. The ERP Solutions Lead translates defined business needs and roadmaps into practical ERP outcomes across finance, procurement, project costing, and related modules, while building team capability, improving delivery and support practices, and driving measurable value. This role is open to any Granite office location." We can put that under

  About the role

  as

  . Responsibilities: Essential Job Accountabilities list. It's a long paragraph with multiple sentences separated by periods. We need to turn into list items. Each sentence seems a duty. Let's split: - Lead and develop the ERP team by setting priorities, assigning work, coaching performance, supporting hiring and onboarding, and building accountability for delivery, service, quality, and professional standards. - Provide hands-on technical leadership for the JD Edwards EnterpriseOne platform and related enterprise applications, including discovery, design, configuration, development, integration, testing, troubleshooting, implementation, and production support. - Translate defined business priorities and the ERP roadmap into actionable delivery plans that account for capacity, dependencies, risk, technical debt, tools and release cycles, and support needs. - Deliver and support ERP solutions across the lifecycle, ensuring existing and new capabilities in finance, procurement, project costing, human capital, and related modules are secure, reliable, documented, maintainable, and aligned with business and operational needs. - Coordinate business stakeholders, ERP vendors and implementation partners, and change activities by clarifying requirements, managing dependencies, communicating status and risks, and supporting effective adoption and transition to support. - Apply technical standards, governance, security, segregation of duties and financial controls, privacy, compliance, documentation, reusable patterns, and responsible-use practices to improve quality, consistency, supportability, and risk management. - Use service, delivery, adoption, quality, risk, cost, and business-outcome measures to inform execution decisions, demonstrate value, and identify opportunities for improvement, automation, modernization, consolidation, or retirement of ERP capabilities. We'll put each as

• . Requirements: Education, Work Experience, Knowledge, Skills, And Abilities, Additional Requirements/Skills, Physical Demands maybe. We need to decide sections: Could have

  Requirements

  containing sub-sections? But we only allowed headings from list; we could still have

  Requirements

  and inside we can have

  paragraphs and

  lists. We need to preserve all details. Education: "Bachelors’ Degree in Computer Science, Information Systems or Engineering required", "Project Management Institute (PMI) CAPM or PMP certification required", "Certified Scrum Master (CSM) required". Could be list. Work Experience: "Minimum 8 years’ solution architecture experience in delivering high security, high availability technical solutions", "Minimum 5 years’ experience in all aspects of delivering cloud-based solutions, leveraging industry best practices and deployment strategies", "Demonstrated experience as a Scrum Master on strategic technical projects". List. Knowledge, Skills, And Abilities: a long paragraph with many bullet-like sentences separated by periods. We need to turn into list items. Let's split that paragraph into items: - Ability to lead as a player/coach by balancing people leadership, coaching, delegation, prioritization, direct technical contribution, delivery execution, operational support, independent ownership, and collaborative team engagement. - Deep working knowledge of ERP platforms, preferably JD Edwards EnterpriseOne, including module configuration, development and reporting tools, security and user provisioning, CNC and environment management, and tools, ESU, and upgrade cycles. - Broad technical knowledge of business applications, cloud and SaaS platforms, integrations, APIs, identity and access, data flows, automation, testing, deployment, monitoring, and production support. - Practical understanding of the core business processes ERP supports, including finance and accounting, procurement, project costing, job cost and equipment, and the reporting and close activities that depend on them. - Ability to translate defined business priorities and the ERP roadmap into practical requirements, delivery plans, trade-off decisions, dependencies, and execution decisions across multiple concurrent complex initiatives. - Strong analytical, data-informed decision-making, and problem-solving skills, including the ability to evaluate alternatives, apply data analytics methods and tools, design practical solutions, troubleshoot issues, and guide implementation and support. - Working knowledge of AI-enabled solutions, intelligent automation, and emerging technologies, including appropriate oversight, responsible use, privacy, security, monitoring, and support considerations. - Knowledge of governance, standards, secure delivery, change and release management, documentation, service management, business continuity, compliance, controls, reusablePatterns, risk practices, continuous improvement, process simplification, automation, and business process re-engineering. - Strong written, verbal, facilitation, and consultative communication skills, with the ability to explain technical concepts, influence peers and cross-functional partners, lead geographically diverse or matrixed teams, manage conflict constructively, and remain effective under pressure. Additional Requirements/Skills: list: - Comply, understand, and support corporate safety initiatives to ensure a safe work environment - Ability and willingness to abide by Granite’s Code of Conduct on a daily basis - Valid driver’s license and ability to drive - Overnight travel, to various corporate locations or other sites, may be required Physical Demands: we can include as a list under Requirements maybe separate heading? Not allowed. Could put under Requirements as a subsection but we can just include as list items under Requirements. We need to ensure we don't create headings with filler like "commensurate with experience". Not present. Benefits: "Our Benefits At a Glance" paragraph: "Building tomorrow starts with you, and Granite knows that you can excel only if we support you in and out of the workplace. That is why we offer a broad benefits package that includes paid holidays, sick leave, medical, dental, vision, life insurance, disability insurance, flexible spending plans, as well as special programs for musculoskeletal health, mental wellness, and more. Salaried employees may choose from two PPO medical plans through Anthem BlueCross, including our most popular plan, for which 100% of the premium is paid by Granite for eligible employees and dependents. Employees can also opt into a Health Savings Account (HSA) or a Flexible Spending Account (FSA). As part of our investment in your future outside of the workplace, Granite provides a 100% match on the first 6% of eligible compensation that salaried employees defer into their 401(k) plans, which vests immediately. Benefits may vary for positions located outside of the continental United States." We can turn into list items maybe: but it's prose; we can keep as

  but also we could list benefits. The instruction: Use

  • for any list of duties/requirements/benefits. So we should create a list for benefits. Let's extract items: - Paid holidays - Sick leave - Medical - Dental - Vision - Life insurance - Disability insurance - Flexible spending plans - Special programs for musculoskeletal health - Mental wellness programs - Two PPO medical plans through Anthem BlueCross (most popular plan: 100% premium paid by Granite for eligible employees and dependents) - Option to opt into a Health Savings Account (HSA) or a Flexible Spending Account (FSA) - 100% match on the first 6% of eligible compensation deferred into 401(k) plans (vests immediately) - Benefits may vary for positions located outside of the continental United States (note: this is a condition, not a benefit; but we can include as note.) We'll keep as list. Pay: Base Salary Range $127,843.00 - $191,763.00. Also note "Pay may vary based upon relevant experience, skills, location, and education among other factors." We'll include as

    maybe. We should not include Schedule section. Now produce HTML fragment:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Requirements

    Maybe we split into subheadings? Not allowed. We'll just put

    for Education, Work Experience, Knowledge, Skills, And Abilities, Additional Requirements/Skills, Physical Demands as lists. Better: Use

    for each category. We'll do:

    Requirements

    Education

    but h4 not allowed? The instruction only mentions using

    for section headings. It didn't forbid other headings, but to be safe we can just use

    with bold? But we must not invent headings not in list? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but to be safe we can avoid extra headings and just use

    paragraphs. We'll do:

    Requirements

    Education:

    • Bachelors’ Degree in Computer Science, Information Systems or Engineering required
    • Project Management Institute (PMI) CAPM or PMP certification required
    • Certified Scrum Master (CSM) required

    Work Experience:

    • Minimum 8 years’ solution architecture experience in delivering high security, high availability technical solutions
    • Minimum 5 years’ experience in all aspects of delivering cloud-based solutions, leveraging industry best practices and deployment strategies
    • Demonstrated experience as a Scrum Master on strategic technical projects

    Knowledge, Skills, and Abilities:

    • Ability to lead as a player/coach by balancing people leadership, coaching, delegation, prioritization, direct technical contribution, delivery execution, operational support, independent ownership, and collaborative team engagement.
    • Deep working knowledge of ERP platforms, preferably