Sample Storage Support Specialist - Environment Testing - Sun-Thurs, 8pm - 6:30am

We need to output HTML fragment with sections: About the role? The posting includes a job description with position summary, essential duties, qualifications, additional info (pay, benefits). We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include a section only when posting has real specific content. We must not repeat job title as heading. Must not put Job ID etc. Must preserve all substantive info, no invented or summarized away detail. Remove boilerplate etc. We need to parse content: - Position Summary: "Interpreting and entering client samples into computer system; managing large projects; maintaining client files; delivering rush samples; serving as information contact at receipt of samples in an efficient and detailed manner with a high degree of quality" - Essential Duties and Responsibilities: list of many items. - Qualifications: Basic Minimum Requirements: High School Diploma or equivalent; Ability to lift up to 50 lbs. frequently; Computer skills, including data entry; Professional working proficiency in English; Authorization to work in the United States without restriction or Sponsorship - Ideal Candidates will have: 1+ years of related laboratory experience; Ability to communicate effectively, both orally and in writing; Strong organizational skills and detail orientation; Ability to work independently and as part of a team; Ability to stay productive during times of high volumes of incoming samples; Able to retain large amounts of information - Additional Information: Pay rate: $17.75/hour + 10% shift differential; note about compensation range (but we should not include placeholder like "may vary". The posting includes a note that actual base salary may vary; but we should not include filler like "commensurate with experience". However we can include the pay rate and note that actual may vary? The instruction: "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')". The note about actual base salary may vary is somewhat filler? It says "Please note - Eurofins Environment Testing (USA) provides a compensation range for informational purposes, the actual base salary may vary based upon, but not limited to, relevant experience and skill set, base salary of internal peers, business sector, and geographic location." That's somewhat generic but it's actual content. However it's not a specific number; it's a disclaimer. The instruction says never emit a heading followed by filler/placeholder text like "varies". The phrase "actual base salary may vary" is a qualifier. Might be considered filler? Safer to omit that note and just include the pay rate: $17.75/hour + 10% shift differential. That is specific. - Benefits: "As a Eurofins employee, you will become part of a company that has received national recognition as a great place to work. We offer excellent full-time benefits including comprehensive medical coverage, life and disability insurance, 401(k) with company match, paid holidays, paid time off, and dental and vision options. *The benefits package offered will vary based on the employee’s full-time or part-time regular status." The second sentence about varying based on status is filler? It says will vary based on status; that's somewhat generic but still info. Might be considered filler? The instruction says never emit a heading followed by filler/placeholder text like "varies". The benefits section includes a statement that benefits vary based on status; that could be considered filler. However we could keep the first sentence about benefits offered, and maybe omit the varying note. But we must preserve ALL substantive information; we cannot invent or summarize away detail. The varying note is substantive? It's a qualifier; but maybe we can keep it as it's not placeholder like "varies" alone; it's a sentence explaining variation. Might be okay. - Schedule: "Role is full time: Sun-Thurs, 8:00pm - 6:30am . Training will be M-F 1st shift, 8am-4:30pm." That's specific schedule info. - About the role: Could be the Position Summary? Or we could treat "About the role" as the Position Summary. The instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have: - About the role: Position Summary (maybe also company intro? but we should not include boilerplate like company description? The initial paragraph about Eurofins is company overview; could be considered About the role? Might be considered boilerplate? It's not job-specific but still about the company. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company overview might be considered boilerplate? It's not strictly legal; it's descriptive. Might be okay to keep? But we need to preserve ALL substantive information; the company overview is substantive about the employer. However the instruction about sections: we can include About the role heading and put the Position Summary there. The company overview could be placed before any heading? The output should be only HTML fragment; we could include a

with company overview before headings? Not sure. The instruction says "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." So we can include a short

for minor metadata like company overview? Might be okay. Better to follow typical structure: About the role: Position Summary. Responsibilities: Essential Duties and Responsibilities (list). Requirements: Basic Minimum Requirements (maybe also Ideal Candidates?). Qualifications: maybe combine Requirements and Qualifications? But we have separate headings: Requirements, Qualifications, Skills. We need to decide what goes where. We have: - Basic Minimum Requirements (education, lift, computer skills, English proficiency, work authorization) -> could go under Requirements. - Ideal Candidates will have (experience, communication, organizational skills, teamwork, productivity, retention) -> could go under Qualifications or Skills. - Skills: maybe the communication, organizational skills, detail orientation, ability to work independently/team, staying productive, retain information. We could map: - Requirements: Basic Minimum Requirements. - Qualifications: Ideal Candidates will have (experience, etc.) - Skills: maybe we could list specific skills like communication, organizational, detail orientation, teamwork, etc. But that overlaps. Given the instruction to prefer a few substantive sections over many thin ones, we could combine Requirements and Qualifications into one section? But we have headings list; we can include only those with real content. We could include About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. That's 7 sections. Might be okay. We need to avoid filler like "varies". For Benefits we have a sentence about benefits varying based on status; maybe we keep it but it's not filler like "varies" alone; it's a statement. Might be okay. Pay: we have specific pay rate. Schedule: we have schedule. Now we need to format lists: Use

• for any list of duties/requirements/benefits. Thus: - About the role:

  Position Summary: Interpreting and entering client samples into computer system; managing large projects; maintaining client files; delivering rush samples; serving as information contact at receipt of samples in an efficient and detailed manner with a high degree of quality

  But we might not need to repeat "Position Summary:"; just the summary. - Responsibilities:
  • Applies GMP/GLP in all areas of responsibility, as appropriate
  ... etc. We need to extract each duty from the list: Essential Duties and Responsibilities: Applies GMP/GLP in all areas of responsibility, as appropriate Demonstrates and promotes the company vision Regular attendance and punctuality Moderate sample interpretation of clients’ analytical requirements and data entry into computer system by keeping up-to-date with technical center requirements Project management of client projects; liaison between project manager and Sample Registration Delivery of rush samples to appropriate technical centers Maintain client files containing quotes, purchase orders, bottle orders, and incoming sample activity records Handling of incoming informational calls into department Read, understand, and carry out standard operating procedures; follow all safety precautions and procedures Unpack sample kits and coolers received at lab Provide training assistance within department to new and/or current employees Assist as needed throughout the department (labeling samples, filing paperwork, etc Conducts all activities in a safe and efficient manner Performs other duties as assigned Note there is a missing closing parenthesis in "(labeling samples, filing paperwork, etc". We'll keep as is. We need to preserve all substantive information; we should not fix grammar. - Requirements: Basic Minimum Requirements: High School Diploma or equivalent Ability to lift up to 50 lbs. frequently Computer skills, including data entry Professional working proficiency in English is a requirement, including the ability to read, write and speak in English. Authorization to work in the United States without restriction or Sponsorship We could make each a
  • . - Qualifications: Ideal Candidates will have: 1+ years of related laboratory experience Ability to communicate effectively, both orally and in writing Strong organizational skills and detail orientation Ability to work independently and as part of a team Ability to stay productive during times of high volumes of incoming samples Able to retain large amounts of information - Benefits: we have paragraph: "As a Eurofins employee, you will become part of a company that has received national recognition as a great place to work. We offer excellent full-time benefits including comprehensive medical coverage, life and disability insurance, 401(k) with company match, paid holidays, paid time off, and dental and vision options. *The benefits package offered will vary based on the employee’s full-time or part-time regular status." We could make a

    for the first sentence and second sentence? Or combine into one

    . The instruction: Use

    for prose. So we can put the benefits description in a

    . The list of benefits could be a

    but they are already in a sentence. Could also make a list: comprehensive medical coverage, life and disability insurance, 401(k) with company match, paid holidays, paid time off, dental and vision options. That is a list. Might be better to use
    • for benefits. The instruction: Use
      • for any list of duties/requirements/benefits. So we should make a list. Thus Benefits section:

        Benefits

        • comprehensive medical coverage
        • life and disability insurance
        • 401(k) with company match
        • paid holidays
        • paid time off
        • dental and vision options

        As a Eurofins employee, you will become part of a company that has received national recognition as a great place to work.

        The benefits package offered will vary based on the employee’s full-time or part-time regular status.

        But we need to avoid filler like "varies". The second sentence includes "will vary". Might be considered filler? The instruction says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). It says "never emit a heading followed by filler/placeholder text". It doesn't say we cannot have a sentence containing the word "varies". It's about a heading followed by filler/placeholder text. So if we have a Benefits heading and then a

        that says "The benefits package offered will vary based on the employee’s full-time or part-time regular status." That is not filler/placeholder text; it's a specific statement. So it's okay