Continuous Improvement Director

We need to output HTML fragment with sections: headings using

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate like EEO, legal, application instructions, etc. Must not invent or summarize away detail. Must not include sections with filler like "commensurate with experience". Must only include sections when posting has real specific content. Let's parse the posting. Job Title: Continuous Improvement Director (we don't output heading for title) Location: Tyler, TX Department: Finance Reports to: CFO Direct Reports: Continuous Improvement Team (corporate and plant CI roles) Normal Work Schedule: Exempt. Based in Tyler with standard business hours, and flexibility to support plant operations across shifts, including early, late and weekend coverage as business needs require. Travel: Regular travel to Valley, AL, and Gainesville, GA is required based on business needs. Overview Of Company: description. Job Summary: description. Qualifications: Minimum Qualifications (Required) and Preferred Qualifications. Key Responsibilities: list. Work Environment: description. Physical Demands: description. Benefits: list of benefits (Incentive Pay, Vacation/Sick days, Medical/Dental/Vision Benefits, Telemedicine, Onsite Clinic, Free annual health screening, 401(k) with company match, STD and LTD, Life insurance & other voluntary benefits, Career Development). Pay: Not explicitly stated; only "Incentive Pay: This position is eligible for the Company’s bonus plan, with amounts varying based on program terms." That's not a specific pay figure. According to rules: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Pay, we need actual pay numbers or salary range. Not present, so we should NOT include a Pay section. For Schedule, we have Normal Work Schedule description: "Exempt. Based in Tyler with standard business hours, and flexibility to support plant operations across shifts, including early, late and weekend coverage as business needs require." That's specific content about schedule. So we can include a Schedule section. For Benefits, we have list, so include Benefits section. We also need About the role? Could be Job Summary or Overview. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map content to these headings. We need to decide which sections to include based on content. We have: - About the role: could be Job Summary + Overview Of Company? But Overview Of Company is about company, not role. Might be better to have "About the role" using Job Summary. We'll include that. - Responsibilities: Key Responsibilities. - Requirements: Could be Qualifications (minimum and preferred). Could also include Driving Requirements? But we can put under Requirements. - Qualifications: Already have Qualifications section; but we might combine Requirements and Qualifications? The instruction list includes both Requirements and Qualifications as possible headings. We need to decide. Since we have both minimum and preferred qualifications, we could put them under Qualifications. Requirements could be things like "Driving Requirements" etc. But we also have Direct Reports, Reports to, Location, Department etc. Those could be considered metadata; we could fold into a short

or drop. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a short paragraph for location, department, reports to, direct reports, travel, etc. Maybe under a heading like "About the role" we can include that. But we must not create sections with filler. So we need to ensure each heading has substantive content. Let's plan sections: -

About the role

: include Job Summary and maybe Overview Of Company? Actually Overview Of Company is about company, not role. Could be separate section "About the company". But not in allowed headings list. However we could still include it under About the role? Might be okay but could be considered not specific to role. However we need to preserve ALL substantive information; we cannot omit company overview. So we need to include it somewhere. Since allowed headings list is just examples, not exhaustive? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we can use other headings if needed? But they say use

for section headings (e.g. ...). Likely they expect us to use those headings where appropriate. But we can also use other headings if needed, but better to stick to those. We could put company overview under About the role as part of context. That seems acceptable. -

Responsibilities

: list of responsibilities. -

Requirements

: maybe include Driving Requirements, location, department, reports to, direct reports, travel, normal work schedule? But schedule is separate section. We could include location, department, reports to, direct reports, travel under Requirements? Or we could have a short paragraph for metadata under About the role. Let's think. Better: Use About the role for role summary (Job Summary). Use Responsibilities for duties. Use Qualifications for qualifications (minimum and preferred). Use Benefits for benefits. Use Schedule for schedule. Possibly also include a section for Work Environment? Not in list but we could add if needed. However instruction says prefer a few substantive sections over many thin ones. So we might combine Work Environment and Physical Demands into a section like "Working Conditions". But not in examples. Could we omit them? We must preserve ALL substantive information. So we need to include work environment and physical demands somewhere. Could we put them under Responsibilities? No. Could we put them under Requirements? Not really. Could we create a section "Work Environment" using

even if not in examples? The instruction says use

for section headings (e.g. ...). It doesn't forbid other headings, but says use

for section headings (e.g. ...). Likely they expect we use those headings where applicable, but we can also add others if needed. However they also say "Prefer a few substantive sections over many thin ones." So maybe we can incorporate work environment and physical demands into a single section like "Working Conditions". That would be substantive. But we need to ensure we don't miss any substantive info: Overview Of Company, Job Summary, Responsibilities, Qualifications (minimum & preferred), Driving Requirements, Work Environment, Physical Demands, Benefits, Schedule, Travel, Direct Reports, Reports to, Department, Location, Normal Work Schedule (already schedule). Also Incentive Pay mentioned under Benefits. We need to avoid boilerplate: EEO, legal, application instructions, unsolicited assistance, etc. Now, let's craft HTML. We'll start with a

for metadata? Actually we can include location, department, reports to, direct reports, travel in a short paragraph under About the role or maybe as a separate

before sections. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include a short paragraph for location, department, reports to, direct reports, travel. Let's do that. Then sections:

About the role

: includes Job Summary and Overview Of Company (maybe combined). We'll put two paragraphs: one for Job Summary, one for Overview Of Company.

Responsibilities

:

• each responsibility. We need to extract responsibilities from "Key Responsibilities" section. It has subheadings: CI Operating Model & Loss Management, Standards, Governance & Sustained Results, Financial Validation & Benefits Realization, Digital Productivity & Analytics, Leadership & Cross-Functional Partnership. Under each there are bullet-like sentences. We'll turn each sentence into
• . We'll need to preserve all detail. Let's list them: CI Operating Model & Loss Management: - Build and lead a consistent enterprise CI operating model across the Tyler, Valley, and Gainesville plants, with a roadmap to extend the model into Supply Chain and other functions. - Identify, quantify, and prioritize losses and improvement opportunities using a common, data-driven methodology. - Own the enterprise productivity pipeline, including opportunity sizing, prioritization, initiative tracking, and escalation of barriers. - Develop improvement glidepaths and targets jointly with Operations; Operations retains accountability for plant operating results. Standards, Governance & Sustained Results: - Establish consistent KPIs, review routines, governance, and accountability mechanisms across all plants. - Develop and maintain standard work, verification routines, and follow-through processes that sustain improvements. - Monitor progress against committed improvement glidepaths, identify gaps, and coordinate recovery plans with Operations. - Partner with FSQA on document control and with HR on training, qualification, and certification processes related to CI standards. Financial Validation & Benefits Realization: - Partner with Finance to quantify improvement benefits, validate savings independently, and ensure realized benefits reconcile to the P&L. - Maintain transparent documentation of assumptions, baselines, calculations, and benefit realization for CI initiatives. Digital Productivity & Analytics: - Support effective use and adoption of RedZone and other digital productivity tools; measure adoption, utilization, and business value. - Use operational data and dashboards to surface losses, monitor performance, and support fact-based prioritization and decisions. - Identify opportunities to scale digital tools and replace manual processes where doing so improves visibility, consistency, or productivity. Leadership & Cross-Functional Partnership: - Build, coach, and develop the corporate and plant CI team. - Coach plant teams and leaders in structured problem-solving, CI methods, and adherence to standard work. - Partner with Operations, Engineering, Supply Chain, FSQA, HR, and Finance to implement and sustain the improvement system. - Communicate performance, risks, and progress to senior leadership and influence execution across sites and functions. Measurement of Success: This seems like outcomes, not responsibilities. Could be omitted? It's part of job description but maybe considered responsibilities? It's more like success metrics. Could be included under Responsibilities or maybe separate section? But we can incorporate as responsibilities? It's about measuring success; maybe we can include as part of Responsibilities as well. However the instruction says preserve ALL substantive information. So we need to include Measurement of Success somewhere. Could be under Responsibilities as additional bullet points. Measurement of Success bullets: - Finance-validated savings are realized and reflected in the P&L. - Performance and recovery are tracked against improvement glidepaths committed with Operations. - Consistent KPIs, review cadences, and governance routines are implemented and sustained across all plants. - Standard work is documented, followed, and verified through defined adherence measures. - CI team capability and performance improve through development plans, coaching, and demonstrated ownership. We'll include those as
• under Responsibilities as well. Now Requirements: we have Minimum Qualifications (Required) and Preferred Qualifications. Also Driving Requirements: "A valid driver’s license with an acceptable driving record." Also maybe location, department, reports to, direct reports, travel, normal work schedule? But schedule is separate. We'll put location, department, reports to, direct reports, travel in a short

  before sections (metadata). Then Requirements heading will contain qualifications and driving requirements. We need to preserve all substantive info: Minimum Qualifications (Required) list: - Bachelor’s degree in Engineering; Industrial Engineering preferred. - 10+ years of progressive experience in continuous improvement, operational excellence, or manufacturing operations leadership. - Progressive experience leading continuous improvement, operational excellence, or productivity initiatives in manufacturing environments. - Strong experience developing and applying labor standards, conducting time studies, and evaluating capacity and productivity. - Experience building or materially transforming a continuous improvement program across multiple sites or business units. - Demonstrated ability to identify, quantify, prioritize, and track operational losses and improvement opportunities