Quality Control Field Technician

We need to produce HTML fragment with sections: 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. We must not include Job ID etc. Remove boilerplate: EEO, equal-opportunity, scam warning, etc. Also remove duplicated lines, navigation, cookie, legal, etc. Also remove application instructions (none present). Keep substantive info. Let's parse the posting: - Intro: "Discover a more connected career At Ansco & Associates, LLC, as a Quality Control Field Technician, you’ll ensure that construction or installation work meets specified standards by performing inspections, conducting tests, and monitoring compliance throughout projects. You’ll address issues, document findings, and collaborate with teams to implement improvements and maintain high-quality outcomes" That's about the role. - Benefits list: "Connecting You To Great Benefits Weekly Paychecks Paid Time Off, Parental Leave, and Holidays Insurance (including medical, prescription drug, dental, vision, disability, life insurance) 401(k) w/ Company Match Stock Purchase Plan Education Reimbursement Legal Insurance Discounts on gym memberships, pet insurance, and much more!" We need to format as list. - What You’ll Do: list of duties. - What You’ll Need To: list of requirements: be 18+, authorization to work, valid driver's license, one year relevant work experience. - Additional Qualifications: list: quality control experience preferred, Associates Degree in industry related field or equivalent work experience, knowledge of telecommunication construction industry standard practices, knowledge of Customer Installation Standards and Documentation. - Physical Abilities & Exposures: list: routinely: work alone in remote locations, operate vehicle, squeeze, bend, stoop, stand, walking, climb stairs, use keyboard and mouse; occasionally: work at heights, use ladder, life greater than 55 pounds (typo: life? maybe lift). We'll keep as given. - Why grow your career with us: paragraph about training, supportive environment, safety-first culture. - Building stronger solutions together: EEO statement (should be removed as boilerplate). So we remove that. Thus sections: About the role: intro paragraph. Responsibilities: the "What You’ll Do" list. Requirements: the "What You’ll Need To" list (basic eligibility). Could also include driver's license etc. Qualifications: Additional Qualifications list (preferred experience, education, knowledge). Could also include Physical Abilities & Exposures? Might be under Skills? But Physical Abilities & Exposures is more about physical demands; could be under Requirements or Qualifications. The instruction: Use headings for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - About the role: intro paragraph. - Responsibilities: duties list. - Requirements: basic eligibility (age, work auth, driver's license, experience). - Qualifications: preferred experience, education, knowledge. - Skills: maybe physical abilities? Or we could treat Physical Abilities & Exposures as Skills? But better to put under Requirements? However we already used Requirements for basic eligibility. Could create a Skills section for physical abilities and maybe knowledge? But knowledge already in Qualifications. Let's decide: Use Skills for physical abilities and maybe other skill sets. The posting includes "Physical Abilities & Exposures". That's more about physical demands; could be under Skills. We'll create a Skills section with that list. - Benefits: benefits list. - Pay: not specified besides "Weekly Paychecks" mentioned under Benefits. Actually "Weekly Paychecks" is a benefit (pay frequency). There's no specific pay amount. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Weekly Paychecks" under Benefits. That's a pay frequency, but not a specific amount. Should we include Pay section? The posting says "Weekly Paychecks" as part of benefits list. It doesn't give a salary range. The instruction: never create Pay section unless posting actually states them. It does state weekly paychecks, which is about pay frequency. Might be considered pay info. However they said "Prefer a few substantive sections over many thin ones." Could combine pay info into Benefits? But they said Benefits section for benefits like PTO, insurance etc. Pay could be separate if they mention pay. Since they mention weekly paychecks, we could include a Pay section with that detail. However they also said "never create Pay/Schedule/Benefits sections unless the posting actually states them." They do state weekly paychecks, so we can include Pay section with that detail. But we also have Benefits section with other benefits. Could we combine? The instruction: "Prefer a few substantive sections over many thin ones." If we split Pay and Benefits, that's two sections; maybe we could combine them into Benefits? But they specifically list Benefits heading as allowed. The posting includes "Weekly Paychecks" as a benefit; we could treat that as part of Benefits. However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." Since they state weekly paychecks, we could create Pay section. But we also have other benefits; we could still have Benefits section for other benefits. That would be two sections. Is that too thin? Possibly but still substantive. However we could also include Pay as a subsection inside Benefits? But they want headings exactly as listed; we can choose to include Pay if we have content. Let's include Pay section with "Weekly paychecks". Benefits section with other benefits. Schedule: Not mentioned besides overtime, travel, on-call, after-hours, all weather conditions. That's schedule info. The posting mentions "Work overtime, travel, and handle on-call or after-hours responsibilities as needed, and perform duties in all weather conditions". That's schedule-related. So we can create Schedule section with that detail. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Now we need to format: - Use

for section headings. - Use

• for any list of duties/requirements/benefits. - Use

  for prose. - Do not repeat job title as heading. - Do not put Job ID etc. - Remove boilerplate: EEO statement, etc. - Preserve all substantive information. Let's extract content precisely. About the role paragraph: "Discover a more connected career At Ansco & Associates, LLC, as a Quality Control Field Technician, you’ll ensure that construction or installation work meets specified standards by performing inspections, conducting tests, and monitoring compliance throughout projects. You’ll address issues, document findings, and collaborate with teams to implement improvements and maintain high-quality outcomes" We could keep as one paragraph. Responsibilities list (What You’ll Do): - Conduct quality inspections during the installation process to ensure work meets plans and specifications - Perform final inspections as requested by customers to ensure compliance with construction standards - Identify issues and report them to relevant team members for resolution - Record and follow up on non-compliance issues until they are resolved - Ensure all required testing is completed as specified and document the results - Follow installation milestones and support project activities as directed by management - Work overtime, travel, and handle on-call or after-hours responsibilities as needed, and perform duties in all weather conditions - Other duties as assigned Note: The last bullet about overtime etc could also go to Schedule, but it's in responsibilities. We'll keep it there; but we also have Schedule section for schedule specifics. Might duplicate. Better to move overtime/travel/on-call to Schedule, and keep responsibilities focused on inspections etc. However the instruction: preserve ALL substantive information; we can't remove it. We can place it in either Responsibilities or Schedule. Since Schedule section is for schedule info, we can put that bullet there. But we need to ensure we don't lose it. Let's parse: The bullet "Work overtime, travel, and handle on-call or after-hours responsibilities as needed, and perform duties in all weather conditions" is schedule-related. We'll put it under Schedule. Thus Responsibilities list will exclude that bullet. Now Requirements list (What You’ll Need To): - Be 18 years of age or older - Authorization to work in the United States for this company - Valid State driver's license (cannot be Provisional), including an acceptable driving record - One year of relevant work experience Now Qualifications list (Additional Qualifications): - Quality control experience preferred - Associates Degree in an industry related field or equivalent work experience - Knowledge and understanding of the telecommunication construction industry standard practices - Knowledge of Customer Installation Standards and Documentation Now Skills list (Physical Abilities & Exposures): We need to parse the list: "Routinely: work alone in remote locations, operate vehicle, squeeze, bend, stoop, stand, walking, climb stairs, use keyboard and mouse Occasionally: work at heights, use ladder, life greater than 55 pounds" We need to turn into list items. Could be two sub-lists? But we can just make each item a bullet with description. We'll preserve the phrasing. Thus Skills list: - Routinely: work alone in remote locations, operate vehicle, squeeze, bend, stoop, stand, walking, climb stairs, use keyboard and mouse - Occasionally: work at heights, use ladder, lift greater than 55 pounds Note: "life" likely typo for "lift". We'll keep as given? Might be better to correct? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Changing "life" to "lift" could be considered inventing? It's correcting a typo; but it's not adding info. Might be okay but safer to keep as "life greater than 55 pounds". However that seems nonsensical. I'd keep as given: "life greater than 55 pounds". It's preserving the text. Now Benefits list: From "Connecting You To Great Benefits Weekly PaychecksPaid Time Off, Parental Leave, and HolidaysInsurance (including medical, prescription drug, dental, vision, disability, life insurance)401(k) w/ Company MatchStock Purchase PlanEducation ReimbursementLegal InsuranceDiscounts on gym memberships, pet insurance, and much more!" We need to split into items. The text seems concatenated without spaces. We need to parse: - Weekly Paychecks - Paid Time Off, Parental Leave, and Holidays - Insurance (including medical, prescription drug, dental, vision, disability, life insurance) - 401(k) w/ Company Match - Stock Purchase Plan - Education Reimbursement - Legal Insurance - Discounts on gym memberships, pet insurance, and much more! We'll make each a

• . Now Pay section: we already used Weekly Paychecks in Benefits. But if we move Weekly Paychecks to Pay, we need to avoid duplication. Let's decide: Put Weekly Paychecks under Pay section. Benefits section will have other benefits (PTO, holidays, insurance, 401k, stock purchase, education reimbursement, legal insurance, discounts). That seems reasonable. Thus Pay section:

  Weekly paychecks

  or
  • Weekly paychecks
  . Since it's a single item, we can use

  . Schedule section: includes overtime, travel, on-call/after-hours, all weather conditions. Also maybe other schedule info? Not else. Thus Schedule list: - Work overtime, travel, and handle on-call or after-hours responsibilities as needed - Perform duties in all weather conditions We could combine into one bullet: "Work overtime, travel, and handle on-call or after-hours responsibilities as needed, and perform duties in all weather conditions". Keep as one. Now we need to ensure we didn't miss any substantive info: The "Why grow your career with us" paragraph: "Your career here is more than just a job — it's your pathway to opportunity. Our hands-on training, supportive environment, and responsive leadership connect you to work with purpose. Our commitment to