Production Scheduler

We need to output HTML fragment with sections: h3 headings for sections present: About the role? The posting includes a summary paragraph; we can treat that as "About the role" maybe. 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. Content: - Summary: description of role: "As a Production Scheduler for RedBuilt LLC, your primary focus will be on scheduling manufacturing production needs across multiple locations and product lines..." This is prose. Could be under "About the role". - Responsibilities: bullet list. - Requirements, Knowledge, Skills, and Abilities: bullet list. - Working Conditions: prose. - Reports to: Supply Chain Manager (metadata). FLSA Classification: Exempt. Job Type: Full-time. Pay: DOE (depends on experience). Work Location: Boise, ID | Chino, CA | Delaware, OH | Hillsboro, OR | Stayton, OR. Benefits: list. - Also mention: "If this sounds like you, we’d love to hear from you!" (application instruction? maybe drop). Also "Please note that the job description is not designed to cover or contain a comprehensive listing..." (boilerplate). Also "RedBuilt is an equal opportunity employer. Must take pre-employment drug test and a background check..." (EEO boilerplate, remove). Also "Please note that the job description is not designed to cover..." remove. We need to include sections only if real specific content. We have: - About the role: summary paragraph. - Responsibilities: list. - Requirements, Knowledge, Skills, and Abilities: list (maybe combine Requirements and Skills). Could be one section "Requirements". The instructions list possible headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose "Requirements" to cover the bullet list. - Benefits: list. - Pay: The posting says "Pay: DOE". That's not specific; it's placeholder "DOE". According to instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state Pay: DOE, but that's not a specific amount; it's "depends on experience". Is that considered placeholder? The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "DOE" is similar to "depends on experience". That's likely considered placeholder. So we should NOT create a Pay section. - Schedule: Not mentioned explicitly. No schedule details. So no Schedule section. - Working Conditions: Could be a section? Not in the list of headings but we could still use

  for any section heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. We could still use "Working Conditions" as heading if we want. However they say prefer a few substantive sections over many thin ones. Working Conditions is a short prose paragraph; maybe we can incorporate into About the role or Requirements? But it's distinct. Could be its own section "Working Conditions". However they didn't list it as example but likely allowed. But to keep few sections, maybe we can fold Working Conditions into About the role or Requirements? It's about physical demands; maybe better as its own short section. But we need to avoid many thin sections. We have About the role, Responsibilities, Requirements, Benefits, maybe Working Conditions. That's 5 sections. Could be okay. Alternatively we could combine Working Conditions into About the role as an extra paragraph. That would keep sections fewer. Let's decide: We'll have sections: About the role (summary + working conditions), Responsibilities, Requirements, Benefits. We need to preserve all substantive information. So we need to include the working conditions sentence somewhere. We'll add it to About the role after the summary. Now we need to format. - About the role:

  About the role

  then

  with the summary prose plus working conditions sentence. Summary: "As a Production Scheduler for RedBuilt LLC, your primary focus will be on scheduling manufacturing production needs across multiple locations and product lines. You will work closely with other supply chain team members to understand inventory constraints and timeline requirements to meet customer dates. A critical job function will require maintaining strong relationships with plant management to help coordinate staffing and resource needs. You will use both the Microsoft Platform and NetSuite ERP systems to monitor production needs, customer dates, and general project movements. The Production Scheduler will be a critical role ensuring customer orders are scheduled efficiently for just in time manufacturing practices. You'll work within a small, collaborative supply chain team where access to support is always available. This role requires attention to detail and strong communication skills to coordinate information that multiple departments rely on. Production planning requires being a team player with sales team members when prioritizing project work. If you can respond to urgent requests with calm decision making this is the position for you." Working Conditions: "Prolonged periods of sitting/standing at a desk and working on a computer." We can combine: after the summary, add a sentence: "Working conditions involve prolonged periods of sitting/standing at a desk and working on a computer." Now Responsibilities: list bullet points. Responsibilities bullet list from posting: - Set Production Schedule: Receive internal order requests and place within manufacturing schedule. Note: this role is responsible for placing orders into needed time blocks for production, it is the responsibility of the product line manager to schedule specific production lines. - Monitor schedule for date changes or open availability for work shifts. - Manage dates, communication, and timeline needs with plant and project management. - Proactively communicate with internal team members about scheduling constraints and actively participate in solutioning efforts. Including, but not limited to, discussing overtime opportunities, sharing information of down manufacturing time, prioritization conversations for competing work, etc. - Product Lines: OpenWeb Wall Panels Steel Fabrication Plated Truss - Cross Functional Support: Work closely with procurement team members for specialty item availability. Proactively monitor schedule openings for urgent projects. Active participation in continuous improvement efforts for procedures and automation. We need to preserve all substantive information. The bullet list may be split into multiple

• . We'll keep each bullet as an
• . For the note inside first bullet, we keep as part of same
• . Now Requirements, Knowledge, Skills, and Abilities: bullet list: - 3+ years working in supply chain, manufacturing, scheduling/planning, or related field. - Effective communication: Clear communication with internal and external stakeholders. - Fantastic organizational and time management skills, with a proven ability to meet deadlines. - Self-sufficient and willing to take ownership of tasks with a desire to learn new skills. - Proficiency with computers, email, and Microsoft Excel. - Bachelor’s degree in supply chain or other relevant field is preferred. - Experience working in ERP systems (NetSuite preferred) is a plus. We'll put these as
• . Now Benefits: list: - 11 Paid Holidays (includes 2 Floating Holidays of your choosing) - Paid Time Off - Paid Community Service - Health Benefits (Medical, Dental, Vision) - FSA/HSA Options - Discounted Pet Insurance - 401k Retirement Plan with Employer Matching - Opportunity for bonus - Paid Parental Leave - Flexible Dependent Care Account - Employee Assistance Program (EAP) - Company Paid Basic Life and AD&D Insurance - Company Paid Short Term Disability - Voluntary Long-Term Disability - Voluntary Life and AD&D Insurance We'll put each as
• . We need to exclude boilerplate: "Reports to: Supply Chain Manager FLSA Classification: Exempt Job Type: Full-time Pay: DOE Work Location: Boise, ID | Chino, CA | Delaware, OH | Hillsboro, OR | Stayton, OR". This is metadata; we could fold into a short

  maybe under About the role? But instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. This is minor metadata (reports to, FLSA, job type, pay, work location). We could include a short paragraph after About the role maybe. But we already have About the role with summary; we could add a

  for metadata. However they said prefer a few substantive sections over many thin ones. Adding a metadata paragraph might be okay as part of About the role? Could add a second

  under About the role for metadata. But we need to preserve all substantive information; this metadata is substantive (reports to, job type, work location). So we should include it. We could create a section "Details" but not in examples. Better to add a

  after the summary within About the role? Or we could create a separate section "Job Details". But to keep sections few, we can add a

  after the summary within the same section? The instruction: Use

  for section headings,

  • for any list, and

    for prose. So we can have multiple

    under a heading. So we can have About the role heading, then a

    for summary, then a

    for metadata (reports to, job type, work location). That seems fine. We need to exclude "If this sounds like you, we’d love to hear from you!" (application instruction) and the EEO boilerplate and the note about job description not comprehensive. Now we need to output only HTML fragment. Let's craft:

    About the role

    As a Production Scheduler for RedBuilt LLC, your primary focus will be on scheduling manufacturing production needs across multiple locations and product lines. You will work closely with other supply chain team members to understand inventory constraints and timeline requirements to meet customer dates. A critical job function will require maintaining strong relationships with plant management to help coordinate staffing and resource needs. You will use both the Microsoft Platform and NetSuite ERP systems to monitor production needs, customer dates, and general project movements. The Production Scheduler will be a critical role ensuring customer orders are scheduled efficiently for just in time manufacturing practices. You'll work within a small, collaborative supply chain team where access to support is always available. This role requires attention to detail and strong communication skills to coordinate information that multiple departments rely on. Production planning requires being a team player with sales team members when prioritizing project work. If you can respond to urgent requests with calm decision making this is the position for you.

    Reports to: Supply Chain Manager. FLSA Classification: Exempt. Job Type: Full-time. Work Location: Boise, ID | Chino, CA | Delaware, OH | Hillsboro, OR | Stayton, OR.

    Responsibilities

    • Set Production Schedule: Receive internal order requests and place within manufacturing schedule. Note: this role is responsible for placing orders into needed time blocks for production, it is the