Network/Security Analyst- Onsite
Collins Aerospace · Great Falls, MT · 1 mo ago
On-siteFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content.
We need to parse the posting.
First, remove boilerplate: Date posted, Country, Location, Position Role Type, etc. Also remove "Learn More & Apply Now!" and other fluff.
We need to preserve substantive info.
Let's extract sections:
- About the role: The paragraph describing company and role: "Raytheon Company, Managed By Collins Aerospace At RTX, the world's largest aerospace and defense company..." etc. Also "We are seeking an onsite Network/Security Analyst to fulfill duties as part of a 24/7 operational helpdesk environment located on Malmstrom AFB in Great Falls, Montana." That's about the role.
We can put that in
About the role
withcontaining that description. - Responsibilities: The bullet list under "What You Will Do:" includes many duties. We need to convert to
- . The text: "This position is primarily a day‑staff role with the ability to support night and weekend operations when mission needs require. Perform Tier 1 and Tier 2 troubleshooting and analysis in an Enterprise IT environment. Assist engineers in configuring, managing, and maintaining applications, network routing, and switching across both Linux and Microsoft environments. Use COTS software such as SolarWinds, Splunk, MECM, Cisco Call Manager, BMC FootPrints, and JSpace (Juniper). Troubleshoot, repair, and configure network devices, including firewalls. Perform system administrator duties, including user account management, certificate management, and group policy administration. Maintain and troubleshoot virtualized environments using technologies such as ESXi, VMware, and vSphere. Support, maintain, and troubleshoot Virtual Desktop Infrastructure (VDI) environments, including deployment, configuration, user support, and issue resolution across enterprise VDI platforms. Configure and troubleshoot Type 1 encryption devices. Assist engineers with monthly patch management, LAN/site installs and decommissions, tech refreshes, and software upgrades."
We can treat each sentence as a list item.
- Requirements: The posting has "Qualifications You Must Have:" and also earlier "U.S. Citizen, U.S. Person, or Immigration Status Requirements: Active and transferable U.S. government issued security clearance is required prior to start date. U.S. citizenship is required, as only U.S. citizens are eligible for a security clearance Security Clearance Type: Top Secret - Current Security Clearance Status: Active and existing security clearance required on day 1". Also later "Qualifications You Must Have:" includes: Must have IT experience working in an Enterprise IT environment. Must be able to work shift schedule to include nights, weekends and holidays. DoD 8570 IAT Level II certification (Security+ or CISSP preferred) is required on day 1. Typically requires a degree in Science, Technology, Engineering or Mathematics (STEM) and minimum 2 years prior relevant experience or an Advanced Degree in a related field. Active and transferable U.S. government issued Top Secret security clearance is required prior to start date with the ability to obtain SCI after start. U.S. citizenship is required, as only U.S. citizens are eligible for a security clearance.
We need to separate Requirements vs Qualifications? The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
"Requirements" likely includes mandatory items: citizenship, clearance, shift schedule, certification, experience/education, etc.
"Qualifications" could be preferred qualifications: "Qualifications We Prefer :" includes experience with Windows & Server, Linux bash, computer security, understanding of network fundamentals, willingness to learn.
"Skills" maybe include specific technical skills: COTS software list, etc. But we already have responsibilities list includes many skills. Could separate skills as bullet list of technologies: SolarWinds, Splunk, MECM, Cisco Call Manager, BMC FootPrints, JSpace (Juniper), ESXi, VMware, vSphere, VDI platforms, Type 1 encryption devices, etc. However we need to avoid duplication. The instruction: "Use
- for any list of duties/requirements/benefits". So we can have separate sections for duties (responsibilities), requirements, qualifications, skills, benefits.
We need to decide what goes where.
Let's extract:
- Requirements (mandatory):
- U.S. citizenship required.
- Active and transferable U.S. government issued Top Secret security clearance required prior to start date (with ability to obtain SCI after start).
- Must have IT experience working in an Enterprise IT environment.
- Must be able to work shift schedule to include nights, weekends and holidays.
- DoD 8570 IAT Level II certification (Security+ or CISSP preferred) required on day 1.
- Typically requires a degree in STEM and minimum 2 years prior relevant experience or an Advanced Degree in a related field.
We could also include "Active Top Secret security clearance is required day one with SCI eligibility." That's same.
- Qualifications (preferred):
- Experience with Microsoft Windows & Server environment to include but not limited to Active Directory, DNS and Group policy.
- Experience with Linux bash.
- Experience implementing computer security.
- Understanding of basic network engineering fundamentals, including: OSI layers, IP addressing, sub-netting, TCP/IP stack, VLANs, DHCP, etc.
- Willingness to learn new technologies and applications as required.
- Skills: Could be the specific tools/technologies mentioned: COTS software such as SolarWinds, Splunk, MECM, Cisco Call Manager, BMC FootPrints, and JSpace (Juniper); technologies such as ESXi, VMware, and vSphere; VDI platforms; Type 1 encryption devices; etc. But many of these appear in responsibilities. However we could still list them under Skills as a concise list.
But we must not repeat content unnecessarily? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep all info, but we can organize it into sections without duplication? It says "Do NOT repeat the job title as a heading" but not about repeating content across sections. It might be okay to have same info in multiple sections? Probably better to avoid duplication but not required. However we should aim to not repeat same sentences verbatim in multiple sections if possible, but we can split.
Given the responsibilities already list many tasks that involve those tools. If we also list them under Skills, we'd be duplicating. Might be okay but better to assign tools to Skills and responsibilities to actions.
Let's parse responsibilities sentences and see if we can extract skills from them:
- Perform Tier 1 and Tier 2 troubleshooting and analysis in an Enterprise IT environment. (skill: troubleshooting)
- Assist engineers in configuring, managing, and maintaining applications, network routing, and switching across both Linux and Microsoft environments. (skill: configuring/managing/maintaining applications, network routing, switching; Linux/MS)
- Use COTS software such as SolarWinds, Splunk, MECM, Cisco Call Manager, BMC FootPrints, and JSpace (Juniper). (skill: using those tools)
- Troubleshoot, repair, and configure network devices, including firewalls. (skill: network devices)
- Perform system administrator duties, including user account management, certificate management, and group policy administration. (skill: sysadmin duties)
- Maintain and troubleshoot virtualized environments using technologies such as ESXi, VMware, and vSphere. (skill: virtualization)
- Support, maintain, and troubleshoot Virtual Desktop Infrastructure (VDI) environments, including deployment, configuration, user support, and issue resolution across enterprise VDI platforms. (skill: VDI)
- Configure and troubleshoot Type 1 encryption devices. (skill: encryption devices)
- Assist engineers with monthly patch management, LAN/site installs and decommissions, tech refreshes, and software upgrades. (skill: patch management, LAN/site installs, tech refresh, software upgrades)
Thus we could put these as responsibilities (actions). Skills could be the specific technologies: SolarWinds, Splunk, MECM, Cisco Call Manager, BMC FootPrints, JSpace (Juniper), ESXi, VMware, vSphere, VDI platforms, Type 1 encryption devices, etc. Also maybe Linux, Microsoft Windows, Active Directory, DNS, Group policy, etc. But those appear in qualifications preferred.
We could decide to not have a separate Skills section if it's too thin. But we have enough specific tech list to make a Skills section.
Benefits: The posting lists many benefits under "What We Offer:" and later also mentions benefits in generic statements. We need to include only substantive benefits, not generic placeholder. The list: Medical, dental, and vision insurance. Three weeks of vacation for newly hired employees. Generous 401(k) plan that includes employer matching funds and separate employer retirement contribution, including a Lifetime Income Strategy option. Tuition reimbursement program. Student Loan Repayment Program. Life insurance and disability coverage. Optional coverages you can buy pet insurance, home and auto insurance, additional life and accident insurance, critical illness insurance, group legal, ID theft protection. Birth, adoption, parental leave benefits. Ovia Health, fertility, and family planning. Adoption Assistance. Autism Benefit. Employee Assistance Plan, including up to 10 free counseling sessions. Healthy You Incentives, wellness rewards program. Doctor on Demand, virtual doctor visits. Bright Horizons, child and elder care services. Teladoc Medical Experts, second opinion program. And more!
We should include these as bullet list under Benefits.
Pay: The posting includes: "The salary range for this role is 68,900 USD - 131,100 USD. The salary range provided is a good faith estimate representative of all experience levels." That's specific pay info. So we include Pay section with that.
Schedule: The posting mentions shift schedule: "Must be able to work shift schedule to include nights, weekends and holidays." Also earlier: "This position is primarily a day‑staff role with the ability to support night and weekend operations when mission needs require." So schedule info exists. We can include Schedule section with that.
Now we need to output HTML fragment with headings
and content. We must not include any markdown fences. We'll produce something like:
About the role
...
Responsibilities
- ... ...
Requirements
- U.S. citizenship required.
- Active and transferable U.S. government issued Top Secret security clearance required prior to start date (with ability to obtain SCI after start).
- IT experience working in an Enterprise IT environment.
- Ability to work shift schedule including nights, weekends, and holidays.
- DoD 8570 IAT Level II certification (Security+ or CISSP preferred) required on day 1.
- Degree in Science, Technology, Engineering or Mathematics (STEM) and minimum 2 years prior relevant experience, or an Advanced Degree in a related field.
Qualifications
- Experience with Microsoft Windows & Server environment (Active Directory, DNS, Group policy).
- Experience with Linux bash.
- Experience implementing computer security.
- Understanding of basic network engineering fundamentals (OSI layers, IP addressing, sub‑netting, TCP/IP stack, VLANs, DHCP, etc.).
- Willingness to learn new technologies and applications as required.
Skills
- COTS software: SolarWinds, Splunk, MECM, Cisco Call Manager, BMC FootPrints, JSpace (Juniper).
- Virtualization technologies: ESXi, VM
- for any list of duties/requirements/benefits". So we can have separate sections for duties (responsibilities), requirements, qualifications, skills, benefits.
We need to decide what goes where.
Let's extract:
- Requirements (mandatory):
- U.S. citizenship required.
- Active and transferable U.S. government issued Top Secret security clearance required prior to start date (with ability to obtain SCI after start).
- Must have IT experience working in an Enterprise IT environment.
- Must be able to work shift schedule to include nights, weekends and holidays.
- DoD 8570 IAT Level II certification (Security+ or CISSP preferred) required on day 1.
- Typically requires a degree in STEM and minimum 2 years prior relevant experience or an Advanced Degree in a related field.
We could also include "Active Top Secret security clearance is required day one with SCI eligibility." That's same.
- Qualifications (preferred):
- Experience with Microsoft Windows & Server environment to include but not limited to Active Directory, DNS and Group policy.
- Experience with Linux bash.
- Experience implementing computer security.
- Understanding of basic network engineering fundamentals, including: OSI layers, IP addressing, sub-netting, TCP/IP stack, VLANs, DHCP, etc.
- Willingness to learn new technologies and applications as required.
- Skills: Could be the specific tools/technologies mentioned: COTS software such as SolarWinds, Splunk, MECM, Cisco Call Manager, BMC FootPrints, and JSpace (Juniper); technologies such as ESXi, VMware, and vSphere; VDI platforms; Type 1 encryption devices; etc. But many of these appear in responsibilities. However we could still list them under Skills as a concise list.
But we must not repeat content unnecessarily? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep all info, but we can organize it into sections without duplication? It says "Do NOT repeat the job title as a heading" but not about repeating content across sections. It might be okay to have same info in multiple sections? Probably better to avoid duplication but not required. However we should aim to not repeat same sentences verbatim in multiple sections if possible, but we can split.
Given the responsibilities already list many tasks that involve those tools. If we also list them under Skills, we'd be duplicating. Might be okay but better to assign tools to Skills and responsibilities to actions.
Let's parse responsibilities sentences and see if we can extract skills from them:
- Perform Tier 1 and Tier 2 troubleshooting and analysis in an Enterprise IT environment. (skill: troubleshooting)
- Assist engineers in configuring, managing, and maintaining applications, network routing, and switching across both Linux and Microsoft environments. (skill: configuring/managing/maintaining applications, network routing, switching; Linux/MS)
- Use COTS software such as SolarWinds, Splunk, MECM, Cisco Call Manager, BMC FootPrints, and JSpace (Juniper). (skill: using those tools)
- Troubleshoot, repair, and configure network devices, including firewalls. (skill: network devices)
- Perform system administrator duties, including user account management, certificate management, and group policy administration. (skill: sysadmin duties)
- Maintain and troubleshoot virtualized environments using technologies such as ESXi, VMware, and vSphere. (skill: virtualization)
- Support, maintain, and troubleshoot Virtual Desktop Infrastructure (VDI) environments, including deployment, configuration, user support, and issue resolution across enterprise VDI platforms. (skill: VDI)
- Configure and troubleshoot Type 1 encryption devices. (skill: encryption devices)
- Assist engineers with monthly patch management, LAN/site installs and decommissions, tech refreshes, and software upgrades. (skill: patch management, LAN/site installs, tech refresh, software upgrades)
Thus we could put these as responsibilities (actions). Skills could be the specific technologies: SolarWinds, Splunk, MECM, Cisco Call Manager, BMC FootPrints, JSpace (Juniper), ESXi, VMware, vSphere, VDI platforms, Type 1 encryption devices, etc. Also maybe Linux, Microsoft Windows, Active Directory, DNS, Group policy, etc. But those appear in qualifications preferred.
We could decide to not have a separate Skills section if it's too thin. But we have enough specific tech list to make a Skills section.
Benefits: The posting lists many benefits under "What We Offer:" and later also mentions benefits in generic statements. We need to include only substantive benefits, not generic placeholder. The list: Medical, dental, and vision insurance. Three weeks of vacation for newly hired employees. Generous 401(k) plan that includes employer matching funds and separate employer retirement contribution, including a Lifetime Income Strategy option. Tuition reimbursement program. Student Loan Repayment Program. Life insurance and disability coverage. Optional coverages you can buy pet insurance, home and auto insurance, additional life and accident insurance, critical illness insurance, group legal, ID theft protection. Birth, adoption, parental leave benefits. Ovia Health, fertility, and family planning. Adoption Assistance. Autism Benefit. Employee Assistance Plan, including up to 10 free counseling sessions. Healthy You Incentives, wellness rewards program. Doctor on Demand, virtual doctor visits. Bright Horizons, child and elder care services. Teladoc Medical Experts, second opinion program. And more!
We should include these as bullet list under Benefits.
Pay: The posting includes: "The salary range for this role is 68,900 USD - 131,100 USD. The salary range provided is a good faith estimate representative of all experience levels." That's specific pay info. So we include Pay section with that.
Schedule: The posting mentions shift schedule: "Must be able to work shift schedule to include nights, weekends and holidays." Also earlier: "This position is primarily a day‑staff role with the ability to support night and weekend operations when mission needs require." So schedule info exists. We can include Schedule section with that.
Now we need to output HTML fragment with headings