OSP Technician

We need to output HTML fragment with sections: headings

for sections like 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). 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 parse the posting. Key sections: - Description: includes overview: "Our telecommunications client is hiring an OUTSIDE PLANT TECHNICIAN to support growing business. This position is contract-to-hire, which converts permanent after completing projects successfully and meeting company performance standards. The OSP TECHNICIAN is responsible for the installation, maintenance, repair, and troubleshooting of telecommunications infrastructure including fiber optic and copper cable networks. The OSP TECHNICIAN supports the construction and operation of outside plant facilities while ensuring network reliability, safety, compliance, and quality standards. Together, the OSP TECHNICIAN is a good fit for aspiring telecommunications, data center, fiber, copper, electric, low voltage and construction professionals." That's prose. - DUTIES: list of duties (bulleted). Should be under a heading like Responsibilities? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map DUTIES to Responsibilities. Use

  Responsibilities

  then
  • each duty. - WORK ENVIRONMENT: maybe not a standard heading; could be part of About the role? But we can include as a separate section maybe "Work Environment". However instruction says only use those headings; but we can still create other headings? It says "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests those as examples. Safer to stick to those headings. We can incorporate work environment into About the role or Responsibilities? Probably better to have a separate section "Work Environment" but not in list; but instruction says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't restrict to only those headings; they gave examples. So we can add a heading like Work Environment. However they said "use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for sections; but we could also add others if needed. To be safe, we can map work environment to About the role (maybe as a paragraph). But we have a lot of content: "Mostly Outdoors Some Indoor work Crew & Team Telecommunications Construction Overtime Monday-Saturday". That's specific. Could be placed under a heading "Work Environment". I'd include it as its own section with

    Work Environment

    . It's not in the examples but seems okay. - INTERVIEWS & START DATE: includes interview dates, start date, deadline to submit resumes. This is metadata like application instructions; we should remove application instructions per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should drop the interview and start date info? It's not exactly application instructions but it's about timing. Might be considered application instructions. The instruction says remove application instructions. Likely we should drop that section. However we need to preserve ALL substantive information; but they say remove application instructions. The interview schedule and start date could be considered substantive but also part of application process. I'd lean to remove it as it's application-related. However the start date could be considered job detail. But they said remove application instructions; start date is not exactly instruction but could be considered part of hiring process. Safer to drop it. - Job Type & Location: "This is a Contract position based out of Ames, IA." That's substantive; we can include maybe under About the role or a separate section "Job Type". Could be a short paragraph. - Pay And Benefits: includes pay range and benefits list. That's definitely substantive; we need Pay and Benefits sections. According to instruction, we should include Pay and Benefits sections only if posting actually states them. It does. So we need a

    Pay

    with the pay range. And

    Benefits

    with list of benefits. - Workplace Type: "This is a fully onsite position in Ames,IA." Could be part of About the role or Job Type. - Application Deadline: "This position is anticipated to close on Sep 24, 2026." That's application instruction; remove. - About TEKsystems: boilerplate about company; remove as it's not specific to role? It's generic company description; likely considered boilerplate; remove. - Also repeated EEO statements etc; remove. Thus final HTML should have sections: About the role (maybe combine description, job type, location, workplace type), Responsibilities (duties), Work Environment (optional), Pay, Benefits. We need to ensure we don't repeat job title as heading. So no

    OSP Technician

    . We need to preserve all substantive information: description paragraphs, duties list, work environment details, pay range, benefits list, job type/contract, location, workplace type. Let's craft. First, About the role: combine description paragraph(s) plus job type/location/workplace type. Description paragraph: "Our telecommunications client is hiring an OUTSIDE PLANT TECHNICIAN to support growing business. This position is contract-to-hire, which converts permanent after completing projects successfully and meeting company performance standards. The OSP TECHNICIAN is responsible for the installation, maintenance, repair, and troubleshooting of telecommunications infrastructure including fiber optic and copper cable networks. The OSP TECHNICIAN supports the construction and operation of outside plant facilities while ensuring network reliability, safety, compliance, and quality standards. Together, the OSP TECHNICIAN is a good fit for aspiring telecommunications, data center, fiber, copper, electric, low voltage and construction professionals." Job type/location: "This is a Contract position based out of Ames, IA." Workplace type: "This is a fully onsite position in Ames, IA." We could combine into one

    or multiple

    . Use

    for prose. Then Responsibilities:

    Responsibilities

    then
    • each duty. Duties list: - Install, maintain, and repair underground and aerial telecommunications infrastructure. - Perform fiber optic and copper cable placement, splicing support, testing, and troubleshooting. - Locate, identify, and mark existing utilities prior to excavation activities. - Read and interpret construction prints, utility maps, and engineering drawings. - Operate hand tools, power tools, and equipment used for cable installation and maintenance. - Assist with trenching, boring, conduit installation, and restoration activities. - Inspect outside plant facilities for damage, defects, or potential service interruptions. - Conduct routine maintenance and emergency repairs to minimize network downtime. - Document work completed, material usage, and field observations accurately. - Coordinate with project managers, construction crews, utility providers, and customers as needed. - Adhere to company safety policies and OSHA regulations at all times. - Participate in on-call rotations and respond to outages or emergency situations when required. Make sure each is
    • . Work Environment:

      Work Environment

      then maybe a

      with the details: "Mostly Outdoors; Some Indoor work; Crew & Team; Telecommunications; Construction; Overtime; Monday-Saturday." Could also be a list but it's not a list of duties; it's descriptive. Use

      . Pay:

      Pay

      then

      with pay range: "The pay range for this position is $20.00 - $22.00/hr. Individual compensation offered for this position within this range will depend on many factors, including qualifications, skills, relevant experience, job knowledge, geographic location, internal equity, and other pertinent job-related factors." Benefits:

      Benefits

      then
      • each benefit. Benefits list from posting: - Medical, dental & vision - Critical Illness, Accident, and Hospital - 401(k) Retirement Plan – Pre-tax and Roth post-tax contributions available - Life Insurance (Voluntary Life & AD&D for the employee and dependents) - Short and long-term disability - Health Spending Account (HSA) - Transportation benefits - Employee Assistance Program - Time Off/Leave (PTO, Vacation or Sick Leave) Make each as
      • . We should not include any filler like "Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms." That's somewhat generic but still substantive? It's about benefits eligibility. Could be included as prose after benefits list? Might be considered boilerplate but it's specific to benefits. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those; it's about benefits eligibility. Might keep it as a

        after benefits list. However to keep sections thin, maybe we can incorporate into benefits

        preceding list. But we already have a list; we could add a

        before list: "Eligibility requirements apply to some benefits and may depend on your job classification and length of employment. Benefits are subject to change and may be subject to specific elections, plan, or program terms." That's substantive. Let's include as a

        under Benefits heading before the

        . Similarly for Pay we have a sentence about individual compensation depending on factors; we already included that. Now ensure we don't duplicate any content. Also we need to remove duplicated lines: there may be duplicate sentences about TEKsystems etc; we removed. Now produce HTML fragment. We must not include or . Just the fragment. Let's construct:

        About the role

        Our telecommunications client is hiring an OUTSIDE PLANT TECHNICIAN to support growing business. This position is contract-to-hire, which converts permanent after completing projects successfully and meeting company performance standards. The OSP TECHNICIAN is responsible for the installation, maintenance, repair, and troubleshooting of telecommunications infrastructure including fiber optic and copper cable networks. The OSP TECHNICIAN supports the construction and operation of outside plant facilities while ensuring network reliability, safety, compliance, and quality standards. Together, the OSP TECHNICIAN is a good fit for aspiring telecommunications, data center, fiber, copper, electric, low voltage and construction professionals.

        This is a Contract position based out of Ames, IA.

        This is a fully onsite position in Ames, IA.

        Responsibilities