Production Worker III

Here's a thinking process: 1. **Analyze User Request:** - Input: A job posting for "Production Worker / Pasteurizer" in Bellevue, WA - Task: Reformat into clean, well-structured semantic HTML - Rules: - Use `

` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule) - Use `

• ` for lists of duties/requirements/benefits - Use `

  ` for prose - Do NOT repeat job title as heading (already shown) - Do NOT put Job ID / requisition numbers as headings - 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 2. **Analyze the Job Posting Content:** Let me extract the meaningful sections from the provided text: **Title/Location/Shift info:** - Title: Production Worker / Pasteurizer - Location: Bellevue, WA, 98005 - Shift (1) Swing Shift (2pm to 10:30pm) Schedule will be Monday through Friday - Shift (2) Grave Shift (10pm to 6:30am) Schedule will be Sunday through Thursday - Candidates must be flexible for overtime if needed **Main Responsibilities** (listed with " " prefix): - Closely monitor the dairy production process and follow Standard Operating Procedures for batching and processing products. - Maintain communication with other departments, management and employees and notify them of any problems and/or concerns that may restrict the efficiency of production. - Ensure all required information is documented in accordance with Federal, State, and Company Laws/Policies. - Monitor fats, total solids, allergens, and other related items as they associate with processing dairy products. - Maintain sanitation of equipment including CIP & hand cleaning. - Operate and clean equipment with a sense of urgency to maximize throughput and minimize downtime. - Analyze process data and equipment performance data to improve quality, throughput, and troubleshoot. - Follow Good Manufacturing Practices. - Follow all required work safe practices. - Responsible for food safety, pre-requisite programs and food quality related to designated area. - Report any food safety and food quality related issues to management immediately. - Perform other duties as assigned. - Must always maintain and promote a safe working environment and have a safety-first mindset. - Follow and maintain 5S standards for work areas and comply with company GMP standards. - Other duties as assigned by supervisor. **Requirements** (listed with " " prefix): - Must possess good written and verbal communication skills. - Perform basic math with ability to add, subtract, multiply and divide. - Stand/ walk almost the entire workday. - Basic understanding of food safety and sanitation practices. - Ability to follow recipes, measurements, and instructions accurately. - Physical stamina to stand for extended periods and lift/move heavy objects. - Attention to detail and commitment to quality. - Good communication skills and ability to work effectively in a team environment. - Flexibility to work in a fast-paced production environment and adapt to changing priorities. - Willingness to follow safety protocols and adhere to company policies and procedures. **What We Are Searching For** (looks like a duplicate/repeat of Requirements, but I'll check): - High school diploma or equivalent. - If candidate has a Pasteurizers License the the manager is looking for for a minimum of 6 - 12 months operating pasteurization or dairy process equipment. - If candidate does not have a Pasteurizers License the manager is looking for a minimum of 12 months operating pasteurization or dairy process equipment. - Ability to follow recipes, measurements, and instructions accurately. - Physical stamina to stand for extended periods and lift/move heavy objects. - Attention to detail and commitment to quality. - Good communication skills and ability to work effectively in a team environment. - Flexibility to work in a fast-paced production environment and adapt to changing priorities. - Willingness to follow safety protocols and adhere to company policies and procedures. - Must be able to lift up to 50 lbs - Note: Candidate must have previous experience with pallet jacks and forklift. I need to be careful about the "What We Are Searching For" section. It seems to overlap with Requirements but has additional specific stuff about Pasteurizers License, 50 lbs, pallet jacks/forklift. I should probably merge or structure it logically, but the rules say: "Preserve ALL substantive information; do NOT invent or summarize away detail." and "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". Also, "Prefer a few substantive sections over many thin ones." Let me identify the unique sections with real content: - About the role? Not really a specific section heading, but there's location and shift info. I could put that in a short prose paragraph or under a minimal heading. The rules say use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But also: "Do NOT repeat the job title as a heading (the page already shows it)" and "include a section ONLY when the posting has real, specific content for it". So "About the role" could contain location/shift info. But I need to be careful not to create thin sections. Let me re-read the rules carefully: - "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." So I need to decide which sections to include. The posting has: - Location/shift info (metadata, fold into short

    ) - Responsibilities (real content) - Requirements (real content) - What We Are Searching For (real content, but overlaps with Requirements; I should probably merge or present as one section with all unique requirements) - No explicit Benefits, Pay, Schedule sections with actual content beyond what's stated (shifts are stated, but "Schedule" as a section might just repeat shift info; I'll be careful) - No Pay mentioned, so no Pay section. - Schedule is stated but I'll fold into a paragraph or minimal section. The headings suggested: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But I should only create those that have real content. Let's map: - "About the role": Could contain location and shift info. But the rule says "fold minor metadata into a short

    or drop it." So maybe I just put location/shift in a

    at the top or inside a section. - "Responsibilities": Yes, has content. - "Requirements": Yes, has content. - "Qualifications": The "What We Are Searching For" section seems like qualifications. I could merge with Requirements or make a separate Qualifications section. The rules say "Prefer a few substantive sections over many thin ones." The Requirements and Qualifications overlap a lot. I'll probably combine the unique stuff into a single "Requirements" section or have "Requirements" and "Qualifications" if there's distinct content. Looking at the text, "Requirements" lists soft skills and basic abilities, while "What We Are Searching For" has education, license/experience requirements, physical specs, and equipment experience. I think I can merge them into one "Requirements" section with all bullet points, or have two sections but that might be thin. The rule says "Prefer a few substantive sections over many thin ones." So I'll likely have just Responsibilities and Requirements (which includes qualifications). But the example headings list both "Requirements" and "Qualifications". I need to decide based on content. Let me check if there's truly distinct content: "Requirements" has communication, math, standing, food safety basics, following recipes, physical stamina, detail, communication, teamwork, flexibility, safety protocols. "What We Are Searching For" has high school diploma, pasteurizer license/experience, ability to follow recipes, physical stamina, detail, communication, flexibility, safety protocols, lift 50 lbs, pallet jack/forklift experience. There's significant overlap. I'll merge all into a single "Requirements" section, or maybe use "Qualifications" for the education/license/experience part. But the rule says only create sections with real specific content. I think having one "Requirements" section that covers both is best, or I could have "Requirements" and "Qualifications" but ensure both are substantive. However, "Prefer a few substantive sections over many thin ones" suggests I should minimize sections. I'll go with: Responsibilities, and Requirements (which encompasses what's labeled both). I'll also include a short

    for location/shift. Wait, the rule says: "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It lists possible headings. I don't have to use all, but if I use one, it should have content. I'll structure as: - Maybe an "About the role"

    for location/shift? Or fold into Responsibilities header? The rule says "fold minor metadata into a short

    or drop it." I'll put location/shift in a

    at the top, before the h3 sections. - Then

    Responsibilities

    with
    • - Then

      Requirements

      with
      • - I won't create Benefits, Pay, Schedule sections since they aren't stated (shifts are stated but I'll fold them into the

        or mention once). - The "What We Are Searching For" I'll merge into Requirements since it's all requirements. Let me re-examine the shift schedule info: "Shift (1) Swing Shift (2pm to 10:30pm) Schedule will be Monday through Friday Shift (2) Grave Shift (10pm to 6:30am