Senior Information System Security Engineer (ISSE) (TS/SCI Clearance And Current Polygraph Required)
- Discuss this with your agent
- Open in Claude
- Open in ChatGPT
Prepare application
- Draft this with your agent
- Open in Claude
- Open in ChatGPT
Role details
Tech stack
Requirements
-
Must have at least 12 years of experience working as an ISSE on a large technical program.
-
Must have a solid understanding of security practices and policies and hands-on vulnerability testing experience.
-
Must have experience applying Risk Management Framework.
-
Must have experience formulating and assessing IT security policy.
-
Must have demonstrated knowledge of and experience with common security tools, such as Nessus, NMAP, and Wireshark hardware/software security implementation, communication protocol, encryption techniques/tools, and web services.
-
Must have experience with secure configurations of commonly used desktop and server operating systems.
-
Must be comfortable working on multiple systems and components simultaneously in various configurations.
-
Must have strong verbal and written communication skills.
-
Must be committed to adopting and adhering to best practices.
-
Must be able to effectively plan and prioritize tasking and communicate clearly regarding technical options and trade-offs.
-
Must be capable of performing high-quality work both independently and with a team in a fast-moving environment.
-
IASAE Level 2 or 3 required.
-
Active TS/SCI security clearance with a current polygraph is required
Apply for this position
This job is hosted externally. Click below to view the full posting and apply.
Prepare application
- Draft this with your agent
- Open in Claude
- Open in ChatGPT
Good distractions
Talks and stories from around this role — technically off-topic, practically not.
Moments
Explore playlistsVideos
See allRelated articles
See all
7 Important Tips That Every Software Developer Should Know
Dev Digest 134 - Where pixels sing?
How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again
Understanding and Mitigating Common Web Vulnerabilities