Jobs · Marketing · Texas

Senior Global Category Manager

Weir Minerals · Fort Worth, TX · 3 wk ago
HybridMarketingFull-time
We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: "What We Do" (maybe About the role?), "Make your impact", "What You'll Do" (Responsibilities), "What You'll Bring" (Requirements/Qualifications/Skills), "Why join Weir?" (maybe Benefits? Actually benefits listed later). There's a "Benefits" section with bullet points. There's no explicit Pay or Schedule info (Hybrid minimum three days in office per week is schedule info). So we can include Schedule section with that detail. Pay: not specified (competitive pay and Bonus Structure mentioned under Benefits? Actually "Competitive pay and Bonus Structure" is under Benefits list. So pay is mentioned as competitive pay but not specific numbers. According to rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive pay and Bonus Structure" as a benefit, but that's still a statement about pay. Should we include Pay section? The rule says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state competitive pay, but not specific numbers. However "competitive pay" is a statement about pay. I'd argue we can include a Pay section with that statement. But they said prefer few substantive sections over many thin ones. Could incorporate pay into Benefits section. Since Benefits already includes "Competitive pay and Bonus Structure". So we can keep Benefits section and not separate Pay. Schedule: we have Hybrid (minimum three days in office per week). That's schedule info. So we can include Schedule section. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We'll include only those with content. We have About the role: maybe "What We Do At Weir" and "Make your impact". Could combine as About the role. Responsibilities: "What You'll Do" with bullet points. Requirements/Qualifications/Skills: "What You'll Bring" includes Must-haves and Nice-to-haves. Could split into Requirements (must-haves) and Qualifications/Skills (nice-to-haves). But we can combine into Requirements section with both must and nice? The rule: prefer few substantive sections over many thin ones. So maybe one Requirements section covering both must-haves and nice-to-haves. Benefits: list. Schedule: hybrid info. We must not repeat job title as heading. No Job ID etc. We must remove boilerplate: EEO, equal opportunity, etc. Also remove navigation, cookie, legal, scam-warning, duplicated lines, application instructions. At end there is "#minerals" maybe ignore. We need to preserve all substantive information. Let's extract content. About the role: Combine "What We Do At Weir" paragraph and "Make your impact" paragraph. What We Do At Weir: "Weir Minerals Fort Worth, TX Hybrid (minimum three days in office per week) What We Do At Weir We are a global leader in mining technology for a sustainable future. We help our customers extract the resources the world needs more efficiently and more sustainably. Our planet’s future depends on the transition to renewable energy, and that transition can only happen with the metals and minerals our customers deliver. So, we work side by side with mines across the globe to move less rock, use less energy, use water wisely, and create less waste. Together, we drive the shift to smart, efficient, and more sustainable mining." Make your impact: "Make your impact You’ll play a key role in solving real-world challenges. You’ll apply your skills to deliver results that matter whether that’s through engineering, planning or customer support. You’ll work with purpose, learn every day and help shape a more sustainable future." Combine into About the role paragraph(s). Could be two

elements. Responsibilities: "What You’ll Do" with bullet points. We need to extract bullet points: - Category Strategy & Value Delivery: Develop and execute global category strategies aligned with business and engineering requirements. Translate market insights into practical sourcing plans and supplier decisions. Identify and deliver cost, value, and performance improvements including should-cost analysis. Success means measurable cost reductions, risk mitigation, and supplier value enhancement. - Global Sourcing: Lead global and regional sourcing initiatives across multiple sites and countries. Manage RFx processes, negotiations, and supplier selection end-to-end. Optimize supplier footprint balancing cost, quality, lead time, and risk. Daily activities include supplier negotiations and cross-functional collaboration. Travel up to 30% globally, primarily to Europe, North America, and South America. - Supplier Management: Own relationships with key global suppliers, monitor performance on cost, delivery, quality, and service. Drive supplier improvement, capability development, and qualification of new sources. Conduct regular supplier reviews and resolve escalations from internal stakeholders. - Risk & Continuous Improvement: Identify and mitigate supply risks including single source, geopolitical, and capacity risks. Support continuous improvement and adoption of procurement tools and data analytics to enhance decision-making. Contribute to global procurement standards and leadership communications. - Safety First: Demonstrate 100% commitment to our zero harm behaviors in support of our drive towards developing a world-class safety culture. These are bullet points. Requirements: "What You’ll Bring" Must-haves and Nice-to-haves. Must-haves: - Degree in Mechanical Engineering, Electrical/Electronics Engineering, or equivalent technical background with deep experience in engineered components. - Proven track record of independently developing and delivering category strategies with measurable outcomes in cost, risk, and performance improvements. - Hands-on experience leading sourcing initiatives across multiple regions and managing international supplier bases. - Strong negotiation, supplier management skills, and fluency in English. Nice-to-haves: - Experience in mining equipment, heavy-industrial manufacturing, or engineered product environments. - Familiarity with digital and AI procurement tools. - Ability to influence business and large international suppliers within matrixed organizations. - Multilingual capabilities beyond English. We can combine into a single Requirements section with two sub-lists? But we must use

  • for any list of duties/requirements/benefits. Could have two separate
      under same heading, or combine into one list with all items. Probably better to separate Must-haves and Nice-to-haves as separate
        with headings? But we cannot add extra headings besides the allowed ones? The instruction only says use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings inside? It says use

        for section headings (list). Likely they expect only those headings as sections. Inside we can have

        and

        • . Could we add a or inside? Probably okay but safer to just have one list with all items, maybe label them with text inside
        • . Could do:
        • Must-haves: ...
        • but that mixes. Better to have two lists: one for Must-haves, one for Nice-to-haves, each preceded by a

          describing? But that adds extra

          which is fine. We'll do:

          Requirements

          Must-haves:

          • ...
          • ...

          Nice-to-haves:

          • ...
          • ...
          That seems okay. Benefits: list from "Benefits" section: - Competitive pay and Bonus Structure - Career development and learning support - Access to global inclusion networks - Regional and team-specific benefits - Sharebuilder scheme - Wellness support for you and your family - Collaboration with global teams - Study support Also there is a paragraph after benefits about company history etc. That might be considered About the role? Actually it's after benefits: "Founded in 1871, Weir is a world leading engineering business..." That's more about company, could be part of About the role? But we already have About the role covering what we do and make your impact. Could add another paragraph under About the role about company history. It's substantive. So we can add that to About the role. Schedule: "Hybrid (minimum three days in office per week)" from the header line. Also maybe mention travel up to 30% globally (that's part of responsibilities). But schedule is about office presence. We'll put schedule section with that line. Pay: Not separate; we have competitive pay mentioned in benefits. Now ensure we don't include boilerplate: Remove EEO statement, equal opportunity, etc. Also remove "Thanks to Weir’s technology..." paragraph? That's after benefits, maybe part of About the role? It's substantive about purpose. Could add to About the role as well. But we must be careful not to include duplicated lines. The paragraph: "Thanks to Weir’s technology, our customers can produce essential metals and minerals using less energy, water and waste at lower cost. With the increasing need for metals and minerals for climate change solutions, Weir colleagues are playing their part in powering a low carbon future. We are a global family of 11,000 uniquely talented people in over 60 counties, inspiring each other to do the best work of our lives." That's substantive; we can add to About the role. Also "For additional information about what it is like to work at Weir, please visit our Career Page and LinkedIn Life Page." That's application instruction? It's a referral to career page; maybe considered application instructions? It's not exactly how to apply but still maybe considered navigation. Safer to remove. Also "Weir is committed to an inclusive and diverse workplace. We are an equal opportunity employer..." Remove. Also "#minerals" remove. Now construct HTML. We'll have:

          About the role

          Weir Minerals Fort Worth, TX Hybrid (minimum three days in office per week) We are a global leader in mining technology for a sustainable future. We help our customers extract the resources the world needs more efficiently and more sustainably. Our planet’s future depends on the transition to renewable energy, and that transition can only happen with the metals and minerals our customers deliver. So, we work side by side with mines across the globe to move less rock, use less energy, use water wisely, and create less waste. Together, we drive the shift to smart, efficient, and more sustainable mining.

          You’ll play a key role in solving real-world challenges. You’ll apply your skills to deliver results that matter whether that’s through engineering, planning or customer support. You’ll work with purpose, learn every day and help shape a more sustainable future.

          Thanks to Weir’s technology, our customers can produce essential metals and minerals using less energy, water and waste at lower cost. With the increasing need for metals and minerals for climate change solutions, Weir colleagues are playing their part in powering a low carbon future. We are a global family of 11,000 uniquely talented people in over 60 counties, inspiring each other to do the best work of our lives.

          But note we duplicated the hybrid line; we might want to keep schedule separate. The About the role shouldn't include the hybrid line? The hybrid line is location and schedule. Might be better to keep location in About the role? It's okay. But we also have schedule section separate. Might duplicate. Could keep location in About the role and schedule separate just stating hybrid expectation. We'll keep About the role without the hybrid line, and schedule section will have that. Thus About the role paragraphs: first paragraph about what we do, second about make your impact, third about thanks to Weir's technology etc. Now Responsibilities:

          Responsibilities

          with
          • each bullet. Requirements:

            Requirements

            with must-haves and nice-to-haves. Benefits:

            Benefits

            with <

Similar jobs