Global Operational Excellence Leader

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. First, I need to identify the sections: - Company Overview (but this is more of an intro, not a section heading per rules) - Description (this is "About the role" essentially) - Job Details (location info) - Key Responsibilities (multiple bullet points) - Required Qualifications & Experience (with sub-sections: Education, Professional Qualifications, Relevant Industry Experience, Functional Expertise, Strong Analytical..., Strong facilitation..., Performance-Oriented..., Excellent Communication..., Willingness to travel) - Benefits mentioned at the end: "Aurorium offers competitive total compensation packages, including benefits such as medical, dental, vision, life, 401(k), disability insurance, flexible spending accounts, health savings accounts, paid time off, and paid holidays." - EEO statement (boilerplate, should be removed) - Status Active (metadata, drop) Rules: - Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. - Use

• for lists,

  for prose. - Do NOT repeat job title as heading. - Do NOT put Job ID/requisition numbers as headings. - Preserve ALL substantive information. - Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. - Include section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). - Never create Pay/Schedule/Benefits sections unless posting actually states them. - Prefer few substantive sections over many thin ones. - Output ONLY HTML fragment — no /, no markdown code fences. Now, let's map content to sections: 1. About the role: The "Description" paragraph describes the role. That's substantive. Use

  About the role

  with

  for the description. 2. Responsibilities: The "Key Responsibilities" list has multiple bullet points. Each bullet is a responsibility. Use

  Responsibilities

  with
  • for each. 3. Requirements/Qualifications: The "Required Qualifications & Experience" includes Education, Professional Qualifications, Relevant Industry Experience, Functional Expertise, and several skill/attribute bullets. This is a mix of requirements and qualifications. Could combine into a "Requirements" section or split into "Qualifications" and "Skills". The rules mention headings: Requirements, Qualifications, Skills. I think "Requirements" is appropriate for the hard requirements (education, certification, experience). The softer skills (analytical, facilitation, performance-oriented, communication, travel) could be "Skills" or part of "Requirements". Since the posting groups them under "Required Qualifications & Experience", I'll create a "Requirements" section with sub-lists. But the rules say use
    • for any list of duties/requirements/benefits. I can have a single
      with multiple
      • items, each being a requirement. However, there are categories: Education, Professional Qualifications, etc. I could make each category a separate
      • with nested list? But the rule says use
        • for any list. Simpler: make each bullet a separate
        • under a single
          . But the categories are headings within the qualifications. The posting uses bolded categories. I could preserve that by making each category a
          • with a strong tag and then nested list? But the rule says use
            • for any list of duties/requirements/benefits. It doesn't forbid nested lists. However, to keep it simple and semantic, I'll create a "Requirements" section with a
              where each
              • is a requirement statement, incorporating the category. For example: "Education: Bachelor’s degree in chemical engineering required". That preserves the structure. Alternatively, I could have subheadings using

                but the rules only mention

                for section headings. Not sure if

                allowed. The instruction: "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

                for section headings. I'll stick to

                for main sections only. Thus, I'll have: - About the role - Responsibilities - Requirements (including all qualifications) - Benefits (since they list specific benefits) Location is in "Job Details". That could be part of "About the role" or a separate "Schedule" or "Location" section. The rules mention "Schedule" as a possible heading. But location is not schedule. There's no schedule info (shift, hours). There's travel up to 30%. That could be in Requirements. The location options: "Role can be based at one of our locations, Zeeland, MI; Greensboro, NC; Denham Springs, LA; or Pasadena, TX". That's substantive location info. Could be a "Location" section, but not in the example headings. The example headings include "Schedule". I could include a "Location" heading? The rules say "use

                for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." suggests those are examples, not exhaustive. But they say "include a section ONLY when the posting has real, specific content for it". Location is specific. However, the example headings don't include Location. I could fold location into a short

                in About the role or a separate "Details" section. But the rules say "fold minor metadata into a short

                or drop it." Location is not minor metadata; it's important. I think I'll include a "Location" section with

                Location

                and a

                listing the locations. But the example headings don't include Location. The user might expect only those headings. However, the instruction says "e.g." meaning for example. I think it's okay to add a Location heading if it's substantive. But to be safe, I'll include location in the About the role section as a paragraph. Similarly, travel requirement is in qualifications. I'll keep it there. Benefits: The posting lists specific benefits: medical, dental, vision, life, 401(k), disability insurance, flexible spending accounts, health savings accounts, paid time off, and paid holidays. That's substantive. So I'll create a Benefits section with

                • for each benefit. Pay: Not mentioned specifically (no salary range). So no Pay section. Schedule: Not mentioned (no shift hours). So no Schedule section. EEO statement: boilerplate, remove. Application instructions: "If you have the energy... Apply today!" Remove. Status Active: drop. Now, let's craft the HTML. Structure:

                  About the role

                  Description paragraph...

                  Location: Role can be based at one of our locations, Zeeland, MI; Greensboro, NC; Denham Springs, LA; or Pasadena, TX.

                  Responsibilities

                  • Lead and facilitate cross-functional structured problem solving, root cause analysis, Kaizen events, and Lean improvement initiatives to eliminate waste, address constraints, improve performance, and implement sustainable solutions aligned to SQDCP (Safety, Quality, Delivery, Cost, People) targets.
                  • Build organizational capability in Lean and Continuous Improvement through training, coaching, facilitation, and hands-on support. Own Lean/Six Sigma certification programs and ensure quality project execution.
                  • Lead selected strategic improvement initiatives from planning through implementation, establishing objectives, milestones, ownership, success measures, and cross-functional engagement to deliver measurable business results.
                  • Partner with Operations, Engineering, Quality, Supply Chain, Finance, HR, IT, Commercial, and other functions to improve end-to-end processes, simplify ways of working, and successfully implement and sustain operational and organizational changes.
                  • Oversee key performance indicators (KPIs), analytic tools, data governance, and performance dashboards to track progress and guide decisions.
                  • Complies with company Health, Safety and Environmental policies, procedures, and arrangements. Reports all Health, Safety and Environmental accidents, incidents and near misses promptly. Acts in a safe and responsible manner at all times.
                  • Active participation in continuous improvement activities. Participates in problem-solving. Takes responsibility and ownership for own learning and development in the spirit of continuous improvement of both self and the business. Assists in the training, mentoring, and assessment of other team members. Exercises autonomy and judgement subject to overall direction or guidance.

                  Requirements

                  • Education: Bachelor’s degree in chemical engineering required.
                  • Professional Qualifications: Lean Six Sigma Black Belt or Master Black Belt certification required.
                  • Relevant Industry Experience: 10+ years of proven leadership experience in operational excellence, process improvement, or related roles, with experience in a global leadership capacity. Strong understanding of the chemical industry or process manufacturing strongly preferred.
                  • Functional Expertise: Proven track record of leading operational excellence deployments and delivering measurable productivity improvements and cost savings.
                  • Strong Analytical, Problem-Solving, and Change Management Skills: Takes a data-driven approach to decision-making, with strong analytical, problem-solving and change management skills.
                  • Strong facilitation, coaching, and training capabilities: Demonstrated ability to train and coach on lean six sigma tools and methodologies.
                  • Performance-Oriented and Action-Biased: Demonstrates urgency and a bias for rapid change, driving business performance based on KPIs aligned with company strategy.
                  • Excellent Communication & Stakeholder Management: Manages diverse stakeholders across diverse cultures and geographies, communicates clearly and persuasively, and builds strong relationships.
                  • Willingness to travel: Up to 30%.

                  Benefits

                  • Medical
                  • Dental
                  • Vision
                  • Life insurance
                  • 401(k)
                  • Disability insurance
                  • Flexible spending accounts
                  • Health savings accounts
                  • Paid time off
                  • Paid holidays
                  Note: The benefits list in the posting is a comma-separated list. I'll split into individual items. Also, the company overview at the top: "Company Overview Aurorium is the materials innovation partner..." That's about the company, not the role. The rules say "Do NOT repeat the job title as a heading (the page already shows it)". The company overview is not the job title. Should I include it? The rules say "Preserve ALL substantive information". The company overview is substantive about the company. But the instruction is to reformat a job posting into clean HTML. Typically, job postings include company overview. However, the example headings don't include "Company Overview". The rules say "use

                  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't include Company Overview. But the posting has a "Company Overview" section. I think I should include it as a section, maybe "About the company" or "Company overview". But the rules say "include a section ONLY when the posting has real, specific content for it". It does have content. However, the user might expect