Jobs · Management · South Carolina

Production Supervisor

LANXESS · Charleston, SC · 3 wk ago
ManagementFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, etc. Must preserve all substantive info. We need to parse the job posting. Job Highlights: seems like bullet points of responsibilities. Then "Experience / Skills" section lists requirements. Then "Location Charleston". Then "Employee Type Regular". Then "Who We Are" (company description). Then "What We Offer" with subpoints: Compensation, Comprehensive Benefits, Work-Life & Flexibility, Training & Development, Diversity (EEO). We need to extract substantive content for sections. We need sections: About the role (maybe from Job Highlights? Or "Who We Are"? Actually "About the role" could be the Job Highlights description. We'll treat Job Highlights as About the role. Responsibilities: from Job Highlights bullet points. Requirements: maybe from Experience / Skills (minimum years, degree). Qualifications: maybe also from Experience / Skills (demonstrated ability etc). Skills: maybe also from Experience / Skills (knowledge, ability). But we need to avoid duplication. The instruction: Prefer a few substantive sections over many thin ones. So we could combine similar content. We need to decide which sections to include: About the role (summary), Responsibilities (list), Requirements (list), Qualifications (list), Skills (list), Benefits (list), maybe Pay (if mentioned), Schedule (if mentioned). Pay: "Competitive compensation packages, inclusive of a global bonus program." That's compensation info, so we can include Pay section with that sentence. Schedule: Not mentioned explicitly; there is Work-Life & Flexibility about flexible working arrangements, but not schedule specifics. So we should not create Schedule section unless posting actually states them. It does not give specific schedule, so omit. Benefits: "Comprehensive Benefits We provide a variety of benefits to support your financial security, health and wellbeing including retirement plans, health programs, life insurance and medical care." Also Work-Life & Flexibility: flexible working arrangements. Training & Development: commitment to professional development. Diversity: EEO statement (but we should remove EEO boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Diversity section includes EEO statement; we should remove that as boilerplate. However the "Diversity" paragraph also includes some motivational language about encouraging applications; that might be considered boilerplate as well. Safer to remove the Diversity section entirely. So Benefits section could include Comprehensive Benefits, Work-Life & Flexibility, Training & Development. But we need to avoid thin sections; maybe combine into Benefits section with bullet list. Pay: we have compensation statement. Now we need to ensure we don't include placeholder text like "commensurate with experience" etc. Not present. We must not invent or summarize away detail; preserve all substantive information. So we need to keep all details from the posting, but we can rephrase? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. That suggests we should not omit details, but we can reformat. However we can combine bullet points but must keep the content. It's okay to condense as long as we don't lose meaning? The instruction says do NOT summarize away detail. So we should keep each point. But we can group similar points under headings but still list them. Thus we need to output HTML with sections:

About the role

Lead the daily execution and performance of the Operations organization...

maybe combine the first bullet? Actually Job Highlights includes multiple sentences; we could put them as

with the whole paragraph. But we also need Responsibilities section with

  • for each duty. We need to avoid duplication: If we put the Job Highlights sentences in About the role paragraph, we might duplicate if we also list them in Responsibilities. Better to treat About the role as a brief overview (maybe first sentence) and Responsibilities as detailed list. However we must preserve all substantive information; we can keep the overview in About the role and then list responsibilities separately, ensuring we don't omit any detail. Let's extract the Job Highlights sentences: - Lead the daily execution and performance of the Operations organization - Establish priorities, allocate available resources, coordinate staffing, and ensure adequate operational coverage to maintain safe and reliable plant operation - Ensure consistent operating standards, work practices, training expectations, communication routines and performance expectations across the production organization - Provide direct line management for Operations, including selection, onboarding, performance management, coaching, development, succession planning, workforce planning, attendance management, recognition, corrective action, and other personnel decisions in accordance with company policies. - Coordinate daily activities with Maintenance, Engineering, Reliability, Supply Chain, Logistics, Quality, E&I, Safety, Environmental and other support functions to maximize plant reliability, production and customer service - Direct and prioritize daily production activities across multiple operating units, balancing safety, environmental, quality, reliability, customer service, production and cost requirements - Establish daily staffing and operating priorities based on production requirements, equipment availability, maintenance needs, employee qualifications, and changing business conditions - Coordinate operating decisions during startups, shutdowns, abnormal conditions, equipment failures, production interruptions and other non-routine situations - Determine when operating conditions require escalation to Engineering, Maintenance, HSSE, Quality, Supply Chain or site leadership - Ensure that production plans are translated into executable operating priorities and that deviations are identified, communicated and addressed in a timely manner - Drive operational excellence through root cause investigations, operational improvements, operator development, housekeeping, operational diligence, and continuous improvement initiatives while supporting site safety, environmental and quality objectives - Own and monitor key operational performance indicators, including production attainment, OEE, operating reliability, operating rate, quality, waste, inventory accuracy, overtime, staffing effectiveness, housekeeping, training completion and operational compliance. - Analyze performance trends and lead corrective actions to improve results - Develop and maintain the capability of the Operations organization through qualification planning, cross-training, succession planning, individual development plans, mentoring and identification of future operational leaders - Identify capability gaps and recommend staffing, training, organizational or process changes needed to maintain safe and reliable operations - Lead cross-functional resolution of operational constraints and recurring performance issues, ensuring that actions are assigned, prioritized, followed up and completed That's a lot. We'll put these as
    • under Responsibilities. Now About the role: maybe a brief summary: "Lead the daily execution and performance of the Operations organization, establishing priorities, allocating resources, coordinating staffing, and ensuring safe and reliable plant operation." But that's basically a subset; we risk losing detail. However we could keep About the role as a short paragraph that captures the essence but not duplicate all details; but the instruction says preserve ALL substantive information; does that mean we cannot omit any detail anywhere? If we put all details in Responsibilities, we have preserved them. About the role can be a brief overview that doesn't need to contain all details; it's okay to have some summary as long as we didn't remove any detail from the posting (they are still present elsewhere). So we can have About the role as a short paragraph summarizing the role (maybe first sentence). That should be acceptable. Now Requirements: from Experience / Skills: "Minimum of 15 years of progressive experience in chemical manufacturing or a related process manufacturing environment, including at least 5 years in a leadership, supervisory or production management role with responsibility for production personnel. Bachelor’s degree in Chemical Engineering, Mechanical Engineering or an equivalent combination of education, technical training and experience > 10 years of demonstrated experience in multi-unit operations organization in a safety-critical, regulated manufacturing environment (e.g., OSHA Process Safety Management)". There's a formatting issue: "> 10 years". Probably means "more than 10 years". We'll keep as written. Qualifications: maybe "Demonstrated ability to lead, coach, mentor and develop a high-performing Operations organization while promoting safety, operational discipline, accountability and continuous improvement". Also "Extensive knowledge of chemical plant operations, troubleshooting, production planning, abnormal operating conditions and operational decision-making across complex manufacturing processes". Also "Strong ability to coordinate and influence Maintenance, Engineering, Reliability, Supply Chain, Logistics, Quality, HSSE and other support functions to resolve issues and achieve business objectives". Also "Ability to independently evaluate operational data, production performance, resource requirements, cost impacts and risks; prioritize actions; and drive sustainable performance improvement". We'll put these as Qualifications. Skills: maybe overlapping; but we could treat the above as Skills. However to avoid thin sections, we could combine Qualifications and Skills into one section called Requirements? But we need to follow headings list; we can include only those with real content. We could have Requirements (experience/degree), Qualifications (abilities/knowledge), Skills (maybe same as Qualifications). To avoid duplication, we could put all experience/degree/abilities under Requirements and skip Qualifications and Skills. But the instruction says prefer a few substantive sections over many thin ones. So we could have just Requirements covering experience, degree, abilities, knowledge, etc. That would be substantive. Then we could have Benefits section. Pay section. Possibly we could also have a section "About the company" from Who We Are. But headings list does not include About the company; only About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should not add extra headings. So we need to fit company description somewhere; maybe we can put it under About the role? But About the role is for the role, not company. However we could incorporate company description into About the role paragraph as context. That would preserve that info. The instruction: "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." It doesn't forbid adding other content under existing headings. So we could include the "Who We Are" paragraph inside About the role as additional context. That would preserve it. Thus About the role could contain: a brief description of the role plus company overview. Now Benefits: we have Comprehensive Benefits, Work-Life & Flexibility, Training & Development. We'll make a

      • list. Pay: "We offer competitive compensation packages, inclusive of a global bonus program." We'll put as

        . Schedule: not present, omit. Now we need to ensure we didn't include any boilerplate like EEO etc. We removed Diversity. Now we need to output only HTML fragment, no /, no markdown fences. Let's craft. First, About the role:

        Lead the daily execution and performance of the Operations organization, establishing priorities, allocating resources, coordinating staffing, and ensuring safe and reliable plant operation. LANXESS is a leading specialty chemicals company with about 12,000 employees in 32 countries, developing, manufacturing and marketing chemical intermediates, additives and consumer protection products, and recognized for sustainability in the Dow Jones Best-in-Class Index and MSCI ESG and ISS ESG ratings.

        That captures role summary and company description. Now Responsibilities:
        • each bullet. We need to ensure we keep all bullet points exactly as in posting (maybe slight punctuation changes okay). We'll list them. Now Requirements: we need to include experience, degree, etc. Let's combine:

          Minimum of 15 years of progressive experience in chemical manufacturing or a related process manufacturing environment, including at least 5 years in a leadership, supervisory or production management role with responsibility for production personnel. Bachelor’s degree in Chemical Engineering, Mechanical Engineering or an equivalent combination of education, technical training and experience. More than 10 years of demonstrated experience in multi-unit operations organization in a safety-critical, regulated manufacturing environment (e.g., OSHA Process Safety Management).

          We changed "> 10 years" to "More than 10 years". That's preserving meaning. Now Qualifications and Skills: we could combine into one

Similar jobs

Production Supervisor

Axelon Services CorporationWichita, KS· 1 mo ago
Managementapply on www1.jobdiva.com

Production Supervisor

Schreiber FoodsRichland Center, WI· 4 mo ago
Manufacturingapply on schreiberfoods.wd115.myworkdayjobs.com

Production Supervisor

Prudential Overall SupplyColonial Heights, VA· 4 mo ago
Managementapply on workforcenow.adp.com

Production Supervisor

Ford Motor CompanyLima, OH· 3 mo ago
Management$84k–$141k/yrapply on careers.ford.com