Network Engineer - Mid-SR, TS/SCI with FSP - $150K-$270K + 15% 401k
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to include sections only when posting has real specific content. We have benefits listed: 100% company-paid medical, dental, vision; disability and life insurance; 15% 401(k) company contribution; 30 days PTO/holidays; generous training budget; paid paternal/maternal leave; business development/growth incentives; top notch company swag. So we can have Benefits section.
Pay: Salary Description $150,000-$270,000. So we can have Pay section.
Schedule: Not explicitly given. No schedule info. So we should not create Schedule section.
Qualifications: The posting has "Required Qualifications:" and "Nice To Have". Those are qualifications. Could also have Requirements. The posting includes "Requirements Required Qualifications:" and then list. So we can have Requirements section (maybe combine with Qualifications). But we need to follow headings: Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have responsibilities list. We have requirements list (required qualifications). We have nice-to-have could be Skills or Qualifications. We could put nice-to-have under Skills or Qualifications. Since we have both Required Qualifications and Nice To Have, we could make Requirements for required, Qualifications for nice-to-have? Or we could combine. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine required and nice-to-have into one Requirements section, and maybe Skills not needed. But we have to use headings only when content exists. We have responsibilities, requirements (including required and nice-to-have), benefits, pay. That's four sections.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not include boilerplate like EEO etc. Remove that.
We must preserve all substantive information. So we need to include the description about Millennial Software, about the position, location, etc. Those can be in prose paragraphs under maybe About the role? But we are not supposed to repeat job title as heading. There's no explicit "About the role" heading in the posting, but we have "About Millennial Software" and "About The Position". We could treat those as prose under a heading like "About the role"? But the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we can use those headings if we have content. We have content about the role (description). So we could make an "About the role" section with paragraphs summarizing the company description and position description. However we must not invent or summarize away detail; we must preserve ALL substantive information. So we need to include the exact details, not just summary. We can include them as paragraphs under About the role.
Thus structure:
About the role
Millennial Software is revolutionizing the landscape of security and defense by leveraging our core competencies in software development, automation, DevSecOps, and machine learning.
[list of benefits? Actually benefits go to Benefits section.]
About The Position Millennial Software is looking for a self-starting, team-oriented Mid-to-Senior Network Engineer to join our dynamic development and operations team in supporting a Government customer. The network engineer will own a medium-sized, multi-enclave network that spans several classification levels and rides across multiple commercial service providers, using VPNs and government-approved encryption to maintain end-to-end security. The environment is primarily Cisco and carries both development and operational data, so the successful candidate will be comfortable balancing fast iteration for development teams against the change discipline an operational mission requires. ... (continue with responsibilities? Actually responsibilities are separate.) We'll need to split: The "About The Position" paragraph includes some responsibilities but we have a separate Responsibilities section later. We should not duplicate content. So we need to parse: The "About The Position" includes description of role and some responsibilities. The Responsibilities section then lists specific duties. To avoid duplication, we could keep the About The Position paragraph as is (excluding the list of responsibilities that are later enumerated). But the bullet list after "Responsibilities include physical hardware installation..." is a list of responsibilities. The preceding sentences also describe responsibilities. To preserve all info, we could keep the paragraph and then the list; some overlap but it's okay as long as we don't omit. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we can keep both.
Thus About the role section will contain the company description and the About The Position paragraph (maybe up to before "Responsibilities include").
Then Responsibilities section will have the list.
Then Requirements section will have required qualifications and nice-to-have (maybe as two sublists or combined). We'll need to preserve all details.
Then Benefits section will have list.
Then Pay section will have paragraph with salary range.
We must not include Schedule.
We must not include Job ID etc.
We must not include EEO boilerplate.
Now craft HTML.
We need to ensure proper nesting:
About the role
then ...
etc.
For lists: - ...
We need to be careful to not include extra whitespace? It's fine.
Let's extract text.
Company description: "Millennial Software is revolutionizing the landscape of security and defense by leveraging our core competencies in software development, automation, DevSecOps, and machine learning."
Then benefits list appears after that but we will move to Benefits section.
About The Position paragraph: "Millennial Software is looking for a self-starting, team-oriented Mid-to-Senior Network Engineer to join our dynamic development and operations team in supporting a Government customer. The network engineer will own a medium-sized, multi-enclave network that spans several classification levels and rides across multiple commercial service providers, using VPNs and government-approved encryption to maintain end-to-end security. The environment is primarily Cisco and carries both development and operational data, so the successful candidate will be comfortable balancing fast iteration for development teams against the change discipline an operational mission requires."
Then after that, there is a sentence: "This position is located in the Washington D.C. Metropolitan Area." That's also part of About The Position? It appears after responsibilities list? Actually in the posting: after responsibilities list, there is "This position is located in the Washington D.C. Metropolitan Area." Then "Job Functions" heading then list. So we should include location in About the role section as a paragraph.
Thus About the role section will have:
Millennial Software is revolutionizing the landscape of security and defense by leveraging our core competencies in software development, automation, DevSecOps, and machine learning.
Millennial Software is looking for a self-starting, team-oriented Mid-to-Senior Network Engineer to join our dynamic development and operations team in supporting a Government customer. The network engineer will own a medium-sized, multi-enclave network that spans several classification levels and rides across multiple commercial service providers, using VPNs and government-approved encryption to maintain end-to-end security. The environment is primarily Cisco and carries both development and operational data, so the successful candidate will be comfortable balancing fast iteration for development teams against the change discipline an operational mission requires.
This position is located in the Washington D.C. Metropolitan Area.
Now Responsibilities section: The list after "Responsibilities include physical hardware installation and cabling, network installation and configuration, infrastructure maintenance, troubleshooting when issues arise, and evolving the architecture to support emerging needs. This role also works alongside the broader team managing data center hardware; racking, cabling, and replacing compute and storage equipment in addition to network devices. The successful candidate will have the ability to work both independently with little supervision as well as engage with a team to achieve overall project objectives." Then there is a list starting with "Job Functions". Actually the posting: after that paragraph, there is "Job Functions" then a list. So we need to include all responsibilities: the paragraph plus the Job Functions list.
Thus Responsibilities section: we can have a for the paragraph (the one before Job Functions) and then a
for the Job Functions list.
Paragraph: "Install, configure, and maintain the client LAN/WAN across a primarily Cisco environmentMaintain network enclaves operating at multiple classification levels, preserving enclave separation, data labeling, and accreditation boundaries.Deliver end-to-end encrypted transport between sites: configure, monitor, and troubleshoot site-to-site VPN. Potentially includes COMSEC responsibilities, based on site and team needs.Respond to and resolve incidents within established service level agreements.Draft and implement network change requests and enhancements performing OS upgrades and patching on network devices applying change control appropriate to whether a change affects development or operational data.Support data center hardware installation and replacement alongside the broader team — racking, cabling, power, and swap-out of compute and storage devices as well as network equipment — including vendor RMA coordination.Keep the environment documented and accounted for: topology drawings, configuration management records, asset management, and inventory.Work directly with end-users and customers on site surveys, TEMS, and new equipment installs, ensuring their feedback is reflected in the delivered capability. Flexibility for occasional work beyond standard business hours and periodic travel as needed."
Wait that seems to be the Job Functions list but without line breaks. Actually the posting: after the paragraph about ability to work independently, there is "Job Functions Install, configure, and maintain the client LAN/WAN across a primarily Cisco environmentMaintain network enclaves operating at multiple classification levels, preserving enclave separation, data labeling, and accreditation boundaries.Deliver end-to-end encrypted transport between sites: configure, monitor, and troubleshoot site-to-site VPN. Potentially includes COMSEC responsibilities, based on site and team needs.Respond to and resolve incidents within established service level agreements.Draft and implement network change requests and enhancements performing OS upgrades and patching on network devices applying change control appropriate to whether a change affects development or operational data.Support data center hardware installation and replacement alongside the broader team — racking, cabling, power, and swap-out of compute and storage devices as well as network equipment — including vendor RMA coordination.Keep the environment documented and accounted for: topology drawings, configuration management records, asset management, and inventory.Work directly with end-users and customers on site surveys, TEMS, and new equipment installs, ensuring their feedback is reflected in the delivered capability. Flexibility for occasional work beyond standard business hours and periodic travel as needed."
Thus the Job Functions list is a continuous string without separators. We need to split into items. The original likely intended each phrase separated by a period? Actually they are separated by periods but missing spaces. We can split by periods and treat each as a list item. However we must preserve all substantive information; we can keep as a single paragraph? But instruction: Use - for any list of duties/requirements/benefits. So we need to make a list. We'll need to parse the string into items.
Let's manually split:
- Install, configure, and maintain the client LAN/WAN across a primarily Cisco environment
- Maintain network enclaves operating at multiple classification levels, preserving enclave separation, data labeling, and accreditation boundaries.
- Deliver end-to-end encrypted transport between sites: configure, monitor, and troubleshoot site-to-site VPN. Potentially includes COMSEC responsibilities, based on site and team needs.
- Respond to and resolve incidents within established service level agreements.
- Draft and implement network change requests and enhancements performing OS upgrades and patching on network devices applying change control appropriate to whether a change affects development or operational data.
- Support data center hardware installation and replacement alongside the broader team — racking, cabling, power, and swap-out of compute and storage devices as well as network equipment — including vendor RMA coordination
- for any list of duties/requirements/benefits. Use
for prose. We must not include boilerplate like EEO etc. Remove that. We must preserve all substantive information. So we need to include the description about Millennial Software, about the position, location, etc. Those can be in prose paragraphs under maybe About the role? But we are not supposed to repeat job title as heading. There's no explicit "About the role" heading in the posting, but we have "About Millennial Software" and "About The Position". We could treat those as prose under a heading like "About the role"? But the instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we can use those headings if we have content. We have content about the role (description). So we could make an "About the role" section with paragraphs summarizing the company description and position description. However we must not invent or summarize away detail; we must preserve ALL substantive information. So we need to include the exact details, not just summary. We can include them as paragraphs under About the role. Thus structure:
About the role
Millennial Software is revolutionizing the landscape of security and defense by leveraging our core competencies in software development, automation, DevSecOps, and machine learning.
[list of benefits? Actually benefits go to Benefits section.]
About The Position Millennial Software is looking for a self-starting, team-oriented Mid-to-Senior Network Engineer to join our dynamic development and operations team in supporting a Government customer. The network engineer will own a medium-sized, multi-enclave network that spans several classification levels and rides across multiple commercial service providers, using VPNs and government-approved encryption to maintain end-to-end security. The environment is primarily Cisco and carries both development and operational data, so the successful candidate will be comfortable balancing fast iteration for development teams against the change discipline an operational mission requires. ... (continue with responsibilities? Actually responsibilities are separate.) We'll need to split: The "About The Position" paragraph includes some responsibilities but we have a separate Responsibilities section later. We should not duplicate content. So we need to parse: The "About The Position" includes description of role and some responsibilities. The Responsibilities section then lists specific duties. To avoid duplication, we could keep the About The Position paragraph as is (excluding the list of responsibilities that are later enumerated). But the bullet list after "Responsibilities include physical hardware installation..." is a list of responsibilities. The preceding sentences also describe responsibilities. To preserve all info, we could keep the paragraph and then the list; some overlap but it's okay as long as we don't omit. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we can keep both. Thus About the role section will contain the company description and the About The Position paragraph (maybe up to before "Responsibilities include"). Then Responsibilities section will have the list. Then Requirements section will have required qualifications and nice-to-have (maybe as two sublists or combined). We'll need to preserve all details. Then Benefits section will have list. Then Pay section will have paragraph with salary range. We must not include Schedule. We must not include Job ID etc. We must not include EEO boilerplate. Now craft HTML. We need to ensure proper nesting:
About the role
then...
etc. For lists:- ...
Millennial Software is revolutionizing the landscape of security and defense by leveraging our core competencies in software development, automation, DevSecOps, and machine learning.
Millennial Software is looking for a self-starting, team-oriented Mid-to-Senior Network Engineer to join our dynamic development and operations team in supporting a Government customer. The network engineer will own a medium-sized, multi-enclave network that spans several classification levels and rides across multiple commercial service providers, using VPNs and government-approved encryption to maintain end-to-end security. The environment is primarily Cisco and carries both development and operational data, so the successful candidate will be comfortable balancing fast iteration for development teams against the change discipline an operational mission requires.
This position is located in the Washington D.C. Metropolitan Area.
Now Responsibilities section: The list after "Responsibilities include physical hardware installation and cabling, network installation and configuration, infrastructure maintenance, troubleshooting when issues arise, and evolving the architecture to support emerging needs. This role also works alongside the broader team managing data center hardware; racking, cabling, and replacing compute and storage equipment in addition to network devices. The successful candidate will have the ability to work both independently with little supervision as well as engage with a team to achieve overall project objectives." Then there is a list starting with "Job Functions". Actually the posting: after that paragraph, there is "Job Functions" then a list. So we need to include all responsibilities: the paragraph plus the Job Functions list. Thus Responsibilities section: we can have afor the paragraph (the one before Job Functions) and then a
- for the Job Functions list.
Paragraph: "Install, configure, and maintain the client LAN/WAN across a primarily Cisco environmentMaintain network enclaves operating at multiple classification levels, preserving enclave separation, data labeling, and accreditation boundaries.Deliver end-to-end encrypted transport between sites: configure, monitor, and troubleshoot site-to-site VPN. Potentially includes COMSEC responsibilities, based on site and team needs.Respond to and resolve incidents within established service level agreements.Draft and implement network change requests and enhancements performing OS upgrades and patching on network devices applying change control appropriate to whether a change affects development or operational data.Support data center hardware installation and replacement alongside the broader team — racking, cabling, power, and swap-out of compute and storage devices as well as network equipment — including vendor RMA coordination.Keep the environment documented and accounted for: topology drawings, configuration management records, asset management, and inventory.Work directly with end-users and customers on site surveys, TEMS, and new equipment installs, ensuring their feedback is reflected in the delivered capability. Flexibility for occasional work beyond standard business hours and periodic travel as needed."
Wait that seems to be the Job Functions list but without line breaks. Actually the posting: after the paragraph about ability to work independently, there is "Job Functions Install, configure, and maintain the client LAN/WAN across a primarily Cisco environmentMaintain network enclaves operating at multiple classification levels, preserving enclave separation, data labeling, and accreditation boundaries.Deliver end-to-end encrypted transport between sites: configure, monitor, and troubleshoot site-to-site VPN. Potentially includes COMSEC responsibilities, based on site and team needs.Respond to and resolve incidents within established service level agreements.Draft and implement network change requests and enhancements performing OS upgrades and patching on network devices applying change control appropriate to whether a change affects development or operational data.Support data center hardware installation and replacement alongside the broader team — racking, cabling, power, and swap-out of compute and storage devices as well as network equipment — including vendor RMA coordination.Keep the environment documented and accounted for: topology drawings, configuration management records, asset management, and inventory.Work directly with end-users and customers on site surveys, TEMS, and new equipment installs, ensuring their feedback is reflected in the delivered capability. Flexibility for occasional work beyond standard business hours and periodic travel as needed."
Thus the Job Functions list is a continuous string without separators. We need to split into items. The original likely intended each phrase separated by a period? Actually they are separated by periods but missing spaces. We can split by periods and treat each as a list item. However we must preserve all substantive information; we can keep as a single paragraph? But instruction: Use
- for any list of duties/requirements/benefits. So we need to make a list. We'll need to parse the string into items. Let's manually split: - Install, configure, and maintain the client LAN/WAN across a primarily Cisco environment - Maintain network enclaves operating at multiple classification levels, preserving enclave separation, data labeling, and accreditation boundaries. - Deliver end-to-end encrypted transport between sites: configure, monitor, and troubleshoot site-to-site VPN. Potentially includes COMSEC responsibilities, based on site and team needs. - Respond to and resolve incidents within established service level agreements. - Draft and implement network change requests and enhancements performing OS upgrades and patching on network devices applying change control appropriate to whether a change affects development or operational data. - Support data center hardware installation and replacement alongside the broader team — racking, cabling, power, and swap-out of compute and storage devices as well as network equipment — including vendor RMA coordination