FSQA Technician Cook

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. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, legal, etc. Also remove application instructions (none). Keep substantive info. We need to parse the posting. Job Title: Quality Assurance Technician 1st Shift - Location: Tyler, Tx Department: Quality Assurance Tech RTE - Reports To: Quality Assurance Supervisor RTE Normal Work Schedule: The typical working hours are 6:00 am to 3:00pm, with a 45-minute lunch. Overview Of Company: description. Job Summary: description. Qualifications: Minimum Qualifications (Required) and Preferred Qualifications. Key Responsibilities: description. Work Environment: description. Physical Demands: description. Benefits: list of benefits after "The applicant who fills this position will be eligible for the following:" then list. Pay: not mentioned. So we should NOT include Pay section. Schedule: we have Normal Work Schedule: typical working hours 6:00 am to 3:00pm, with a 45-minute lunch. That's schedule info. So we can include a Schedule section. We also have location and department etc. Could be part of About the role? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role (maybe includes overview, job summary, location, department, reports to). Responsibilities (key responsibilities). Requirements (maybe minimum qualifications). Qualifications (maybe preferred? But they said Qualifications as a heading; we could combine minimum and preferred under Qualifications? But they also have Requirements separate. Could treat Requirements as minimum qualifications, Qualifications as preferred? Or we could have Requirements for minimum, Qualifications for preferred. Or we could combine both under Qualifications and skip Requirements. But they said prefer few substantive sections over many thin ones. We have a lot of info; we could do: About the role, Responsibilities, Qualifications (including both minimum and preferred), Benefits, Schedule. That's 5 sections. That seems fine. We must not include Skills unless there is specific skill list; we have some skills mentioned but could be part of Qualifications. So we skip Skills. We must not include Pay. We must not include empty sections. Now we need to format content: Use

• for any list of duties/requirements/benefits, and

  for prose. Thus for each section we need to decide if content is list or prose. About the role: could be prose summarizing overview, job summary, location, department, reports to. We'll put in

  . Responsibilities: list of duties from Key Responsibilities and maybe Work Environment? Actually Work Environment is separate but could be part of responsibilities? But we can treat Work Environment as part of Responsibilities? However they said use

  • for any list of duties/requirements/benefits. Work Environment is not a list but prose. Could be its own section? But we don't have a heading for Work Environment; we could incorporate into Responsibilities as prose. But we have Physical Demands also. Could be part of Responsibilities? Might be better to have separate sections for Work Environment and Physical Demands? But we don't have predefined headings for those; we could still use

    with custom headings? 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? It says use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect only those headings. So we should not create other headings like Work Environment. So we need to fit that info into existing sections. We can put Work Environment and Physical Demands under Responsibilities as prose (maybe as part of responsibilities). Or we could put them under About the role? Better to put under Responsibilities as prose describing the work environment and physical demands. Benefits: list. Schedule: we have schedule info: typical working hours 6:00 am to 3:00pm, with a 45-minute lunch. That's prose; could be

    . Now we need to preserve all substantive information; do not invent or summarize away detail. So we must include all details from the posting, but we can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can rephrase? Probably we should keep the details as is, maybe copy sentences. We can keep them but format into HTML. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to remove the EEO paragraph at the end, also the "John Soules Foods is an Equal Employment Opportunity Employer..." etc. Also remove "Applicants with disabilities needing accommodation..." etc. Also remove "We also participate in the E-Verify program..." etc. Also remove duplicated lines? Not seeing duplicates. Now let's extract substantive content: - Job Title: Quality Assurance Technician 1st Shift - Location: Tyler, Tx Department: Quality Assurance Tech RTE - Reports To: Quality Assurance Supervisor RTE Normal Work Schedule: The typical working hours are 6:00 am to 3:00pm, with a 45-minute lunch. But we are not to repeat job title as heading; we can include location, department, reports to in About the role prose. - Overview Of Company: paragraph about John Soules Foods. - Job Summary: paragraph about QA Technician supports QA Supervisor etc. - Qualifications: Minimum Qualifications (Required) list: Working knowledge of food safety and quality systems, including HACCP, GMPs, and SSOPs, Intermediate computer proficiency (e.g., data entry, basic spreadsheets, document management), ability to stand firm on quality issues while maintaining respect with staff, excellent attendance, and strong communication and interpersonal skills. Must have the willingness to work overtime, including weekends, as needed. - Preferred Qualifications: 2 years of experience in a food processing or manufacturing environment, prior experience in a QA Technician or QA Lead Technician role, and knowledge of the company’s products and equipment. Familiarity with regulatory compliance standards (e.g., USDA, FDA, third-party audits), strong focus, time management, organizational skills, and the ability to work in a team-oriented environment. Bilingual (English/Spanish) is a plus. - Key Responsibilities: note: description not all-inclusive. Then bullet? Actually it's prose: "The QA Technician will work primarily on the production floor, which includes cold temperature zones (40 F – 45 F), and may be exposed to food-related odors, dust, and seasoning particles. This role requires working near machinery and frequent interaction with production and sanitation teams, and is a fast-paced environment requiring attentiveness and quick problem-solving. Always wearing PPE is required to follow the company’s Safety and Food Safety Polices." But that's actually under Work Environment heading. Wait the posting had: Key Responsibilities NOTE: This description is not intended to be all-inclusive. An employee may perform other related duties to meet the organization's ongoing needs; these duties are considered marginal. Work Environment The QA Technician will work primarily on the production floor, which includes cold temperature zones (40 F – 45 F), and may be exposed to food-related odors, dust, and seasoning particles. This role requires working near machinery and frequent interaction with production and sanitation teams, and is a fast-paced environment requiring attentiveness and quick problem-solving. Always wearing PPE is required to follow the company’s Safety and Food Safety Polices. Physical Demands The position requires regular standing, walking, bending, climbing stairs, and lifting (up to 50 pounds). Use their hands for tasks, reach with their arms, communicate verbally, and be able to perform detailed paperwork and inspections requiring focus and precision. Close, distance, color vision, depth perception, and the ability to adjust focus. The applicant who fills this position will be eligible for the following: Vacation Sick days Medical, Dental, Vision Benefits 401k with company match Telemedicine Onsite Clinic – Tyler and Valley Free annual health screening STD and LTD Life insurance Thus Key Responsibilities section only had the note about not all-inclusive; no actual responsibilities listed? Actually the responsibilities might be implied in the earlier Job Summary? The Job Summary gave responsibilities: monitoring HACCP, GMPs, SSOPs, product specifications monitoring, detailed documentation, real-time corrective actions, clear communication across all levels. Thus we need to capture responsibilities from Job Summary and maybe also from Key Responsibilities note (but that's just a disclaimer). So we should include responsibilities: monitoring HACCP, GMPs, SSOPs, product specifications monitoring, detailed documentation, real-time corrective actions, clear communication across all levels of the production process to maintain consistent product quality and safety. Also maybe other duties? Not needed. Thus Responsibilities section will be a list of duties. Now Work Environment and Physical Demands we need to incorporate somewhere. Could be under Responsibilities as prose describing environment and demands. Thus Responsibilities section could have a

    • for each duty, and then maybe a

      for environment and physical demands? But instruction: Use

      • for any list of duties/requirements/benefits, and

        for prose. So we can have both list and prose within same section? Probably we can have a

        for duties list, then a

        for environment and physical demands. That's okay. Now Benefits: list of benefits: Vacation, Sick days, Medical, Dental, Vision Benefits, 401k with company match, Telemedicine, Onsite Clinic – Tyler and Valley, Free annual health screening, STD and LTD Life insurance. We need to preserve each item exactly as posted? The posting: "Vacation Sick days Medical, Dental, Vision Benefits 401k with company match Telemedicine Onsite Clinic – Tyler and Valley Free annual health screening STD and LTD Life insurance". It seems missing commas between some. We should keep as is but maybe separate items with commas? Better to keep exactly as posted but we can format as list items each separated by line breaks. However the original lacks punctuation; we could keep as is but it's ambiguous. We could split by spaces? Might be better to keep as a single string? But instruction: preserve ALL substantive information; do NOT invent or summarize away detail. If we split incorrectly we might be altering. Safer to keep the exact sentence as a single

        ? But they said use

        • for any list of benefits. So we need to make a list. We need to decide how to split items logically. The posting likely intended each as separate benefit: Vacation, Sick days, Medical, Dental, Vision Benefits, 401k with company match, Telemedicine, Onsite Clinic – Tyler and Valley, Free annual health screening, STD and LTD Life insurance. We can infer that. That seems reasonable and not inventing? It's interpreting but likely acceptable. However to be safe, we could keep as a single

          with the exact string, but then we violate the rule to use

          • for any list. The rule says "Use
            • for any list of duties/requirements/benefits". If we treat it as a list, we should use
              • . If we treat it as not a list (just a sentence), we could use

                . But it's clearly a list. I'd go with splitting into logical items. Now Schedule: we have "Normal Work Schedule: The typical working hours are 6