Sr Principal Network Communications Administrator - Ellsworth AFB
VetJobs · Ellsworth Air Force Base, SD · 1 mo ago
$106k–$159k/yrFull-time
We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc as headings; can fold minor metadata into short p or drop.
We need to parse the job description.
Key content:
- Intro about military affiliated job seekers: maybe part of About the role? Could be "About the role" includes description of organization and role.
- At Northrop Grumman... repeated paragraphs about culture, pioneering spirit, etc. Could be part of About the role.
- Role: Sr. Principal Network Communications Administrator, location Ellsworth, SD.
- Essential Functions list: bullet points.
- Minimum Education Required: High School/GED (but later says Bachelor's etc). Actually there is contradictory: Minimum Education Required High School/GED then Additional Qualifications/Responsibilities Basic Qualifications: Must have a Bachelor’s degree... So we need to preserve all substantive info. Likely the Minimum Education Required is a mistake; but we must include it.
- Additional Qualifications/Responsibilities: Basic Qualifications (education + experience), Ability to be granted and maintain DoD SECRET clearance, may need TOP SECRET, SAP, CompTIA Security+, experience designing/maintaining LAN/WAN/Cloud networks, configuring/installing/maintaining network hardware, encryption devices (TACLANES), STIG compliance, network analysis tools, Microsoft Office suite, ability to lift up to 40 lbs, ability to work after hours/weekends.
- Preferred Qualifications: remote cloud architecture, Air Force flightline environment, Air Force flight communications systems, active DoD SECRET/TOP SECRET clearance, active Specific Special Access Program access #ICS Primary Level.
- Salary Range: $105,800.00 - $158,600.00
- City: Ellsworth, State: South Dakota
- Job Category: Engineering
- Job Code: Manufacturing
- Manufacturing Affiliate Sponsor: Northrop Grumman
We need sections: About the role (maybe includes intro and company description). Responsibilities (essential functions). Requirements (maybe basic qualifications). Qualifications (maybe education/experience?). Skills (maybe technical skills). Benefits (none given). Pay (salary range). Schedule (maybe mention ability to work after hours and weekends as needed). Also location maybe part of About the role.
We must not create sections with filler like "not specified". So only include sections where we have content.
We have content for About the role (intro, company culture, location). Responsibilities (essential functions list). Requirements (maybe basic qualifications? Actually "Requirements" could be the basic qualifications). Qualifications (maybe education/experience? But we already used Requirements for qualifications; we need to differentiate. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We could treat:
- About the role: description of company, role, location, military affiliated note.
- Responsibilities: essential functions list.
- Requirements: basic qualifications (education + experience, clearance, certifications, ability to lift, work hours).
- Qualifications: preferred qualifications? Or maybe "Qualifications" could be the combination of basic and preferred? But we already used Requirements for basic. Could put Qualifications for preferred qualifications.
- Skills: technical skills list (network hardware, tools, Microsoft Office, etc.) Could be separate.
- Pay: salary range.
- Schedule: ability to work after hours and weekends as needed.
- Benefits: none given, so omit.
We must not repeat job title as heading.
We must not include Job ID etc as headings; we can put minor metadata in a short p or drop. Could include location in About the role.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all bullet points exactly as given, but we can format as
- . Must not lose any detail.
Let's extract each piece.
About the role content:
- "ATTENTION MILITARY AFFILIATED JOB SEEKERS - Our organization works with partner companies to source qualified talent for their open roles. The following position is available to Veterans, Transitioning Military, National Guard and Reserve Members, Military Spouses, Wounded Warriors, and their Caregivers. If you have the required skill set, education requirements, and experience, please click the submit button and follow the next steps. Unless specifically stated otherwise, this role is "On-Site" at the location detailed in the job post."
- Then description of Northrop Grumman: "At Northrop Grumman, our employees have incredible opportunities to work on revolutionary systems that impact people's lives around the world today, and for generations to come. Our pioneering and inventive spirit has enabled us to be at the forefront of many technological advancements in our nation's history - from the first flight across the Atlantic Ocean, to stealth bombers, to landing on the moon. We look for people who have bold new ideas, courage and a pioneering spirit to join forces to invent the future, and have fun along the way. Our culture thrives on intellectual curiosity, cognitive diversity and bringing your whole self to work — and we have an insatiable drive to do what others think is impossible. Our employees are not only part of history, they're making history." This appears twice; we should include once (no duplication). We'll include it once.
- Then: "Northrop Grumman Aeronautics Systems has an opening for an Sr. Principal Network Communications Administrator to join our team of qualified, diverse individuals within our Ground Systems Team. This role is in Ellsworth, SD."
Thus About the role includes military affiliated note, company description, role title and location.
We must not repeat job title as heading, but we can mention it in paragraph.
Now Responsibilities: essential functions list bullet points.
Let's list them exactly:
- Provide real time support for network Ground Systems during flight operations and maintenance, addressing any issues related to communications and networking to include fault isolation, remediation, and resolution.
- Account for, control, and deploy equipment.
- Work with partners to resolve connectivity issues and data movement issues between Ground Systems and external networks.
- Perform field integration, troubleshooting, and repair of communications systems in military flight operations environment, including operations on flightline, in a hangar, and in command-and-control centers.
- Adherence to checklists and procedures to ensure repeated success and providing redlines to procedures when necessary.
- Work with a team to provide 24/7 on-site support for network operations of the Ground Communications Interface.
- Provide local network management support through updates, configurations, security patches, drawings, and feedback to the Responsible Engineers (REs).
- Communicate complex technical issues to local support, Main Operation Bases (MOBs), and Responsible Engineers (REs).
- Support and lead air crew engagement for proper techniques in solving complex analysis of technical problems that arise during operations.
- Assist with trend analysis as needed for Responsible Engineers (REs).
- Perform/support review and analysis of supplier design data and definition of functional test requirements including acceptance, qualification, and system integration.
- Take responsibility for the testing, maintenance, and integration of Comms and Networks equipment required to support ground and flight operations.
- Work with system admins, maintainers, and onsite personnel to troubleshoot and repair any internal operational issues.
Now Requirements: basic qualifications (education + experience, clearance, certifications, ability to lift, work hours). Also Minimum Education Required High School/GED (though contradictory). We'll include both.
Basic Qualifications:
- Must have a Bachelor’s degree in a Science, Technology, Engineering or Mathematics (STEM) discipline from an accredited university AND 8 years of related professional/military experience in Engineering; OR a Master’s degree in a STEM discipline from an accredited university AND 6 years of related professional/military experience in Engineering; or a Ph.D. AND 4 years of related professional/military experience in Engineering.
- Ability to be granted and maintain a DoD SECRET clearance.
- May be required to attain TOP SECRET clearance in the future.
- The ability to obtain Special Access Programs (SAP) within a period of time as determined by program and/or customer requirements, as a condition of continued employment.
- Current CompTIA Security Plus (or higher) certification.
- Experience designing and maintaining LAN, WAN, and Cloud based networks.
- Experience with configuring, installing, and maintaining network hardware.
- Experience configuring, installing, and maintaining encryption devices (TACLANES).
- Experience with STIG compliance.
- Experience in the use of network analysis tools (i.e. WireShark, Opnet, SolarWinds, etc.).
- Experience with Microsoft Office, Visio, Project, PowerPoint, and Excel.
- Ability to lift equipment weighing up to 40 pounds.
- Ability to work after hours and weekends as needed.
Also Minimum Education Required High School/GED (maybe separate). We'll include as a bullet.
Now Qualifications (preferred):
- Experience with remote cloud architecture.
- Experience working in an Air Force flightline environment
- Experience working with Air Force flight communications systems
- Active DoD SECRET or TOP SECRET clearance.
- Active Specific Special Access Program access #ICS Primary Level
Now Skills: maybe we could separate technical skills like network hardware, tools, Microsoft Office etc. But many of those are already in Requirements. Could treat Skills as the technical skills list (network hardware, tools, Microsoft Office, etc.) but we risk duplication. The instruction says preserve ALL substantive information; we can duplicate content across sections? It didn't forbid duplication, but better to avoid redundancy. However we need to fill sections meaningfully. Perhaps we can put Skills as the list of technical competencies: network hardware, encryption devices, STIG compliance, network analysis tools, Microsoft Office suite, remote cloud architecture, etc. But many are already in Requirements/Preferred. Might be okay to have overlapping but we should try to avoid redundancy. However we need to include all info; if we put some in Requirements and some in Skills, we still covered all. Let's decide:
- Requirements: education/experience/clearance/certification/ability to lift/work hours.
- Skills: technical skills: designing/maintaining LAN/WAN/Cloud networks, configuring/installing/maintaining network hardware, encryption devices (TACLANES), STIG compliance, network analysis tools (WireShark, Opnet, SolarWinds, etc.), Microsoft Office, Visio, Project, PowerPoint, Excel, remote cloud architecture, Air Force flightline environment, Air Force flight communications systems, active clearances, SAP access.
But that duplicates some. Might be okay but we risk being seen as filler? The instruction: "Prefer a few substantive sections over many thin ones." So maybe better to combine Requirements and Qualifications and Skills into fewer sections. But we must use headings only when there is real specific content. We could have:
- About the role
- Responsibilities
- Requirements (includes education/experience/clearance/certification/technical skills/preferred qualifications)
- Pay
- Schedule
That would be 5 sections. That seems reasonable. We can include all details under Requirements, using sub-lists maybe? But we must use
- for any list of duties/requirements/benefits. So we can have multiple lists under Requirements: education, experience, clearances, certifications, technical skills, preferred qualifications. That's okay.
Thus we avoid separate Skills section.
We need Pay section: salary range.
Schedule section: ability to work after hours and weekends as needed (maybe also 24/7 on-site support? That's responsibility). But schedule: mention ability to work after hours and weekends as needed.
We must not create Benefits section as none given.
Now we need to output HTML fragment only.
Structure:
About the role
... (combined paragraphs)
Responsibilities
- ... each bullet
Requirements
- ... maybe we need subheadings? Not allowed; only
for section headings. So we can just have a flat list of items. But that would
- for any list of duties/requirements/benefits. So we can have multiple lists under Requirements: education, experience, clearances, certifications, technical skills, preferred qualifications. That's okay.
Thus we avoid separate Skills section.
We need Pay section: salary range.
Schedule section: ability to work after hours and weekends as needed (maybe also 24/7 on-site support? That's responsibility). But schedule: mention ability to work after hours and weekends as needed.
We must not create Benefits section as none given.
Now we need to output HTML fragment only.
Structure: