Jobs · Information Technology · Kentucky

Outside Plant Engineer I/II

Uniti Group Inc. · Ashland, KY · 1 mo ago
Information TechnologyFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Let's parse the posting. First, there is a paragraph about Kinetic (company description). Then "About This Role" heading. Then description: "Kinetic’s team of Outside Plant Engineers connects consumer and small business partners to our leading telecommunications products across the United States. In this role you will work to create meaningful connections with customers and build long-term relationships. By analyzing a variety of data, you will solve complex problems for our business and residential customers utilizing copper cable, fiber cable, and electronics." Then "What You’ll Do" list: bullet points. Then "Do you Have?" list: bullet points. Then "Even Better" list: bullet points. Then "Minimum Requirements" paragraph. Then "This is a safety sensitive position." etc. Then driver's license etc. Then physical tasks etc. Then equipment used etc. Then exposures etc. Then "Our Benefits" list. Then EEO etc. Then "Actual base pay for this job will depend on the candidate's primary work location and other factors, such as relevant skills and experience." That's pay info but vague. It says depends on location etc. Not a specific number. According to rule: 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. The pay statement is vague but it's still stating that pay depends on location etc. It's not a specific number but it's still content. However rule says avoid filler like "varies". The phrase "Actual base pay for this job will depend on the candidate's primary work location and other factors, such as relevant skills and experience." That is essentially "varies". Likely considered filler. So we should not create Pay section. Schedule: there is a line: "Conduct 70% of work in the field and 30% in the office on average (varies per market)". That's schedule info but includes "(varies per market)". That's vague. According to rule, we should not create Schedule section unless posting actually states them. It does state a ratio but with varies. Might be considered filler. Safer to omit Schedule section. Benefits: we have "Our Benefits Medical, Dental, Vision Insurance Plans 401K Plan Health & Flexible Savings Account Life and AD&D, Spousal Life, Child Life Insurance Plans Educational Assistance Plan". That's specific enough. So include Benefits section. Now we need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Possibly also "Qualifications" separate from Requirements? The posting has Minimum Requirements and also "Do you Have?" (skills) and "Even Better" (preferred qualifications). We need to map. We should not repeat job title as heading. Already not. We need to use

for section headings. We need to use
  • for any list of duties/requirements/benefits, and

    for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO paragraph, the notice to non-US citizens, notice to applicants, etc. Also remove duplicated lines like "Types of Driver’s License Required: Valid Driver’s License" appears twice; we should keep only once? Probably keep one instance but not duplicate. Also remove the repeated "Types of Driver’s License Required: Driver’s License". We'll keep one. Also remove the line "This is a safety sensitive position." Might be considered substantive? It's a statement about safety sensitivity. Could be part of Requirements? Might be considered a requirement. We'll keep as a

    maybe under Requirements. We need to keep the physical tasks details etc. That's substantive. Should we include them? They are part of job description. Could be under Requirements or Qualifications. We'll include them as a list under Requirements maybe. We need to decide sections: - About the role: could be the paragraph after "About This Role". That's prose. - Responsibilities: the "What You’ll Do" list. - Requirements: Minimum Requirements paragraph plus maybe safety sensitive statement, driver's license, physical tasks, equipment used, exposures. Could be a mix. - Qualifications: maybe "Do you Have?" list (desired skills). Could be Skills. - Skills: "Even Better" list (preferred qualifications). Could be Skills as well. But we have both Skills and Qualifications sections possible. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Qualifications and Skills. We need to decide what goes where. Typically, Qualifications = minimum qualifications (education/experience). Skills = desired skills/knowledge. But we have Minimum Requirements separate. So we can put Minimum Requirements under Qualifications. Then "Do you Have?" under Skills (required skills). Then "Even Better" under maybe also Skills? Or could be Qualifications? But we already have Qualifications. Perhaps we put "Even Better" under Skills as preferred skills. Thus: - About the role: paragraph. - Responsibilities: "What You’ll Do" list. - Qualifications: Minimum Requirements paragraph + safety sensitive statement + driver's license + physical tasks + equipment used + exposures? Might be too much. But we can keep them as part of Qualifications. - Skills: "Do you Have?" list (required skills) and "Even Better" list (preferred skills). Could combine into one list? Better to separate: maybe two subsections? But we only have one Skills heading. Could combine both lists under Skills heading, maybe separate with

    indicating required and preferred. But we must not invent headings. We could put both as separate

      under Skills heading, with a

      preceding each to label. That's acceptable. - Benefits: list. We must not include Pay or Schedule. Now we need to strip boilerplate: remove the EEO paragraph, notice to non-US citizens, notice to applicants, etc. Also remove duplicated lines like "Types of Driver’s License Required: Valid Driver’s License" appears twice; keep one. Also remove the line "Additional information about Kinetic is available at www.GoKinetic.com _________________________________________________________". That's fluff; we can drop. Also remove the line "Kinetic, a business unit of Uniti (NASDAQ: UNIT), is a premier insurgent provider of multi-gigabit fiber internet, whole-home Wi-Fi, internet security, and voice services in 1,400 markets across 18 states in across the U.S." That's company description; maybe we can keep as part of About the role? But the About the role section should be about the role, not company. However we could include a brief company overview under About the role? The instruction: "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So About the role heading likely expects description of the role. The initial company description could be considered boilerplate? It's not about the role. Might be considered not needed. But we could incorporate it into About the role as context? The rule says preserve ALL substantive information; do NOT invent or summarize away detail. The company description is substantive about the company, not the role. But the heading is About the role, not About the company. However we could still put it there as it's still relevant to the role? Might be okay. But maybe better to treat the initial paragraph as part of About the role (since it's the first content after the title). The posting includes "About This Role" heading then description. So we should use that description as About the role. The preceding company description could be considered boilerplate? It's not navigation/legal/EEO, but it's still about the company. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. It does not explicitly say to remove company description. So we should keep it. But where? Could be a preamble before any heading? The instruction says output ONLY the HTML fragment — no /. It didn't say we must have headings covering all content. We could have a

      for the company description before the first heading. That's allowed. Then we have

      About the role

      with the role description. Thus structure:

      Kinetic, a business unit of Uniti (NASDAQ: UNIT), is a premier insurgent provider of multi-gigabit fiber internet, whole-home Wi-Fi, internet security, and voice services in 1,400 markets across 18 states in across the U.S. Additional information about Kinetic is available at www.GoKinetic.com

      Then

      About the role

      with the paragraph after "About This Role": "Kinetic’s team of Outside Plant Engineers connects consumer and small business partners to our leading telecommunications products across the United States. In this role you will work to create meaningful connections with customers and build long-term relationships. By analyzing a variety of data, you will solve complex problems for our business and residential customers utilizing copper cable, fiber cable, and electronics." Then

      Responsibilities

      with
        of the "What You’ll Do" items. Then

        Qualifications

        with content: Minimum Requirements paragraph, safety sensitive statement, driver's license, physical tasks, equipment used, exposures. We'll need to format as

        for prose and maybe

          for lists? The physical tasks etc are a list of items with percentages. Could be represented as
          • each item. But they are not a simple list; they have categories. We'll keep as

            maybe preserving the text. However rule: Use

            • for any list of duties/requirements/benefits. The physical tasks is a list of requirements; we should use
              • . Similarly equipment used and exposures could be lists. We'll need to decide how to chunk. Let's extract the Minimum Requirements paragraph: "College degree in Engineering or a related field and 2-4 years professional level experience; or 6+ years professional level related Engineering/Technical experience; or an equivalent combination of education and professional level related Engineering/Technical experience required." Then "This is a safety sensitive position." Then "Types of Driver’s License Required: Valid Driver’s License" Then physical tasks list: many items with percentages. Then "Equipment Used in Job Performance/Working Environment: Computer, Printer, Fax, Telephone, Basic Office Supplies, Copier, Vehicle" Then "Exposures to: Cold: Occasionally: 0-33% | Heat: Occasionally: 0-33% | Dampness: Occasionally: 0-33% | Heights: Occasionally: 0-33% | Vibration: Occasionally: 0-33% | Skin Irritants: Occasionally: 0-33% | Lung Irritants: Dust: Occasionally: 0-33% | Fumes/Gases: Occasionally: 0-33%" We also have duplicated "Types of Driver’s License Required: Driver’s License" later; we will keep only one. Now for Skills section: "Do you Have?" list items: - Strong and effective technical communication skills, both verbally and written - Knowledge of Microsoft Office tools including Excel, Word, and Outlook - Ability to be a self-starter, able to work with little guidance - Ability to work in a self-directed work group, work easily with others and be a team player - Ability to analyze problems and priorities and make decisions - A love of solving problems and building solutions - Ability to travel overnight and out of the market

Similar jobs