Sr Forescout Engineer
ECS · Honolulu, Hawaii, United States · 1 mo ago
$130k–$150k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, etc. Must preserve all substantive info.
We need to parse the job description.
Key info:
- Location: Honolulu, HI OR Wiesbaden, Germany office. Primarily on site, some remote, occasional support/deployment of Comply to Connect (C2C) at various Army bases, CONUS and OCONUS.
- Role: Sr Forescout Engineer.
- Provide engineering support and documentation to create a healthy security posture implementing Comply-To-Connect for delivered Managed Service supporting US Army.
- Focus on design, integration, deployment.
- Provide tactical and strategic input on improving overall network operations and Network Access Control using Forescout.
- Must be well versed in architectural best practices applying across breadth of technologies to solve organizational problem.
- Capable of articulating views on future development of technology to varying audiences, understand interaction between infrastructure and solution architecture.
- Provide Engineering support for Comply to Connect on multiple DoD networks and classification domains.
- Establish and maintain network analysis and monitoring tools; including fine-tuning, health reporting and alerting.
- Make recommendations to optimize stability, availability, reliability and performance of networking infrastructure.
- Resolve complex networking and other technology issues with multiple parties involved.
- Develop process and architecture diagrams.
- Identify and provide technical subject matter expertise on remediation and mitigation of all open findings from DISA STIGs.
- Provide program status reports and briefings to internal management, senior leadership and government oversight officials.
- Understanding of enterprise computing environments, distributed applications, strong knowledge and understanding of TCP/IP networks to include ASA, Palo Alto firewalls, and Cisco, Juniper, and Brocade switches.
- Advanced Administrator’s level of understanding of Operating Systems (Linux, Windows, Macintosh, and UNIX) is a plus.
- Computer Networking Systems Administrator’s level Knowledge of all protocol layers.
- Strong knowledge of enterprise networking environments.
- Expertise in debugging and root-cause analysis in complex systems and large environments.
- Experience installing, implementing and debugging network access control security solutions.
- Understanding of programming languages: C, Java, and Perl.
- This is a “hands‑on” position that requires someone who is capable of multi‑tasking. Requires an individual with a service‑oriented mentality that can focus and take ownership of assignments/issues and manage/resolve those issues.
- Work well in a team oriented environment and be able to self‑manage their tasks to ensure success.
- Communicate up and down within the organization; prepare detailed descriptions of issues, status updates, recommendations, and reports.
- Applicants must be organized with an eye for detail.
- Salary Range: $130,000 - $150,000
- General Description Of Benefits (maybe placeholder? Actually they wrote "General Description Of Benefits" but no details; we should not create Benefits section unless posting actually states them. It says "General Description Of Benefits" but no actual benefits listed. Likely we should not include Benefits section because no specific benefits described. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. So we can include Pay (salary range) but not Benefits or Schedule unless specified. There's no schedule info besides "primarily on site, with some remote work". That could be considered schedule? It's about work location, not schedule. The instruction says only create Schedule section if posting actually states them. It doesn't give explicit schedule like hours, shift, etc. So we should not create Schedule.
- Required Skills list: Active Secret Clearance or higher, US Citizen, DoD 8570 IAT II, 6+ yrs. experience working in a DOD environment (Contractor/Civilian/Military), preferably US Army or DISA, Willingness to obtain Forescout Certified Engineer (FSCE) certification within 90 days of employment, Experience with Network Access Controls, Experience with projects across development lifecycles (analysis through implementation), Ability to multi‑task and effectively prioritize competing requirements, Must be proficient with desktop programs such as MS Powerpoint, MS Excel, MS Word, MS Visio, Must possess a high attention to detail, Good oral and written communications skills, Have networking, telecom, or application development, client/server, network and internet/web development experience, The ability to apply IT industry standards to secure network environment, Experience in creating and maintaining programmatic and technical documentation to ensure efficient planning and execution, ability to manage and document system configurations.
- Desired Skills: Test plan development and execution, TS/SCI preferred, ITIL v3 or ITIL 4 Certification, Experience with the following: Windows, MDE, Trellix Endpoint Detection and Response (EDR), ACAS, Tychon, Elastic/Splunk, Intune, Knowledge of DODIN-A, JMN, and Army Networks.
We need to decide sections: About the role (maybe a brief summary), Responsibilities (list of duties), Requirements (mandatory), Qualifications (maybe overlapping with requirements? Usually qualifications include education/experience; but we can combine? The instruction: prefer a few substantive sections over many thin ones. We can have About the role, Responsibilities, Requirements, Skills (maybe combine required and desired?), Pay. But we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content.
We have About the role: we can summarize the role purpose.
Responsibilities: list of duties (design, integration, deployment, support, monitoring, recommendations, resolve issues, develop diagrams, STIG remediation, reports, etc.)
Requirements: mandatory items: Active Secret Clearance or higher, US Citizen, DoD 8570 IAT II, 6+ yrs DOD experience, willingness to obtain FSCE within 90 days, experience with Network Access Controls, experience across development lifecycles, ability to multitask, proficiency with MS Office, high attention to detail, good oral/written communications, networking/telecom/application dev experience, ability to apply IT industry standards, experience creating/maintaining documentation.
Qualifications: maybe education? Not mentioned. Could be omitted if no specific qualifications beyond experience. Could combine with Requirements. But we need to decide if we have content for Qualifications. The posting does not mention degrees or certifications required besides willingness to obtain FSCE. So maybe we skip Qualifications.
Skills: could list desired skills (test plan dev, TS/SCI, ITIL, specific tools, knowledge of DODIN-A etc.) plus maybe technical skills like OS knowledge, programming languages, debugging, etc. But many of those are already in responsibilities/requirements. To avoid duplication, we could put technical skills like OS knowledge, programming languages, debugging, expertise in NAC, etc. under Skills. However the instruction: prefer few substantive sections over many thin ones. We could combine Requirements and Skills into one section called Requirements (or Skills). But we need to follow headings; we can include both if they have content.
We have Pay: salary range.
We have no explicit Benefits or Schedule.
Thus output sections: About the role, Responsibilities, Requirements, Skills, Pay.
We need to use for each section heading. Use
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. So no
Sr Forescout Engineer
. Good.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them as lists.
We must not include boilerplate like EEO, etc.
Let's extract details precisely.
About the role: Could be a paragraph summarizing: "ECS is seeking a Sr Forescout Engineer to work in Honolulu, HI or Wiesbaden, Germany office. The role is primarily on‑site with some remote work and occasional support/deployment of Comply‑to‑Connect (C2C) at various Army bases CONUS and OCONUS. The engineer will provide engineering support and documentation to create a healthy security posture implementing Comply‑To‑Connect for the delivered Managed Service supporting the US Army, focusing on design, integration, and deployment."
We need to include location, remote, occasional support, etc.
Responsibilities: list each duty:
- Provide engineering support for Comply to Connect on multiple DoD networks and classification domains
- Establish and maintain network analysis and monitoring tools; including fine‑tuning, health reporting and alerting
- Make recommendations to optimize stability, availability, reliability and performance of networking infrastructure
- Resolve complex networking and other technology issues with multiple parties involved
- Develop process and architecture diagrams
- Identify and provide technical subject matter expertise on remediation and mitigation of all open findings from DISA STIGs
- Provide program status reports and briefings to internal management, senior leadership and government oversight officials
- Focus on design, integration, and deployment of Comply‑to‑Connect solutions
- Provide tactical and strategic input on improving overall network operations and Network Access Control using Forescout
- Apply architectural best practices across a breadth of technologies to solve organizational problems
- Articulate views on future technology development to varying audiences and understand interaction between infrastructure and solution architecture
- Demonstrate hands‑on, service‑oriented mentality, multi‑tasking, ownership of assignments/issues
- Work well in a team‑oriented environment and self‑manage tasks to ensure success
- Communicate up and down within the organization; prepare detailed descriptions of issues, status updates, recommendations, and reports
- Be organized with an eye for detail
We need to ensure we don't miss any.
Also mention: "Understanding of enterprise computing environments, distributed applications, and strong knowledge and understanding of TCP/IP networks to include ASA, Palo Alto firewalls, and Cisco, Juniper, and Brocade switches" - that's more a requirement/skill.
"Advanced Administrator’s level of understanding of Operating Systems (Linux, Windows, Macintosh, and UNIX) is a plus" - skill.
"Computer Networking Systems Administrator’s level Knowledge of all protocol layers" - skill.
"Strong knowledge of enterprise networking environments" - skill.
"Expertise in debugging and root-cause analysis in complex systems and large environments" - skill.
"Experience installing, implementing and debugging network access control security solutions" - skill/requirement.
"Understanding of programming languages: C, Java, and Perl" - skill.
"Ability to multi‑task and effectively prioritize competing requirements" - skill.
"Must be proficient with desktop programs such as MS Powerpoint, MS Excel, MS Word, MS Visio" - skill.
"Must possess a high attention to detail" - skill/requirement.
"Good oral and written communications skills." - skill.
"Have networking, telecom, or application development, client/server, network and internet/web development experience." - skill/experience.
"The ability to apply IT industry standards to secure network environment." - skill.
"Experience in creating and maintaining programmatic and technical documentation to ensure efficient planning and execution, ability to manage and document system configurations." - skill.
Now Required Skills list (mandatory):
- Active Secret Clearance or higher
- US Citizen
- DoD 8570 IAT II
- 6+ yrs. experience working in a DOD environment (Contractor/Civilian/Military), preferably US Army or DISA
- Willingness to obtain Forescout Certified Engineer (FSCE) certification within 90 days of employment
- Experience with Network Access Controls
- Experience with projects across development lifecycles (analysis through implementation)
- Ability to multi‑task and effectively prioritize competing requirements
- Must be proficient with desktop programs such as MS Powerpoint, MS Excel, MS Word, MS Visio
- Must possess a high attention to detail
- Good oral and written communications skills
- Have networking, telecom, or application development, client/server, network and internet/web development experience
- The ability to apply IT industry standards to secure network environment
-
for prose. We must not repeat job title as heading. So no