Cyber Systems Engineering, Advisor - TS/SCI w/Poly
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we need to include sections only if posting has real specific content for them. The posting includes "About The Role" heading with content: location, clearance, position overview. That's "About the role". So we should have About the role
with content.
Then "Key Responsibilities" list – that is Responsibilities section.
Then "Qualifications" heading with Basic Qualifications etc. That's Qualifications.
Then "Required Skills & Experience" – that's Skills.
Then "Preferred Qualifications" – could be part of Qualifications or separate? The instruction says we can have Qualifications and Skills sections. Preferred qualifications could be under Qualifications as additional info, but we must not create thin sections. Probably combine basic and preferred under Qualifications? But we have separate "Required Skills & Experience" which is Skills. The "Preferred Qualifications" could be included under Qualifications as extra bullet points, but we need to decide.
We also have "Work Environment" – not in list of allowed headings; we could maybe omit or incorporate into About the role? The instruction says only use those headings; we should not create other headings. So we can either drop Work Environment or incorporate its content into About the role or maybe under Responsibilities? Probably better to incorporate into About the role as a paragraph.
Then "Why Peraton" – not in allowed headings; could be omitted or maybe part of About the role? Probably omit as not required.
Then "Details" includes Target Salary Range, Benefits Statement, Application Statements, EEO etc. We need Pay and Benefits sections if they have real specific content. Pay: we have Target Salary Range: $135,000 - $216,000. That's specific. So we need Pay
with that info. Also mention that salary determined by factors etc. That's still pay details. So include.
Benefits: Benefits Statement: list of benefits. So we need Benefits
with that list.
Schedule: Not mentioned. No schedule info. So we should not create Schedule section.
Also we need to include maybe "Requirements" section? The posting has Basic Qualifications under Qualifications. Could treat Requirements as same as Qualifications? The instruction lists both Requirements and Qualifications as possible headings. We need to decide based on content. The posting has "Basic Qualifications" and "Preferred Qualifications". Could map Basic Qualifications to Requirements, and Preferred Qualifications to Qualifications? Or combine. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have both Requirements and Qualifications sections if content exists. The posting has Basic Qualifications (required) and Preferred Qualifications (preferred). So we could put Basic Qualifications under Requirements, and Preferred Qualifications under Qualifications. Also we have Required Skills & Experience under Skills. That seems appropriate.
Thus sections:
- About the role (location, clearance, position overview, maybe work environment)
- Responsibilities (Key Responsibilities list)
- Requirements (Basic Qualifications)
- Qualifications (Preferred Qualifications)
- Skills (Required Skills & Experience)
- Benefits (Benefits Statement)
- Pay (Target Salary Range and salary determination details)
We must not include Schedule.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the details exactly as given, but we can format as
or
- . For lists, use
- . For prose, use
. We must not repeat job title as heading. The job title is "Network Systems Engineer (Cloud & Network Operations)". Not to be used as heading. We must not put Job ID/requisition numbers as headings – none present. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out EEO statement, application statements, etc. Also remove "Application Statements:" and the following text about 30 days, on-camera interview, AI tools prohibition, etc. Also remove EEO line. Also remove "Why Peraton" maybe? It's not boilerplate but not in allowed headings; we could either drop it or incorporate into About the role? The instruction says "Prefer a few substantive sections over many thin ones." So we could drop Why Peraton entirely as it's not required heading and could be considered boilerplate? It's not exactly boilerplate but it's promotional. Safer to omit because not in allowed headings and we should not create extra headings. The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It didn't say we must include all content; we must preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep all substantive information. If we drop Why Peraton, we lose substantive info about why work at Peraton. That is substantive. So we need to include it somewhere. Since we cannot create a heading not in list, we could incorporate it into About the role as a paragraph. That would preserve the info. Similarly, Work Environment could be incorporated into About the role. Thus About the role section will contain: location, clearance, position overview, work environment, why Peraton (maybe combined). We'll need to keep all details. Let's extract the relevant paragraphs. From posting: About Peraton (company description) – maybe not needed as substantive for the role? It's about the company; could be considered substantive but not directly about the role. However we might incorporate into About the role? The instruction says we must preserve ALL substantive information. The company description is substantive about Peraton. But we have no heading for company info. Could we put it under About the role? That might be okay as it's still about the role's context. But the heading "About the role" is specific to role; adding company description might be okay but could be considered not strictly about the role. However we need to preserve it; we could add a
under About the role that includes the company description. That would preserve it. But we also have "About Peraton" paragraph at start. Then "About The Role" heading. So we could combine. Let's extract: About Peraton paragraph: "Peraton is a next-generation national security company that drives missions of consequence spanning the globe and extending to the farthest reaches of the galaxy. As the world's leading mission capability integrator and transformative enterprise IT provider, we deliver trusted, highly differentiated solutions and technologies to protect our nation and allies. Peraton operates at the critical nexus between traditional and nontraditional threats across all domains: land, sea, space, air, and cyberspace. The company serves as a valued partner to essential government agencies and supports every branch of the U.S. armed forces. Each day, our employees solve the most daunting challenges that our customers face. Visit peraton.com to learn how we're keeping people around the world safe and secure." About The Role: includes location, clearance, position overview. Position Overview paragraph: "We are seeking a highly capable Network Systems Engineer to support mission-critical operations within our customer environment. This role operates at the intersection of enterprise networking, cloud infrastructure, and real-time operations, ensuring the availability, performance, and security of systems supporting national intelligence missions. This is an operations-focused engineering role, requiring technical expertise to monitor, analyze, and sustain complex, distributed systems. The ideal candidate thrives in high-tempo environments and understands the importance of precision, speed, and mission continuity." Work Environment paragraph: "High-tempo, mission-driven environment supporting national security operationsCollaboration across multidisciplinary teams including network engineering, cybersecurity, and cloud operationsEmphasis on operational excellence, rapid response, and continuous improvement" Why Peraton paragraph: "At Peraton, you'll work at the forefront of national security, supporting some of the most complex and mission-critical programs within the Intelligence Community. We combine deep domain expertise in cyber, signals intelligence, cloud, and network operations with a mission-first mindset-enabling our teams to deliver capabilities that directly impact real-world operations." We need to preserve all that. Now Responsibilities: list of items after "Key Responsibilities". Let's extract each bullet: - Monitor and sustain high-availability network and cloud infrastructure supporting our mission systems - Analyze network traffic, system logs, and telemetry to detect anomalies, performance degradation, and potential mission impact - Provide real-time situational awareness and concise operational reporting to mission stakeholders - Perform incident triage, root cause analysis, and coordinated response actions across network and system layers - Escalate issues with clear technical context, impact assessment, and actionable recommendations - Develop and execute remediation strategies to restore services and prevent recurrence - Support secure data flows and cross-domain solutions, ensuring compliance with IC security requirements - Collaborate with systems engineers, cybersecurity teams, and cloud architects to enhance resiliency, performance, and scalability - Contribute to runbooks, SOPs, and automation efforts to improve operational efficiency and response times - Maintain awareness of evolving network architectures, cloud capabilities, and threat landscapes within the customer environment - #MDFSP (maybe a tag; we can keep as is? It's a hashtag; maybe keep as part of responsibilities? It's likely a tag; we could keep as a bullet? It's not a responsibility; but it's present. We'll keep as a bullet? Might be considered metadata. Safer to keep as a bullet? It's not a responsibility; but we could drop it as it's not substantive? It's a tag maybe for internal use. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The tag "#MDFSP" is not substantive; maybe we can drop it. It's likely a internal code. I'd drop it. Now Requirements (Basic Qualifications): - Ten (10) years of experience as a Systems Engineer, Network Engineer, or related role supporting programs of similar scope, type, and complexity - Bachelor's degree in Systems Engineering, Computer Science, Information Systems, Engineering Science, Engineering Management, or a related discipline from an accredited institution - OR five (5) additional years of relevant experience may be substituted for a degree - Active TS/SCI clearance with Maryland Polygraph required We need to keep the OR statement as part of requirements. Now Qualifications (Preferred Qualifications): - Experience supporting Maryland customer or similar Intelligence Community missions - Knowledge of cross-domain solutions (CDS), data tagging, and secure data transfer mechanisms - Experience with DevSecOps, automation, or infrastructure-as-code (Terraform, Ansible, etc.) - Familiarity with Zero Trust architectures and advanced network security controls - Experience with cloud platforms (AWS GovCloud, Azure Government) in classified environments - Relevant certifications such as CCNP/CCIE, Security+, AWS Solutions Architect, or equivalent Now Skills (Required Skills & Experience): - Strong expertise in enterprise networking (TCP/IP, routing protocols such as BGP/OSPF, switching, DNS, segmentation) - Experience in real-time operations environments (NOC, SOC, or mission operations centers) - Proficiency with monitoring and analytics tools (e.g., Splunk, Elastic, Prometheus, SolarWinds, or similar) - Experience analyzing packet-level data, logs, and system metrics to support troubleshooting and performance tuning - Solid understanding of Linux/Unix systems and operational scripting (B
- . For prose, use