​Network Technician​

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Opportunity Information Management Group (IMG) seeking Network Technician. It includes description: on-site position, professional, etc. That could be "About the role". Responsibilities: maybe not explicit list; they mention developing, implementing, maintaining effective workflow solutions, etc. Could be responsibilities. Qualifications: list of qualifications: Active Secret or L clearance, 5+ years experience, qualified to install etc. Also knowledge of standards, proficient with Fluke testers, writing and speaking clearly. Preferred qualifications: Active Top Secret or Q clearance. Skills: maybe technical skills listed. Benefits: listed. Pay: not mentioned. Schedule: not mentioned (on-site but not schedule). So we should not include Pay or Schedule sections. We need to use

for each section heading. Use

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

  for prose. We must not repeat job title as heading. Do not include Job ID etc. Remove boilerplate: EEO statement, etc. Also remove navigation etc. We need to preserve all substantive information. Let's extract content: - Intro: "Opportunity Information Management Group (IMG) is seeking a highly motivated Network Technician to join our team in West Mifflin, PA. This on-site position requires a professional who brings strong technical expertise, exceptional attention to detail, and a collaborative approach to problem-solving. At IMG, our success is driven by our people. We foster a collaborative environment where employees are empowered to grow professionally, contribute meaningfully, and make a lasting impact on the missions we support. The successful candidate will play a key role in developing, implementing, and maintaining effective workflow solutions that enhance operational efficiency, support mission objectives, and contribute to overall organizational success." That could be About the role (or maybe a summary). We'll put under

  About the role

  with

  containing that paragraph. - Responsibilities: The sentence about developing, implementing, maintaining effective workflow solutions could be considered responsibilities. Could also list as bullet list? It's a single sentence. Could still be

  . But we can also treat as responsibilities bullet list: maybe break into duties: developing workflow solutions, implementing workflow solutions, maintaining workflow solutions, enhancing operational efficiency, supporting mission objectives, contributing to organizational success. However we must not invent detail; we can rephrase but must preserve meaning. Safer to keep as prose. But we need to use

  • for any list of duties/requirements/benefits. If we have a list, we must use ul. If not list, we can use p. We have qualifications list: many items. That should be a ul. We have benefits list: also ul. We have preferred qualifications: maybe separate? Could be under Qualifications as well, but we could have a separate section "Preferred Qualifications" but not in allowed headings list (only Qualifications). The allowed headings list includes Qualifications, Skills, Benefits, Pay, Schedule, About the role, Responsibilities, Requirements. There's no "Preferred Qualifications". We could incorporate preferred qualifications into Qualifications section (maybe as a sub-list). Or we could put under Skills? Probably better to add under Qualifications as a separate bullet list with note "Preferred". But we must not invent headings not allowed. So we will include preferred qualifications within Qualifications section, maybe as a separate
    with a note? Could add a

    preceding: "Preferred qualifications:" then ul. Skills: The posting mentions "Proficient with Fluke DSX-8000 copper/fiber tester", "Proficient with Fluke OFP-100-QI OptiFiber Pro Optical Time Domain Reflectometer", "Writing and speaking clearly and concisely about technical topics". Also "Qualified to install, terminate, and conduct certification testing of Category 3, 5e, 6, and 6a unshielded twisted pair (UTP) cable, multimode and single-mode fiber cable". Also "Knowledge in the application of the following structured cable standards and codes: ..." Those could be considered skills. We could create a Skills section with those items as bullet list. Requirements: Could be similar to Qualifications? The posting uses "Qualifications" heading already. We could treat Requirements as same as Qualifications? But we need to decide which sections to include. The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include multiple of those if content exists. We have content for About the role, Responsibilities, Qualifications, Skills, Benefits. Possibly Requirements could be same as Qualifications but we might not need duplicate. Better to include Requirements as a section that lists the mandatory requirements (Active Secret clearance, 5+ years experience, etc.) and Qualifications could list both mandatory and preferred? But the posting already uses "Qualifications" heading for the list of mandatory qualifications and then "Preferred Qualifications". So we could map: Requirements = mandatory qualifications; Qualifications = maybe also includes preferred? But to avoid duplication, we could put mandatory under Requirements and preferred under Qualifications? However the instructions say "Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid using both Requirements and Qualifications if content distinct. We'll try to split: Requirements: mandatory qualifications (Active Secret or L clearance, 5+ years experience, qualified to install..., knowledge of standards, proficient with Fluke testers, writing and speaking clearly). Qualifications: maybe include preferred qualifications (Active Top Secret or Q clearance) plus maybe other qualifications like experience? But that would duplicate. Better to treat Qualifications as the list of qualifications (including both mandatory and preferred) and maybe not have Requirements separate. However we need to follow instruction: "Prefer a few substantive sections over many thin ones." So we should avoid thin sections. Having both Requirements and Qualifications might be thin if they overlap. So better to have one section for qualifications (maybe called Qualifications) and maybe not include Requirements. But we need to decide which heading to use. The posting uses "Qualifications" as a heading. So we will use

    Qualifications

    for the list (including mandatory and preferred). Then we can have Responsibilities separate. About the role separate. Benefits separate. Skills maybe separate? But the qualifications list already includes many technical skills; we could treat those as skills. However we could also have a Skills section for the specific technical proficiencies (Fluke testers, standards knowledge, cabling). But that may be thin. Let's see: The qualifications list includes: Active Secret or L security clearance, 5+ years’ experience in cabling or network technician work, Qualified to install, terminate, and conduct certification testing of Category 3, 5e, 6, and 6a UTP cable, multimode and single-mode fiber cable, Knowledge in the application of the following structured cable standards and codes: ANSI/TIA/EIA 568-B, ANSI/TIA/EIA 569, ANSI/TIA/EIA 606, ANSI/TIA/EIA 607, NFPA 70, Proficient with Fluke DSX-8000 copper/fiber tester, Proficient with Fluke OFP-100-QI OptiFiber Pro Optical Time Domain Reflectometer, Writing and speaking clearly and concisely about technical topics. That's a mix of experience, clearance, technical skills, knowledge. Could be all under Qualifications. Then Skills section might be redundant. However we could still have Skills section for the specific technical proficiencies (Fluke testers, standards knowledge, cabling). But that would split the list. Might be okay but risk of thin sections. The instruction: "Prefer a few substantive sections over many thin ones." So better to have fewer sections. Let's combine everything into Qualifications and maybe Skills not needed. But we need to include Benefits definitely. About the role and Responsibilities also. Thus sections: About the role, Responsibilities, Qualifications, Benefits. Check if any content for Responsibilities beyond the earlier sentence. The posting also says: "The successful candidate will play a key role in developing, implementing, and maintaining effective workflow solutions that enhance operational efficiency, support mission objectives, and contribute to overall organizational success." That's basically responsibilities. Could also include "developing, implementing, and maintaining effective workflow solutions". That's it. We could also include "collaborative approach to problem-solving" as part of About the role. Thus we will output:

    About the role

    Opportunity Information Management Group (IMG) is seeking a highly motivated Network Technician to join our team in West Mifflin, PA. This on-site position requires a professional who brings strong technical expertise, exceptional attention to detail, and a collaborative approach to problem-solving. At IMG, our success is driven by our people. We foster a collaborative environment where employees are empowered to grow professionally, contribute meaningfully, and make a lasting impact on the missions we support.

    Responsibilities

    The successful candidate will play a key role in developing, implementing, and maintaining effective workflow solutions that enhance operational efficiency, support mission objectives, and contribute to overall organizational success.

    Qualifications

    • Active Secret or L security clearance
    • 5+ years’ experience in cabling or network technician work
    • Qualified to install, terminate, and conduct certification testing of Category 3, 5e, 6, and 6a unshielded twisted pair (UTP) cable, multimode and single-mode fiber cable
    • Knowledge in the application of the following structured cable standards and codes: ANSI/TIA/EIA 568-B, ANSI/TIA/EIA 569, ANSI/TIA/EIA 606, ANSI/TIA/EIA 607, NFPA 70
    • Proficient with Fluke DSX-8000 copper/fiber tester
    • Proficient with Fluke OFP-100-QI OptiFiber Pro Optical Time Domain Reflectometer
    • Writing and speaking clearly and concisely about technical topics
    • Preferred: Active Top Secret or Q security clearance

    Benefits

    • Medical, Dental, Vision, and Life Insurance
    • Short-Term and Long-Term Disability Insurance
    • 401(k) Retirement Plan with Generous Company Match
    • Health Savings Account (HSA)
    • Supplemental Benefits
    • Paid Time Off and Paid Federal Holidays
    • Professional Development and Training Assistance
    We must not include any boilerplate like EEO statement. We removed that. Check if any other substantive content: "About IMG: Founded in 1987, IMG is a leading small business that exemplifies competence, integrity and follow-through. We consistently provide customer focused professional services, which ensures our company is recognized for continually exceeding expectations. We believe that at the core of our success stand our people. Our people have provided professional services in the Information Technology field for our customers with a commitment to customer satisfaction for over 35 years." That's about the company; could be part of About the role or maybe a separate section "About IMG". But not in allowed headings. Could incorporate into About the role paragraph. We can add a second paragraph under About the role describing IMG. That would preserve all substantive info. Similarly "Why Join IMG? Join a team that has built a reputation for excellence, integrity, and customer commitment. At IMG, you'll have the opportunity to contribute to meaningful government missions while growing your career within a supportive and collaborative environment