Sourcing Expeditor

We need to output HTML fragment with sections: About the role? Actually the posting includes "About PROENERGY" (company description) and "Our Footprint", "Our Philosophy". The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include. The posting includes: - About PROENERGY (company description) - Our Footprint (locations) - Our Philosophy (benefits, pay? Actually says "We offer competitive pay, excellent benefits that include Medical, Dental, Vision, and Life/Disability Insurance at minimal cost to the employee, 10 paid holidays, paid time off, and a 401K plan.") - Position Summary (description) - Position Responsibilities (list of duties) - Required Qualifications (list) - Desired Qualifications (list) - Key Competencies (list) - Performance Metrics (list) - Travel requirement (mentioned in Required Qualifications) - Work authorization etc (maybe minor metadata) - EEO statement (should be removed as boilerplate) We need to map to allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use "About the role" for Position Summary? Or maybe "About PROENERGY" is company description, not role. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. We have: - About the role: could include Position Summary and maybe company description? Probably Position Summary is about the role. Could also include brief about PROENERGY? But "About the role" likely refers to role description. We'll put Position Summary there. - Responsibilities: list of duties (Position Responsibilities). Use

  • . - Requirements: maybe Required Qualifications? Or combine Required and Desired? The instruction says we can have Requirements and Qualifications separate. Use Requirements for mandatory qualifications (Required Qualifications). Use Qualifications for desired? Or Skills for competencies? Let's think. We have Required Qualifications (mandatory). Desired Qualifications (preferred). Key Competencies (skills). Performance Metrics (maybe not needed). Benefits: we have benefits described in Our Philosophy (competitive pay, excellent benefits...). Pay: we have "competitive pay" but not specific numbers. Should we include Pay section? The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "competitive pay" and benefits details. So we can include Benefits section with those details. Pay section maybe we can include "competitive pay" but that's vague; but it's stated. However they said avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "competitive pay" is not filler but still vague. Might be okay to include Pay section with that phrase. But they said prefer a few substantive sections over many thin ones. Could combine Pay and Benefits into one Benefits section? But they have separate headings allowed. We could include Benefits section with the benefits details, and maybe not include Pay section because it's just "competitive pay" without specifics; could be considered filler? Might be better to omit Pay section. Schedule: not specified (travel 80%+ domestic and international travel). That's travel schedule, not work schedule. Could we put Schedule section for travel? The posting mentions travel requirement. Could be considered schedule? But they said only create Schedule section if posting actually states them. It does state travel: 80%+ domestic and international travel. That's about schedule. Could include Schedule section with that detail. We also have Work Location (multiple sites) and Remote Connecticut option. That's location info, not a heading we have. Could fold into About the role or Responsibilities? Probably not needed; we can include as a short

    under About the role or maybe as a separate section? Not in allowed headings. Could fold into About the role as minor metadata. We must remove boilerplate: EEO statement, etc. We need to preserve all substantive information. So we need to include company description? The instruction says do not repeat job title as heading, but we can include company description as prose maybe under About the role? But About the role is for role description, not company. However we could include a brief About PROENERGY as a preamble before sections? The instruction says output only HTML fragment, no restrictions on extra prose outside headings? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

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

      for prose. It doesn't forbid other prose outside headings, but likely they expect sections only. However we need to preserve all substantive information, including company description, footprint, philosophy. Where to put them? Could be under About the role? But that might misrepresent. Perhaps we can create a section "About the company" but not allowed heading. Could we treat "About PROENERGY" as part of About the role? Might be okay to include as a

      before the first heading. The instruction didn't forbid extra prose; just said use those headings for sections. So we can have a leading

      with company overview, then sections. Thus structure:

      About PROENERGY ... (company description, footprint, philosophy)

      Then

      About the role

      with Position Summary

      . Then

      Responsibilities

      with
      • list of duties. Then

        Requirements

        with Required Qualifications
        • . Then

          Qualifications

          with Desired Qualifications
          • . Then

            Skills

            with Key Competencies
            • . Then

              Benefits

              with benefits description

              (Medical, Dental, Vision, Life/Disability Insurance, 10 paid holidays, paid time off, 401K). Then

              Schedule

              with travel requirement

              (Travel: 80%+ domestic and international travel. This role requires frequent on-site engagement...). We could also include Work Location as a

              under About the role or maybe as its own paragraph before sections. But we can include it in About the role paragraph. We must not include Pay section because we already have competitive pay mentioned in Benefits? Actually benefits section includes "competitive pay" as part of philosophy. Could include that in Benefits

              . So we don't need separate Pay. We must not include Performance Metrics (list) because no heading for it; but we could fold into Skills or Qualifications? It's substantive; maybe we can add a section "Performance Metrics" but not allowed heading. Could we treat it as Skills? Not ideal. But instruction says prefer a few substantive sections over many thin ones; we could omit Performance Metrics if not fitting headings. However we must preserve ALL substantive information. So we need to include it somewhere. Could we add a

              Skills

              and include both Key Competencies and Performance Metrics as lists? That would be merging two lists under Skills heading. That's acceptable: Skills heading can contain both competency and performance metrics lists. Or we could add a separate

              Performance Metrics

              but not in allowed list; but maybe we can still use it? The instruction says 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? It says "use

              for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings; but maybe we can also use other headings if needed? The instruction: "Use

              for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It seems they expect those headings. It also says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we could create a section with a heading not in the list if we have content, but they gave examples. Safer to stick to those headings. Thus we need to fit Performance Metrics somewhere. Could be under Skills as a sub-list? Or under Qualifications? Probably under Skills as it's about performance expectations. We'll include both Key Competencies and Performance Metrics as separate

              under Skills heading. Now we need to ensure we don't include boilerplate: EEO statement, duplicated lines, application instructions. Also remove "It is PROENERGY’s policy to provide equal opportunity..." etc. Also remove "Position Summary" heading? We'll convert to prose under About the role. Now let's extract content. Company description: "About PROENERGY PROENERGY is an engineering, R&D, and manufacturing powerhouse. The company addresses every need for fast-start power generation: turbine and package manufacturing, turnkey project execution, power purchase agreements, and asset lifecycle care for turbines and plants. Where others see impossible energy challenges, PROENERGY provides innovative aeroderivative solutions. Our Footprint PROENERGY delivers fast-start, dispatchable power solutions from worldwide centers for aeroderivative excellence. We are investing more than $1 billion through 2028 in infrastructure to serve our customers. In Sedalia, Missouri, our 600,000 sq ft Center for Excellence in Manufacturing—a world-class investment in fast-start power and the only campus of its kind in the world—is growing by 40 percent. In Houston, Texas, our 500,000 sq ft Center for Excellence in Lifecycle Care features a Level-IV depot and aero repair facility, which executes comprehensive services for aeroderivative engines under one roof. In Kansas City, we have an office with an Engineering team that supports our sought-after solutions for turnkey projects and contracted power. And our worldwide service centers ensure local service expertise near our customers. Our expanding service footprint includes Phoenix, Buenos Aires, New Brunswick, and additional locations in Europe, Australia, and Southeast Asia. Our Philosophy We take care of our people and strive to make a positive difference for the world. We offer competitive pay, excellent benefits that include Medical, Dental, Vision, and Life/Disability Insurance at minimal cost to the employee, 10 paid holidays, paid time off, and a 401K plan. If you are looking for a rewarding career and possess specialized knowledge and quality-oriented problem-solving skills, we encourage you to apply today." We need to preserve all that. We'll put in a

              maybe multiple paragraphs. Now Position Summary: "Position Summary The Sourcing Expeditor is responsible for driving supplier execution and ensuring the timely delivery of