Sourcing Manager Resin/PCR

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 that have real, specific content. The job posting has: - Company description (Greif overview) - Job title: Sourcing Manager Resin/PCR - Job Requisition #: 035801 (should fold into a short

or drop) - Job Description with Key Responsibilities broken into sub-sections: Strategic Sourcing Execution, Project Management, Negotiation & Contracting, Supplier & Contract Management - Education And Experience - Knowledge And Skills - Compensation Range (pay range) - Benefits Statement - Then boilerplate: scam warning, EEO statement, equal opportunity employer, etc. 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 (page already shows it) - 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 - Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text - 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 Now, I need to decide on sections. The posting has: - Company overview (could be "About the company" or "About the role"? The rule says "About the role" as example heading. But the company description is about the company, not the role. However, the job description starts with "The Sourcing Manager – Resin plays a key role..." That's about the role. I could have an "About the role" section with that paragraph. - Responsibilities: there are multiple sub-sections. I could combine them under a "Responsibilities" heading with sub-lists or separate headings? The rule says use

  for section headings like Responsibilities. I think I should have one "Responsibilities" heading and then list all the duties, perhaps grouped by the sub-categories. But the sub-categories are Strategic Sourcing Execution, Project Management, Negotiation & Contracting, Supplier & Contract Management. They are distinct. I could make them sub-headings? But the rule only mentions

  for section headings. It doesn't forbid sub-headings, but the example headings are top-level. I think I'll keep them as separate

  headings? However, the rule says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". That suggests those are the main sections. But the posting has multiple responsibility areas. I could make "Responsibilities" as an

  and then use

  for sub-sections? But the rule doesn't mention

  . It says use

  for section headings. I think I should use

  for each major section. The posting has: Key Responsibilities (with sub-sections), Education And Experience, Knowledge And Skills, Compensation Range, Benefits Statement. I'll map them to appropriate headings. Let's map: - "About the role" for the introductory paragraph about the role. - "Responsibilities" for the key responsibilities. I'll include all bullet points under one list, but maybe group them with sub-headings? Since the rule says use

  • for any list of duties. I could create a single list with all duties, but they are categorized. I think it's better to keep the categories as sub-headings (maybe

    ) but the rule doesn't specify. However, the rule says "use

    for section headings". It doesn't say we cannot use other heading levels. But to be safe, I'll use

    for each major section. The major sections in the posting are: Job Description (with Key Responsibilities), Education And Experience, Knowledge And Skills, Compensation Range, Benefits Statement. I'll create: -

    About the role

    with the paragraph describing the role. -

    Responsibilities

    with a list of all duties. I'll combine all bullet points from the four sub-sections into one list, but maybe keep the sub-categories as bold text within list items? Or separate lists? The rule says "use
    • for any list of duties/requirements/benefits". I can have multiple
      under the same heading. I'll do: under Responsibilities, have four sub-sections each with a

      ? But the rule says only

      for section headings. I think I'll keep it simple: one "Responsibilities" heading, then a single

      with all bullet points, but I'll include the category as part of the bullet text? That might be messy. Better to have separate
      for each category, but without extra headings. I'll just put them as separate lists under the same heading, maybe with a

      indicating the category? But the rule says use

      • for lists. I'll do:

        Responsibilities

        Strategic Sourcing Execution

        • ...

        Project Management

        • ...
        etc. But that uses

        for category labels. That's acceptable. - "Requirements" for Education And Experience (since it's education and experience requirements). The rule mentions "Requirements" as an example heading. I'll use "Requirements". - "Skills" for Knowledge And Skills (since it's skills). The rule mentions "Skills" as an example heading. - "Pay" for Compensation Range (since it's pay range). The rule mentions "Pay" as an example heading. - "Benefits" for Benefits Statement. I should not include the scam warning, EEO statement, equal opportunity employer boilerplate. Also, the Job Requisition #: 035801 should be folded into a short

        or dropped. I'll include it as a

        maybe at the top or bottom? The rule says "fold minor metadata into a short

        or drop it." I'll include it as a

        at the beginning or end. Probably at the beginning after the company description? But the company description is about the company. I'll include a

        with "Job Requisition #: 035801" maybe under "About the role" or separate. I'll put it as a

        before the sections. Now, let's write the HTML fragment. Structure:

        Job Requisition #: 035801

        About the role

        The Sourcing Manager – Resin plays a key role in executing sourcing strategies, leading supplier evaluations, and supporting cost optimization initiatives across the raw material category. This role is responsible for managing sourcing events, negotiating competitive commercial terms, and partnering with cross-functional teams to meet business needs. The Manager contributes to category strategy development while focusing on operational execution, supplier performance, and continuous improvement.

        Responsibilities

        Strategic Sourcing Execution

        • Support the development and execution of category strategies to achieve cost savings and mitigate supply risk.
        • Manage the sourcing lifecycle and development, supplier evaluations, negotiation, and contract preparation.
        • Conduct market research and benchmarking to inform sourcing recommendations.

        Project Management

        • Lead sourcing and procurement-related projects from initiation through completion, ensuring clear scope definition, timeline management, and delivery of key milestones.
        • Coordinate cross-functional project teams and maintain strong communication to keep stakeholders informed of progress, risks, and issues (Operations, Engineering, IT, Finance, etc.).
        • Develop and maintain project documentation, including charters, action logs, and status reports.
        • Identify risks and mitigation plans to ensure project objectives are met on time and within scope.
        • Drive accountability across internal teams and suppliers to ensure successful project execution and adoption of sourcing outcomes.

        Negotiation & Contracting

        • Lead negotiations for global and high impact sourcing events.
        • Develop negotiation plans to achieve competitive commercial terms.

        Supplier & Contract Management

        • Manage supplier relationships, track, and report performance KPI’s.
        • Support quarterly supplier business reviews and corrective action follow-up.
        • Performs other duties as assigned.

        Requirements

        • Bachelor’s degree in Supply Chain, Project Mgmt., Business, or related field.
        • 4–7 years of experience in sourcing or procurement (Capex, MRO, Opex).
        • Strong negotiation and analytical skills.
        • Working knowledge of sourcing processes, cost analysis, and contract management.
        • Experience with procurement systems (SAP, Ariba, Coupa, etc.).
        • Fluent in English.

        Skills

        • In-depth knowledge of and experience with sourcing, category management, and/or supply chain operations.
        • Excellent written and oral communication skills, with proven negotiation skills.
        • Excellent interpersonal and customer service skills.
        • Excellent organizational and time-management skills along with strong attention to detail.
        • Strong analytical and problem-solving skills.
        • Demonstrates the ability to prioritize tasks and delegate them when appropriate.
        • Ability to manage multiple sourcing projects.
        • Continuous improvement mindset.
        • Thorough understanding of plant manufacturing operations and sourcing processes as well as the materials and supplies used in the organization.

        Pay

        The pay range for this position is $108,400.00 - $184,600.00 annually. Typically, a competitive wage for new hires will fall between $108,400.00 to $140,000.00 annually. Offers for this position may vary based on market data and other factors such as job-related knowledge, skills, experience, and geographic location. The position may also be eligible for a short-term incentive.

        Benefits

        Greif offers a comprehensive benefits package, including competitive core benefits, paid time off, and a range of local benefits for eligible colleagues.

        That's it. No boilerplate. Ensure no markdown code fences. Output only the HTML fragment. Check for any missing substantive info: The company description at the top (Greif is a global leader...) is not included. Should I include it? The rule says "Preserve ALL substantive information". The company description is substantive about the company. But the rule also says "Do NOT repeat the job title as a heading (the page already shows it)". The company description is not the job title. It's about the company. Should I include an "About the company" section? The example headings include "About the role". Not "About the company". But the posting starts with company description. I think it