Staff Telecommunications Engineer

The user wants me to reformat a job posting into clean, well-structured semantic HTML. Let me analyze the content and apply the rules. Rules: - Use

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

• for lists of duties/requirements/benefits, and

  for prose - Do NOT repeat the job title as a heading - 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 - Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text - 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 Now, let me parse the job posting: Job Title: Staff Telecommunications Engineer (already shown on page, so don't repeat as heading) Contract Details: - Location: Kansas City, MO - Onsite Flexibility: Onsite - Position Type: Contract - Contract Duration: 12 months - Pay Rate: $55.00–$61.00 / Hour (USD) - Travel Requirements: Kansas City-based team with periodic travel to project sites - Work Authorization: Applicants must be authorized to work for ANY employer in the U.S. We are unable to sponsor or take over sponsorship of an employment Visa at this time. Job Summary: The Staff Telecommunications Engineer will assist in various phases of planning, site evaluations, analytical designs, report preparation, and construction documentation as part of a project team. This role will require work on a diverse portfolio of project types and clients. Key Responsibilities: (list of bullet points) Required Skills: (list of bullet points) Preferred Skills: (list of bullet points) Education Requirements: (list) Required Experience: Minimum 3 years of utility telecommunications project or related experience required. Work Environment / Physical Requirements: (list of details) Benefits: Medical, Vision, and Dental Insurance Plans; 401k Retirement Fund About the Client: (some info) Formatting Notes: (this seems like internal notes, not part of job posting) Compliance Watch: (internal notes) Special Considerations: (internal notes) About GTT: (company info) Job Number: 26-06743 Industry: Engineering I need to decide which sections to include. The posting has: - Contract Details (metadata) - could be a short

  or a section - Job Summary (About the role) - Key Responsibilities (Responsibilities) - Required Skills (Requirements/Qualifications) - Preferred Skills (Preferred Qualifications) - Education Requirements (Education) - Required Experience (Experience) - Work Environment / Physical Requirements (Work Environment) - Benefits (Benefits) - Pay Rate is mentioned, so Pay section - Schedule? Not explicitly, but "Onsite position; no remote/no hybrid" and contract duration. I should include sections only when there's real content. The posting has Pay Rate, so include Pay. Benefits are listed, so include Benefits. Schedule: contract duration and onsite, could be Schedule. But the rules say: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state Pay Rate, Benefits, and contract duration/onsite. I'll structure: -

  About the role

  with job summary -

  Contract details

  with location, type, duration, pay rate, travel, work authorization (maybe as a list or prose) -

  Responsibilities

  with list -

  Requirements

  with required skills, education, experience -

  Preferred qualifications

  with preferred skills -

  Work environment

  with details -

  Benefits

  with list -

  Pay

  with pay rate -

  Schedule

  with contract duration and onsite But the rules say "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". So I should use those exact headings where appropriate. I'll combine Required Skills, Education Requirements, Required Experience into Requirements section. Preferred Skills into Preferred qualifications. Work Environment into Work environment. Also, the "About the Client", "Formatting Notes", "Compliance Watch", "Special Considerations", "About GTT", "Job Number", "Industry" are likely boilerplate or internal notes. The user said "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Also "fold minor metadata into a short

  or drop it." Job Number is minor metadata, drop it. About GTT is company boilerplate, maybe drop. But "About the Client" might be relevant? It says "Industry: Infrastructure Engineering & Utilities Typical Roles: ..." but that's not about this job. Probably drop. I'll keep only the substantive job content. Now, let's write HTML. First, Contract details: I'll make a

  with the metadata, or a list. Since it's multiple items, maybe a

  but the rule says use
  • for any list of duties/requirements/benefits. Contract details are not duties/requirements/benefits, but could be a list. I'll use a

    with line breaks or a list. I'll do a

    for clarity. But the rule: "Use
    • for any list of duties/requirements/benefits, and

      for prose." Contract details are not duties/requirements/benefits, so maybe prose. I'll do a

      with each on new line? But HTML doesn't preserve line breaks. Could use
      but not semantic. Better to use a

      for metadata? The rule doesn't forbid using
      for other lists, but says "for any list of duties/requirements/benefits". It doesn't say exclusively. I think it's okay to use
      for contract details as a list. I'll do:

      Contract details

      • Location: Kansas City, MO
      • Onsite flexibility: Onsite
      • Position type: Contract
      • Contract duration: 12 months
      • Pay rate: $55.00–$61.00 / Hour (USD)
      • Travel requirements: Kansas City-based team with periodic travel to project sites
      • Work authorization: Applicants must be authorized to work for ANY employer in the U.S. We are unable to sponsor or take over sponsorship of an employment Visa at this time.
      But pay rate also appears in Pay section. Could duplicate? Better to have Pay section with pay rate, and contract details without pay rate? The posting has Pay Rate under Contract Details. I'll include in Contract details and also have a Pay section? The rule says include Pay section if posting states it. It does. But to avoid duplication, I could put pay rate only in Pay section. However, contract details include pay rate as part of contract. I'll include in Contract details and also have a Pay section with just the pay rate? That seems redundant. I'll put pay rate in Pay section and keep contract details without pay rate? But the contract details list includes pay rate. I'll keep it in Contract details and not create a separate Pay section? But the rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state pay rate. But the example headings include Pay. I think it's okay to have a Pay section with the pay rate. But then contract details would also have it. I'll include pay rate in Contract details and also have a Pay section? That's duplication. Better to have Pay section and not include pay rate in Contract details. But the contract details are a group. I'll make Contract details a prose paragraph with all except pay rate, and then Pay section with pay rate. Or include pay rate in both? I'll decide to have Contract details as a list including pay rate, and then a Pay section with just the pay rate? That's silly. I'll structure: Contract details (location, type, duration, travel, work auth) and then Pay section with pay rate. Schedule section with contract duration and onsite? But contract duration is in contract details. The rule says "Schedule" heading for schedule info. The posting has "Contract Duration: 12 months" and "Onsite position; no remote/no hybrid". That's schedule info. I'll create a Schedule section with that. But the rule: "Prefer a few substantive sections over many thin ones." So maybe combine Contract details, Pay, Schedule into one "Contract details" section? But the example headings include Pay and Schedule separately. I'll follow the example headings. Let's see the example: "e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So they expect separate sections. I'll create: - About the role - Contract details (maybe not in example, but it's metadata) - Responsibilities - Requirements - Preferred qualifications - Education (could be part of Requirements) - Experience (part of Requirements) - Work environment - Benefits - Pay - Schedule But that's many sections. Some are thin. Education and Experience could be under Requirements. Preferred qualifications separate. I'll do:

      About the role

      Job summary...

      Contract details

      ... (location, onsite, type, duration, travel, work auth)

      Responsibilities

      ... list of responsibilities ...

      Requirements

      ... required skills, education, experience ...

      Preferred qualifications

      ... preferred skills ...

      Work environment

      ... work environment details ...

      Benefits

      ... benefits ...

      Pay

      $55.00–$61.00 per hour (USD)

      Schedule

      Contract duration: 12 months. Onsite position; no remote or hybrid work. Kansas City-based with periodic travel to project sites.

      But note: travel is already in contract details. Could be in schedule. I'll keep travel in contract details. Now, check for duplication: Required Skills list includes many items. Education Requirements and Required Experience are separate in posting. I'll include them in Requirements as sub-lists? But the rule says use
      • for any list. I can have multiple
        under Requirements. Or combine into one list. I'll do separate lists with headings? But we only have

        for sections. Could use

        ? Not allowed. The rule says use

        for section headings. So within a section, I can use

        and

        . I'll do:

        Requirements

        Required skills:

        ... required skills ...

        Education:

        ... education ...

        Experience:

        ... experience ...
        Similarly for Preferred qualifications. Now, Work environment: list of details. Benefits: list. Pay: prose.