Secret Cleared Optical Networking Engineer- Scott AFB

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. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, equal opportunity, etc. Also remove application instructions (none present). Must not include placeholder text like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes salary range: $115,000 to $150,000. So we can include Pay section. Benefits: they say "We offer excellent benefits and compensation packages." That's vague but they mention benefits. However they didn't list specific benefits. The rule: never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "We offer excellent benefits and compensation packages." is vague but not a placeholder like "not specified". It's a statement that they offer benefits, but no specifics. Is that considered filler? It's not a list; it's a vague statement. The rule says "never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD")". This statement is not exactly those examples, but it's still vague. However they said "Prefer a few substantive sections over many thin ones." Might be better to omit Benefits section because no specific benefits listed. Pay section we have specific range, so include. Schedule: they said full time position, onsite daily. That's schedule info: full-time, onsite daily. Could include Schedule section with that info. It's substantive. Now sections: About the role (intro paragraph), Responsibilities (list of duties), Requirements (maybe combine with Qualifications/Skills). The posting includes Required Skills list and Nice To Haves list. We could split: Requirements (required skills) and Qualifications (education, clearance, experience). Skills could be separate but we might combine. The instruction: Use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can include those that have content. We need to preserve all substantive information. Let's extract: Intro: "Our client, a leader in telecommunications and networking technology, is seeking a Network Solutions Engineer for a full time position. They will be working onsite daily to support a federal customer at Scott AFB in Illinois. This individual will serve as an onsite technical SME supporting the implementation, testing, and modernization of optical network infrastructure. The engineer will work hands-on with Ciena equipment, troubleshoot network issues, perform service turn-ups and testing, and support integration with the customer’s existing network environment." That's about the role. Responsibilities: likely the same as above? Could list: supporting implementation, testing, modernization of optical network infrastructure; work hands-on with Ciena equipment; troubleshoot network issues; perform service turn-ups and testing; support integration with customer’s existing network environment. Also maybe: commissioning, testing, troubleshooting, turning up network services (from required skills). But those are skills. We'll list responsibilities as the duties described. Requirements: Active Secret Security Clearance; Ability to work onsite daily at Scott AFB; 10+ years of telecommunications/network engineering experience; Hands-on experience with Ciena networking equipment; Strong experience with DWDM, SONET, ROADM/nOADM, and optical networking; Experience with Ethernet architecture, provisioning, and implementation; Knowledge of IP/MPLS and Layer 2/Layer 3 networking protocols; Experience commissioning, testing, troubleshooting, and turning up network services; Knowledge of fiber optics, including fiber characterization and OTDR; Experience reading network diagrams, cabling guides, and signal flow diagrams; Familiarity with Network Management Systems (NMS) such as Ciena MCP/Navigator; Bachelor’s degree in Telecommunications, Networking, or related field, or equivalent experience; Ability to travel up to 25%. Qualifications: maybe education and clearance already in requirements. Could separate: Bachelor’s degree, Active Secret Security Clearance. But we already have those. Might combine. Skills: maybe the technical skills list: DWDM, SONET, ROADM/nOADM, optical networking, Ethernet architecture, provisioning, IP/MPLS, Layer 2/Layer 3, fiber optics, OTDR, network diagrams, NMS, etc. But that overlaps with requirements. To avoid duplication, we could treat Requirements as the list of required qualifications (including experience, clearance, education) and Skills as the technical competencies. However the instruction says preserve all substantive information; we can duplicate? Better to split logically: Requirements: clearance, onsite, travel, years experience, degree. Skills: technical hands-on etc. Qualifications: maybe education and clearance again? Might be redundant. Let's think: The posting has "Required Skills" bullet list and then "Nice To Haves". So we can map Required Skills to Skills section. And we can have Requirements section for things like clearance, onsite, travel, years experience, degree. Qualifications could be education and clearance? But clearance already in requirements. Could put Qualifications for degree and equivalent experience. But we might just have Requirements and Skills, and omit Qualifications to avoid thin sections. The instruction: Prefer a few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Skills, Pay, Schedule. That's six sections. Benefits omitted because vague. Let's see if we have enough content for each. About the role: intro paragraph. Responsibilities: list of duties (implementation, testing, modernization; hands-on Ciena; troubleshoot; service turn-ups/testing; support integration). Could also include commissioning, testing, troubleshooting, turning up network services (but that's similar). We'll keep. Requirements: Active Secret Security Clearance; Ability to work onsite daily at Scott AFB; Ability to travel up to 25%; 10+ years of telecommunications/network engineering experience; Bachelor’s degree in Telecommunications, Networking, or related field, or equivalent experience. Skills: Hands-on experience with Ciena networking equipment; Strong experience with DWDM, SONET, ROADM/nOADM, and optical networking; Experience with Ethernet architecture, provisioning, and implementation; Knowledge of IP/MPLS and Layer 2/Layer 3 networking protocols; Experience commissioning, testing, troubleshooting, and turning up network services; Knowledge of fiber optics, including fiber characterization and OTDR; Experience reading network diagrams, cabling guides, and signal flow diagrams; Familiarity with Network Management Systems (NMS) such as Ciena MCP/Navigator. Pay: $115,000 to $150,000. Schedule: Full-time position; onsite daily at Scott AFB. We should not repeat "Ability to work onsite daily at Scott AFB" in both Requirements and Schedule; but Schedule can just say "Full-time, onsite daily". Requirements can mention ability to work onsite daily as a requirement. It's okay to have some overlap but maybe we can avoid duplication: In Requirements we can list clearance, travel, years experience, degree. In Schedule we list full-time, onsite daily. The requirement to work onsite daily is also a schedule aspect; but we can keep it in Schedule only and not in Requirements. However the posting says "Ability to work onsite daily at Scott AFB" as a requirement. It's both a requirement and schedule. We could keep it in Requirements and Schedule just says "Full-time". But schedule section should have substantive content; we can say "Full-time position". That's enough. Let's decide: Requirements: Active Secret Security Clearance; Ability to work onsite daily at Scott AFB; Ability to travel up to 25%; 10+ years of telecommunications/network engineering experience; Bachelor’s degree in Telecommunications, Networking, or related field, or equivalent experience. Schedule: Full-time position. That avoids duplication. Now Benefits: we omit because no specific benefits. Now ensure we don't include boilerplate like "ClearBridge Technology Group is an Equal Opportunity Employer." Remove. Now output HTML fragment: use

for each section heading, then content:

for prose,

• for lists. We need to preserve all substantive information: include Nice To Haves? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Nice To Haves are substantive; we should include them somewhere. Could be under a section like "Preferred Qualifications" or "Nice To Haves". But we only have allowed headings list; we could add a section "Preferred Qualifications" but not in list. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should stick to those headings. However we could incorporate Nice To Haves into Requirements or Skills as "Preferred" but that would lose detail. Better to add a section "Preferred Qualifications" maybe using

  as well, even though not in the example list. The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies examples, not exclusive. So we can add other headings if needed. But they also say "Prefer a few substantive sections over many thin ones." Adding a Preferred Qualifications section may be okay if it has substantive content. The Nice To Haves list is substantive. Let's include a section "Preferred Qualifications" (or "Nice To Haves") with that list. We must not repeat job title as heading. We'll not. Now compile: About the role: paragraph. Responsibilities: list. Requirements: list. Skills: list. Preferred Qualifications: list (Nice To Haves). Pay: paragraph with salary range. Schedule: paragraph. Now ensure we don't include any filler like "commensurate with experience". Not present. Now produce HTML. Let's write:

  About the role

  Our client, a leader in telecommunications and networking technology, is seeking a Network Solutions Engineer for a full time position. They will be working onsite daily to support a federal customer at Scott AFB in Illinois. This individual will serve as an onsite technical SME supporting the implementation, testing, and modernization of optical network infrastructure. The engineer will work hands-on with Ciena equipment, troubleshoot network issues, perform service turn-ups and testing, and support integration with the customer’s existing network environment.

  Responsibilities

  • Support implementation, testing, and modernization of optical network infrastructure
  • Work hands-on with Ciena equipment
  • Troubleshoot network issues
  • Perform service turn-ups and testing
  • Support integration with the customer’s existing network environment

  Requirements

  • Active Secret Security Clearance
  • Ability to work onsite daily at Scott AFB
  • Ability to travel up to 25%
  • 10+ years of telecommunications/network engineering experience
  • Bachelor’s degree in Telecommunications, Networking, or related field, or equivalent experience

  Skills

  • Hands-on experience with Ciena networking equipment
  • Strong experience with DWDM, SONET, ROADM/nOADM, and optical networking
  • Experience with Ethernet architecture, provisioning, and implementation
  • Knowledge of IP/MPLS and Layer 2/Layer 3 networking protocols
  • Experience commissioning, testing, troubleshooting, and turning