Network Engineer Sr
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate. Must preserve all substantive info.
We need to parse the job description.
Key sections:
- About the role: The paragraph starting "Transform technology into opportunity..." etc. Could be considered About the role.
- Responsibilities: The list under "HOW A NETWORK ENGINEER SR WILL MAKE AN IMPACT:" includes bullet points.
- Requirements/Qualifications/Skills: The "WHAT YOU’LL NEED TO SUCCEED:" includes education, experience, familiarity, abilities, etc. Could be split into Qualifications and Skills.
- Benefits: The "GDIT IS YOUR PLACE:" list includes 401K, health packages, internal mobility, professional growth, cutting-edge tech, paid vacation and holidays. Also later "Total Rewards At GDIT:" includes medical, dental, vision, 401k, flex work weeks, paid time off, disability, life, etc. So benefits content.
- Pay: The likely salary range: "$124,950 - $169,050." Also note not guarantee. Should we include? The instruction: include Pay section only if posting actually states them. It does state salary range. So include Pay.
- Schedule: "Scheduled Weekly Hours: 40 Travel Required: 10-25% Telecommuting Options: Hybrid Work Location: USA AK Joint Base Elmendorf Richardson Additional Work Locations:" Also maybe schedule includes weekly hours, travel, telecommuting. So we can include Schedule section.
- Also need to include maybe location info? Not a heading but could be in About the role or Schedule.
We must not repeat job title as heading. No Job ID etc.
We must not include boilerplate like EEO, legal, etc. Remove those.
We must preserve all substantive info; not invent or summarize away detail.
We need to output only HTML fragment, no /, no markdown fences.
We need to use for section headings, - for any list of duties/requirements/benefits, and
for prose.
We need to decide which sections to include.
Potential sections:
- About the role (prose)
- Responsibilities (list)
- Qualifications (maybe combine education, experience, abilities)
- Skills (maybe list of specific skills like LAN, networking hardware, routers, MS Visio, etc.)
- Benefits (list)
- Pay (prose)
- Schedule (list or prose)
But we must avoid thin sections. Prefer few substantive sections over many thin ones. However we need to include all substantive info. Could combine Qualifications and Skills into one "Requirements" section? But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It seems we can choose which to include. We could have sections: About the role, Responsibilities, Requirements (which includes qualifications, skills, experience), Benefits, Pay, Schedule.
But we need to follow instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must use all; we can use subset.
Thus we can produce:
About the role
Transform technology into opportunity as a Network Engineer SR with GDIT. A career in enterprise IT means connecting and enhancing the systems that matter most. At GDIT you’ll be at the forefront of innovation and play a meaningful part in improving how agencies operate! A Network Engineer SR provides the technical expertise to modernize network design and implementation supporting multiple Air Force and Space Force bases globally. The Network Engineer SR will be the technical resource supporting the survey and implementation efforts and will work closely with the base's counterparts and facilitate the planning, execution, testing and sustainment of the wired functionality of the network.
Responsibilities
- Responsible for the design and development of voice, video, radio frequency, and/or data communications networks
- Collaborates directly with GDIT team leads and AF client on planning and procedures
- Troubleshoot issues, resolves local network issues and provide knowledge support to other technicians as necessary
- Participates in network software upgrades, moderations tasks and installs
- Updates technical documentation; maintains and implements SOPs for local networks
- Works after-hours and weekends during maintenance windows on-site as needed
- Manage the operational changes to configurations of network devices, subnets, and IP address allocation for both LAN and WAN
- Support development of Network services SOPs and knowledge management articles
- Perform patching and upgrade of network device operating systems and configurations.
- Support testing of patches, upgrades, and configuration changes.
- Maintain configurations on network devices to include routers, switches, servers, and appliances.
- Support architects in design, development, and testing network changes.
Requirements
Education: Bachelor of Arts/Bachelor of Science (additional years of experience in lieu of degree can be considered)
Required Experience: 5+ years of related experience
Familiarity with network design documents such as – Site Survey Reports, Preliminary and Critical Design documentation, As-built diagrams, rack elevations and circuit connectivity matrices
Thorough understanding of Wired and general IT functions
Ability to work effectively in a virtual teaming environment.
Ability to read, analyze and interpret technical procedures, documents and governmental regulations
Strong commitment to a team environment and the ability to work collaboratively
Thorough understanding of Wireless, and RF Networking IT Functions
Experience using MS Visio or related CAD tools
Strong coordination and organizational skills
Excellent written and oral communication skills
Security Clearance Level: Secret
Required Certification: Security + CE or DoD 8140 equivalent
US Citizenship Required: Yes
Location: Onsite-Joint Base Elmendorf Richardson
But we might want to separate Skills: maybe list of specific technical skills: LAN, Networking Hardware, Network Services, Routers, etc. However those appear under Skills: Job Qualifications: Local Area Network (LAN), Networking Hardware, Network Services, Routers Certifications: None. That is a short list. Could be included in Requirements as a bullet list.
Better to have a Skills section: list LAN, Networking Hardware, Network Services, Routers, MS Visio, etc.
But we need to avoid thin sections. Could combine.
Let's think: The posting includes "Skills: Job Qualifications: Local Area Network (LAN), Networking Hardware, Network Services, Routers Certifications: None Experience: 5 + years of related experience US Citizenship Required: Yes". That seems like a metadata block. We already captured experience, citizenship. The skills list could be a separate under Skills heading.
But we already have many items in Requirements; maybe we can split: Qualifications (education, experience, clearance, certification, citizenship) and Skills (technical skills). However the instruction says prefer few substantive sections over many thin ones. Having both Qualifications and Skills may be okay if each has substantive content.
Let's decide:
Sections:
- About the role
- Responsibilities
- Qualifications (education, experience, clearance, certification, citizenship)
- Skills (LAN, Networking Hardware, Network Services, Routers, MS Visio, etc.)
- Benefits
- Pay
- Schedule
That's 7 sections, each with substantive content. Might be okay.
But we need to ensure we don't create sections with filler like "commensurate with experience". We have real content.
Now we need to extract Benefits: from "GDIT IS YOUR PLACE:" list and later "Total Rewards At GDIT:" details. Combine.
Benefits list:
- 401K with company match
- Comprehensive health and wellness packages
- Internal mobility team dedicated to helping you own your career
- Professional growth opportunities including paid education and certifications
- Cutting-edge technology you can learn from
- Rest and recharge with paid vacation and holidays
- Medical plan options (some with HSAs)
- Dental plan options
- Vision plan
- 401(k) plan offering ability to contribute both pre and post-tax dollars up to IRS annual limits and receive a company match (already mentioned)
- Flex work weeks where possible
- Paid time off plans: vacation, sick and personal time, holidays, paid parental, military, bereavement and jury duty leave
- Short and long-term disability benefits
- Life, accidental death and dismemberment, personal accident, critical illness and business travel and accident insurance
We should not duplicate 401k mention; but we can keep both.
We need to preserve all substantive info; we can combine into a single with items.
Pay: The likely salary range: "$124,950 - $169,050." Also note not guarantee. We'll include that as prose.
Schedule: "Scheduled Weekly Hours: 40 Travel Required: 10-25% Telecommuting Options: Hybrid Work Location: USA AK Joint Base Elmendorf Richardson Additional Work Locations:" Also maybe location already in Qualifications; but schedule includes weekly hours, travel, telecommuting. We'll include as list.
Now we need to ensure we don't repeat location; but it's okay.
Now produce HTML.
We must not include any markdown fences. Just raw HTML.
Let's craft.
Check for any boilerplate: We removed EEO, legal, identity verification, etc. Also removed "About Our Work", "Equal Opportunity Employer", etc.
We kept "GDIT IS YOUR PLACE:" benefits.
We kept "Total Rewards At GDIT:" details.
We kept "Our Identity Verification Process:"? That's boilerplate/legal; we should remove. Indeed it's about identity verification, which is likely boilerplate; we should remove per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So remove that.
We also removed "Join our Talent Community..." etc.
Now produce final HTML.
Let's write:
About the role
Transform technology into opportunity as a Network Engineer SR with GDIT. A career in enterprise IT means connecting and enhancing the systems that matter most. At GDIT you’ll be at the forefront of innovation and play a meaningful part in improving how agencies operate! A Network Engineer SR provides the technical expertise to modernize network design and implementation supporting multiple Air Force and Space Force bases globally. The Network Engineer SR will be the technical resource supporting the survey and implementation efforts and will work closely with the base's counterparts and facilitate the planning, execution, testing and sustainment of the wired functionality of the network.
Responsibilities
- Responsible for the design and development of voice, video, radio frequency, and/or data communications networks
- Collaborates directly with GDIT team leads and AF client on planning and procedures
- Troubleshoot issues, resolves local network issues and provide knowledge support to other technicians as necessary
- Participates in network software upgrades, moderations tasks and installs
- Updates technical documentation; maintains and implements SOPs for local networks
- Works after-hours and weekends during maintenance windows on-site as needed
- Manage the operational changes to configurations of network devices, subnets, and IP address allocation for both LAN and WAN
- Support development of Network services SOPs and knowledge management articles
- Perform patching and upgrade of network device operating systems and configurations.
- Support testing of patches
- for any list of duties/requirements/benefits, and
for prose. We need to decide which sections to include. Potential sections: - About the role (prose) - Responsibilities (list) - Qualifications (maybe combine education, experience, abilities) - Skills (maybe list of specific skills like LAN, networking hardware, routers, MS Visio, etc.) - Benefits (list) - Pay (prose) - Schedule (list or prose) But we must avoid thin sections. Prefer few substantive sections over many thin ones. However we need to include all substantive info. Could combine Qualifications and Skills into one "Requirements" section? But the instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It seems we can choose which to include. We could have sections: About the role, Responsibilities, Requirements (which includes qualifications, skills, experience), Benefits, Pay, Schedule. But we need to follow instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we must use all; we can use subset. Thus we can produce:
About the role
Transform technology into opportunity as a Network Engineer SR with GDIT. A career in enterprise IT means connecting and enhancing the systems that matter most. At GDIT you’ll be at the forefront of innovation and play a meaningful part in improving how agencies operate! A Network Engineer SR provides the technical expertise to modernize network design and implementation supporting multiple Air Force and Space Force bases globally. The Network Engineer SR will be the technical resource supporting the survey and implementation efforts and will work closely with the base's counterparts and facilitate the planning, execution, testing and sustainment of the wired functionality of the network.
Responsibilities
- Responsible for the design and development of voice, video, radio frequency, and/or data communications networks
- Collaborates directly with GDIT team leads and AF client on planning and procedures
- Troubleshoot issues, resolves local network issues and provide knowledge support to other technicians as necessary
- Participates in network software upgrades, moderations tasks and installs
- Updates technical documentation; maintains and implements SOPs for local networks
- Works after-hours and weekends during maintenance windows on-site as needed
- Manage the operational changes to configurations of network devices, subnets, and IP address allocation for both LAN and WAN
- Support development of Network services SOPs and knowledge management articles
- Perform patching and upgrade of network device operating systems and configurations.
- Support testing of patches, upgrades, and configuration changes.
- Maintain configurations on network devices to include routers, switches, servers, and appliances.
- Support architects in design, development, and testing network changes.
Requirements
Education: Bachelor of Arts/Bachelor of Science (additional years of experience in lieu of degree can be considered)
Required Experience: 5+ years of related experience
Familiarity with network design documents such as – Site Survey Reports, Preliminary and Critical Design documentation, As-built diagrams, rack elevations and circuit connectivity matrices
Thorough understanding of Wired and general IT functions
Ability to work effectively in a virtual teaming environment.
Ability to read, analyze and interpret technical procedures, documents and governmental regulations
Strong commitment to a team environment and the ability to work collaboratively
Thorough understanding of Wireless, and RF Networking IT Functions
Experience using MS Visio or related CAD tools
Strong coordination and organizational skills
Excellent written and oral communication skills
Security Clearance Level: Secret
Required Certification: Security + CE or DoD 8140 equivalent
US Citizenship Required: Yes
Location: Onsite-Joint Base Elmendorf Richardson
But we might want to separate Skills: maybe list of specific technical skills: LAN, Networking Hardware, Network Services, Routers, etc. However those appear under Skills: Job Qualifications: Local Area Network (LAN), Networking Hardware, Network Services, Routers Certifications: None. That is a short list. Could be included in Requirements as a bullet list. Better to have a Skills section: list LAN, Networking Hardware, Network Services, Routers, MS Visio, etc. But we need to avoid thin sections. Could combine. Let's think: The posting includes "Skills: Job Qualifications: Local Area Network (LAN), Networking Hardware, Network Services, Routers Certifications: None Experience: 5 + years of related experience US Citizenship Required: Yes". That seems like a metadata block. We already captured experience, citizenship. The skills list could be a separate- under Skills heading.
But we already have many items in Requirements; maybe we can split: Qualifications (education, experience, clearance, certification, citizenship) and Skills (technical skills). However the instruction says prefer few substantive sections over many thin ones. Having both Qualifications and Skills may be okay if each has substantive content.
Let's decide:
Sections:
- About the role
- Responsibilities
- Qualifications (education, experience, clearance, certification, citizenship)
- Skills (LAN, Networking Hardware, Network Services, Routers, MS Visio, etc.)
- Benefits
- Pay
- Schedule
That's 7 sections, each with substantive content. Might be okay.
But we need to ensure we don't create sections with filler like "commensurate with experience". We have real content.
Now we need to extract Benefits: from "GDIT IS YOUR PLACE:" list and later "Total Rewards At GDIT:" details. Combine.
Benefits list:
- 401K with company match
- Comprehensive health and wellness packages
- Internal mobility team dedicated to helping you own your career
- Professional growth opportunities including paid education and certifications
- Cutting-edge technology you can learn from
- Rest and recharge with paid vacation and holidays
- Medical plan options (some with HSAs)
- Dental plan options
- Vision plan
- 401(k) plan offering ability to contribute both pre and post-tax dollars up to IRS annual limits and receive a company match (already mentioned)
- Flex work weeks where possible
- Paid time off plans: vacation, sick and personal time, holidays, paid parental, military, bereavement and jury duty leave
- Short and long-term disability benefits
- Life, accidental death and dismemberment, personal accident, critical illness and business travel and accident insurance
We should not duplicate 401k mention; but we can keep both.
We need to preserve all substantive info; we can combine into a single
- Responsible for the design and development of voice, video, radio frequency, and/or data communications networks
- Collaborates directly with GDIT team leads and AF client on planning and procedures
- Troubleshoot issues, resolves local network issues and provide knowledge support to other technicians as necessary
- Participates in network software upgrades, moderations tasks and installs
- Updates technical documentation; maintains and implements SOPs for local networks
- Works after-hours and weekends during maintenance windows on-site as needed
- Manage the operational changes to configurations of network devices, subnets, and IP address allocation for both LAN and WAN
- Support development of Network services SOPs and knowledge management articles
- Perform patching and upgrade of network device operating systems and configurations.
- Support testing of patches
- with items.
Pay: The likely salary range: "$124,950 - $169,050." Also note not guarantee. We'll include that as prose.
Schedule: "Scheduled Weekly Hours: 40 Travel Required: 10-25% Telecommuting Options: Hybrid Work Location: USA AK Joint Base Elmendorf Richardson Additional Work Locations:" Also maybe location already in Qualifications; but schedule includes weekly hours, travel, telecommuting. We'll include as list.
Now we need to ensure we don't repeat location; but it's okay.
Now produce HTML.
We must not include any markdown fences. Just raw HTML.
Let's craft.
Check for any boilerplate: We removed EEO, legal, identity verification, etc. Also removed "About Our Work", "Equal Opportunity Employer", etc.
We kept "GDIT IS YOUR PLACE:" benefits.
We kept "Total Rewards At GDIT:" details.
We kept "Our Identity Verification Process:"? That's boilerplate/legal; we should remove. Indeed it's about identity verification, which is likely boilerplate; we should remove per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So remove that.
We also removed "Join our Talent Community..." etc.
Now produce final HTML.
Let's write:
About the role
Transform technology into opportunity as a Network Engineer SR with GDIT. A career in enterprise IT means connecting and enhancing the systems that matter most. At GDIT you’ll be at the forefront of innovation and play a meaningful part in improving how agencies operate! A Network Engineer SR provides the technical expertise to modernize network design and implementation supporting multiple Air Force and Space Force bases globally. The Network Engineer SR will be the technical resource supporting the survey and implementation efforts and will work closely with the base's counterparts and facilitate the planning, execution, testing and sustainment of the wired functionality of the network.
Responsibilities