Security Engineering Lead
Agile Defense · Reston, VA · 1 mo ago
HybridFull-time
We need to output HTML fragment with sections: About the role? The posting includes "About Agile Defense" but not "About the role". The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to decide which sections to include based on content.
Content includes:
- About Agile Defense (company description). Could be "About the role"? Actually "About Agile Defense" is company description, not role. But we could treat as "About the role"? The instruction says use headings like About the role, Responsibilities, etc. But we can also use other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples, but we can use other headings if appropriate? Probably we should stick to those headings when applicable. The posting includes a summary, responsibilities, qualifications, additional skills & qualifications, working conditions, core values, etc.
We need to decide which sections to output.
We have:
- Summary: "Agile Defense is seeking experienced Security Engineering Lead to support an enterprise cybersecurity program delivering 24/7 Cybersecurity Operations Center (CSOC) services. This role serves as the technical lead for SOC security engineering and modernization efforts, including the integration and sustainment of SIEM, SOAR, EDR, and IDS/IPS platforms. Responsibilities include ensuring compliance with established standards, optimizing system performance, and driving continuous improvement across the enterprise security architecture. A highly technical self-starter with excellent analytical and problem-solving skills, flexibility, good judgment and the ability to coordinate multiple, concurrent tasks in an effective manner."
That's a prose summary.
- JOB DUTIES AND RESPONSIBILITIES: bullet list (though not bullet but sentences). We can turn into - .
- QUALIFICATIONS: includes Required Certifications, Education, Background, and Years of Experience. Could be under Requirements or Qualifications.
- ADDITIONAL SKILLS & QUALIFICATIONS: includes Required Skills and Preferred Skills.
- WORKING CONDITIONS: includes Environmental Conditions Hybrid in Reston, VA, Strength Demands Physical Requirements (but no detail). Might be minimal.
- Core Values: description of company values.
We need to remove boilerplate: EEO, AI tools, etc.
We need to preserve all substantive info.
We need to avoid sections with filler like "not specified". Pay, Schedule, Benefits not mentioned, so we should not create those sections.
We need to decide on sections: maybe About the role (could be summary), Responsibilities, Requirements (or Qualifications), Skills, Working Conditions (maybe not needed if minimal), Culture/Values (maybe not in list but could be a section like "About the company"? Not in list but we could still use
for "Company Overview" but instruction says use those examples; but we can still use other headings? Safer to stick to given headings. However, we have company description that could go under "About the role"? Not exactly. Could treat as "About the role" includes company overview? Might be okay.
Alternatively, we could omit company description if not needed? But we must preserve ALL substantive information. So we need to include it somewhere.
We could create a section "About the company" using but not in list; risk of violating instruction? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we can use other headings as long as they are . Probably fine.
Thus we can have sections:
- About Agile Defense (company overview)
- Summary (maybe as part of About the role)
- Responsibilities
- Qualifications (or Requirements)
- Skills (maybe split Required and Preferred)
- Working Conditions (maybe brief)
- Core Values (Culture)
We need to avoid duplication.
Let's extract substantive content.
Company overview paragraph: "At Agile Defense we know that action defines the outcome and new challenges require new solutions. That’s why we always look to the future and embrace change with an unmovable spirit and the courage to build for what comes next. Our vision is to bring adaptive innovation to support our nation's most important missions through the seamless integration of advanced technologies, elite minds, and unparalleled agility—leveraging a foundation of speed, flexibility, and ingenuity to strengthen and protect our nation’s vital interests."
That's substantive.
Summary paragraph: as above.
Responsibilities: list:
- Engineer, integrate, and maintain CSOC capabilities and platforms, ensuring effective configuration management and performance optimization.
- Advance Zero Trust principles, automation, and telemetry coverage across both cloud and on-premises environments.
- Assess and test emerging technologies; develop comprehensive technical reports and implementation plans to support modernization initiatives.
We could also include "ensuring compliance with established standards, optimizing system performance, and driving continuous improvement across the enterprise security architecture." but that was in summary; but it's also a responsibility. We'll keep it maybe in responsibilities.
Qualifications:
- Required Certifications: Minimum required A+, Security+ or Network+; CISSP certification.
- Education, Background, and Years of Experience: Bachelor's Degree
Also maybe years of experience? Not explicitly stated besides "experienced". But we have "Minimum of 3 years’ experience security administration systems and support." under Required Skills.
Thus qualifications: Bachelor's Degree, certifications.
Skills:
Required Skills (list many):
- A minimum of 3 years’ experience security administration systems and support.
- Strong working knowledge of Security Services, Networking, Security Policy, and Consulting.
- Proven experience in installing, configuring, monitoring, and troubleshooting network security solutions and related monitoring tools including Layer 2 / Layer 3 network devices, Network Admission Control (NAC), 802.1x, Firewalls, IDS / IPS, VPN Solutions, Web Application Firewalls, Content Filtering, fault analysis.
- Advanced working knowledge of encryption algorithms, Operating Systems (Linux, windows), secure communications, SIEM technologies, and embedded systems security.
- Advanced working knowledge of network and data communication protocols.
- Familiar with standard concepts, practices, and procedures within a particular field such as NIST, FISMA and Common Criteria regulations and standards.
- Experience with Network based IDS / IPS technologies and affiliated modes of operation; experienced in evaluating new technologies and processes that enhance security capabilities.
- Supervise changes in software, hardware, facilities, telecommunications and user needs.
- Experience with Test security solutions using industry standard analysis criteria; experience with the delivery technical reports and formal papers on test findings; experience responding to information security issues during each stage of a project’s lifecycle to include.
- Strong scripting skills (bash PowerShell) and ability to use automation tools such as ansible, or puppet.
- Produce technical documentation, including architecture diagrams, and detailed root cause analysis reports.
Preferred Skills:
- CISSP certification (though already required? but listed as preferred)
- Experience with supporting Zero Trust Network and Operating Certifications (Cisco, Redhat, Microsoft)
- Cloud provider certifications (AWS Certified Solutions Architect, Azure Solutions Architect Expert, etc)
- Supervise changes in software, hardware, facilities, telecommunications and user needs. (duplicate)
- Excellent written and oral communication skills
Working Conditions:
- Environmental Conditions Hybrid in Reston, VA
- Strength Demands Physical Requirements (no detail) maybe we can omit as filler.
Core Values: description of 6Hs.
We need to avoid duplication: "Supervise changes..." appears twice; we can keep once.
We need to remove boilerplate: EEO, AI tools, etc.
Now produce HTML.
We'll use for each section heading.
Inside sections, use
for prose,
- for lists.
We need to preserve all substantive info; we can combine some lists.
Let's structure:
About Agile Defense
At Agile Defense we know that action defines the outcome and new challenges require new solutions. That’s why we always look to the future and embrace change with an unmovable spirit and the courage to build for what comes next. Our vision is to bring adaptive innovation to support our nation's most important missions through the seamless integration of advanced technologies, elite minds, and unparalleled agility—leveraging a foundation of speed, flexibility, and ingenuity to strengthen and protect our nation’s vital interests.
Summary
Agile Defense is seeking experienced Security Engineering Lead to support an enterprise cybersecurity program delivering 24/7 Cybersecurity Operations Center (CSOC) services. This role serves as the technical lead for SOC security engineering and modernization efforts, including the integration and sustainment of SIEM, SOAR, EDR, and IDS/IPS platforms. Responsibilities include ensuring compliance with established standards, optimizing system performance, and driving continuous improvement across the enterprise security architecture. A highly technical self-starter with excellent analytical and problem-solving skills, flexibility, good judgment and the ability to coordinate multiple, concurrent tasks in an effective manner.
Responsibilities
- Engineer, integrate, and maintain CSOC capabilities and platforms, ensuring effective configuration management and performance optimization.
- Advance Zero Trust principles, automation, and telemetry coverage across both cloud and on-premises environments.
- Assess and test emerging technologies; develop comprehensive technical reports and implementation plans to support modernization initiatives.
- Ensure compliance with established standards, optimize system performance, and drive continuous improvement across the enterprise security architecture.
Qualifications
- Required Certifications: Minimum required A+, Security+ or Network+; CISSP certification.
- Education: Bachelor's Degree.
Required Skills
- A minimum of 3 years’ experience security administration systems and support.
- Strong working knowledge of Security Services, Networking, Security Policy, and Consulting.
- Proven experience in installing, configuring, monitoring, and troubleshooting network security solutions and related monitoring tools including Layer 2 / Layer 3 network devices, Network Admission Control (NAC), 802.1x, Firewalls, IDS / IPS, VPN Solutions, Web Application Firewalls, Content Filtering, fault analysis.
- Advanced working knowledge of encryption algorithms, Operating Systems (Linux, windows), secure communications, SIEM technologies, and embedded systems security.
- Advanced working knowledge of network and data communication protocols.
- Familiar with standard concepts, practices, and procedures within a particular field such as NIST, FISMA and Common Criteria regulations and standards.
- Experience with Network based IDS / IPS technologies and affiliated modes of operation; experienced in evaluating new technologies and processes that enhance security capabilities.
- Supervise changes in software, hardware, facilities, telecommunications and user needs.
- Experience with testing security solutions using industry standard analysis criteria; experience with the delivery of technical reports and formal papers on test findings; experience responding to information security issues during each stage
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include based on content. Content includes: - About Agile Defense (company description). Could be "About the role"? Actually "About Agile Defense" is company description, not role. But we could treat as "About the role"? The instruction says use headings like About the role, Responsibilities, etc. But we can also use other headings? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples, but we can use other headings if appropriate? Probably we should stick to those headings when applicable. The posting includes a summary, responsibilities, qualifications, additional skills & qualifications, working conditions, core values, etc.
We need to decide which sections to output.
We have:
- Summary: "Agile Defense is seeking experienced Security Engineering Lead to support an enterprise cybersecurity program delivering 24/7 Cybersecurity Operations Center (CSOC) services. This role serves as the technical lead for SOC security engineering and modernization efforts, including the integration and sustainment of SIEM, SOAR, EDR, and IDS/IPS platforms. Responsibilities include ensuring compliance with established standards, optimizing system performance, and driving continuous improvement across the enterprise security architecture. A highly technical self-starter with excellent analytical and problem-solving skills, flexibility, good judgment and the ability to coordinate multiple, concurrent tasks in an effective manner."
That's a prose summary.
- JOB DUTIES AND RESPONSIBILITIES: bullet list (though not bullet but sentences). We can turn into - .
- QUALIFICATIONS: includes Required Certifications, Education, Background, and Years of Experience. Could be under Requirements or Qualifications.
- ADDITIONAL SKILLS & QUALIFICATIONS: includes Required Skills and Preferred Skills.
- WORKING CONDITIONS: includes Environmental Conditions Hybrid in Reston, VA, Strength Demands Physical Requirements (but no detail). Might be minimal.
- Core Values: description of company values.
We need to remove boilerplate: EEO, AI tools, etc.
We need to preserve all substantive info.
We need to avoid sections with filler like "not specified". Pay, Schedule, Benefits not mentioned, so we should not create those sections.
We need to decide on sections: maybe About the role (could be summary), Responsibilities, Requirements (or Qualifications), Skills, Working Conditions (maybe not needed if minimal), Culture/Values (maybe not in list but could be a section like "About the company"? Not in list but we could still use
for "Company Overview" but instruction says use those examples; but we can still use other headings? Safer to stick to given headings. However, we have company description that could go under "About the role"? Not exactly. Could treat as "About the role" includes company overview? Might be okay.
Alternatively, we could omit company description if not needed? But we must preserve ALL substantive information. So we need to include it somewhere.
We could create a section "About the company" using but not in list; risk of violating instruction? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we can use other headings as long as they are . Probably fine.
Thus we can have sections:
- About Agile Defense (company overview)
- Summary (maybe as part of About the role)
- Responsibilities
- Qualifications (or Requirements)
- Skills (maybe split Required and Preferred)
- Working Conditions (maybe brief)
- Core Values (Culture)
We need to avoid duplication.
Let's extract substantive content.
Company overview paragraph: "At Agile Defense we know that action defines the outcome and new challenges require new solutions. That’s why we always look to the future and embrace change with an unmovable spirit and the courage to build for what comes next. Our vision is to bring adaptive innovation to support our nation's most important missions through the seamless integration of advanced technologies, elite minds, and unparalleled agility—leveraging a foundation of speed, flexibility, and ingenuity to strengthen and protect our nation’s vital interests."
That's substantive.
Summary paragraph: as above.
Responsibilities: list:
- Engineer, integrate, and maintain CSOC capabilities and platforms, ensuring effective configuration management and performance optimization.
- Advance Zero Trust principles, automation, and telemetry coverage across both cloud and on-premises environments.
- Assess and test emerging technologies; develop comprehensive technical reports and implementation plans to support modernization initiatives.
We could also include "ensuring compliance with established standards, optimizing system performance, and driving continuous improvement across the enterprise security architecture." but that was in summary; but it's also a responsibility. We'll keep it maybe in responsibilities.
Qualifications:
- Required Certifications: Minimum required A+, Security+ or Network+; CISSP certification.
- Education, Background, and Years of Experience: Bachelor's Degree
Also maybe years of experience? Not explicitly stated besides "experienced". But we have "Minimum of 3 years’ experience security administration systems and support." under Required Skills.
Thus qualifications: Bachelor's Degree, certifications.
Skills:
Required Skills (list many):
- A minimum of 3 years’ experience security administration systems and support.
- Strong working knowledge of Security Services, Networking, Security Policy, and Consulting.
- Proven experience in installing, configuring, monitoring, and troubleshooting network security solutions and related monitoring tools including Layer 2 / Layer 3 network devices, Network Admission Control (NAC), 802.1x, Firewalls, IDS / IPS, VPN Solutions, Web Application Firewalls, Content Filtering, fault analysis.
- Advanced working knowledge of encryption algorithms, Operating Systems (Linux, windows), secure communications, SIEM technologies, and embedded systems security.
- Advanced working knowledge of network and data communication protocols.
- Familiar with standard concepts, practices, and procedures within a particular field such as NIST, FISMA and Common Criteria regulations and standards.
- Experience with Network based IDS / IPS technologies and affiliated modes of operation; experienced in evaluating new technologies and processes that enhance security capabilities.
- Supervise changes in software, hardware, facilities, telecommunications and user needs.
- Experience with Test security solutions using industry standard analysis criteria; experience with the delivery technical reports and formal papers on test findings; experience responding to information security issues during each stage of a project’s lifecycle to include.
- Strong scripting skills (bash PowerShell) and ability to use automation tools such as ansible, or puppet.
- Produce technical documentation, including architecture diagrams, and detailed root cause analysis reports.
Preferred Skills:
- CISSP certification (though already required? but listed as preferred)
- Experience with supporting Zero Trust Network and Operating Certifications (Cisco, Redhat, Microsoft)
- Cloud provider certifications (AWS Certified Solutions Architect, Azure Solutions Architect Expert, etc)
- Supervise changes in software, hardware, facilities, telecommunications and user needs. (duplicate)
- Excellent written and oral communication skills
Working Conditions:
- Environmental Conditions Hybrid in Reston, VA
- Strength Demands Physical Requirements (no detail) maybe we can omit as filler.
Core Values: description of 6Hs.
We need to avoid duplication: "Supervise changes..." appears twice; we can keep once.
We need to remove boilerplate: EEO, AI tools, etc.
Now produce HTML.
We'll use for each section heading.
Inside sections, use
for prose,
- for lists.
We need to preserve all substantive info; we can combine some lists.
Let's structure:
About Agile Defense
At Agile Defense we know that action defines the outcome and new challenges require new solutions. That’s why we always look to the future and embrace change with an unmovable spirit and the courage to build for what comes next. Our vision is to bring adaptive innovation to support our nation's most important missions through the seamless integration of advanced technologies, elite minds, and unparalleled agility—leveraging a foundation of speed, flexibility, and ingenuity to strengthen and protect our nation’s vital interests.
Summary
Agile Defense is seeking experienced Security Engineering Lead to support an enterprise cybersecurity program delivering 24/7 Cybersecurity Operations Center (CSOC) services. This role serves as the technical lead for SOC security engineering and modernization efforts, including the integration and sustainment of SIEM, SOAR, EDR, and IDS/IPS platforms. Responsibilities include ensuring compliance with established standards, optimizing system performance, and driving continuous improvement across the enterprise security architecture. A highly technical self-starter with excellent analytical and problem-solving skills, flexibility, good judgment and the ability to coordinate multiple, concurrent tasks in an effective manner.
Responsibilities
- Engineer, integrate, and maintain CSOC capabilities and platforms, ensuring effective configuration management and performance optimization.
- Advance Zero Trust principles, automation, and telemetry coverage across both cloud and on-premises environments.
- Assess and test emerging technologies; develop comprehensive technical reports and implementation plans to support modernization initiatives.
- Ensure compliance with established standards, optimize system performance, and drive continuous improvement across the enterprise security architecture.
Qualifications
- Required Certifications: Minimum required A+, Security+ or Network+; CISSP certification.
- Education: Bachelor's Degree.
Required Skills
- A minimum of 3 years’ experience security administration systems and support.
- Strong working knowledge of Security Services, Networking, Security Policy, and Consulting.
- Proven experience in installing, configuring, monitoring, and troubleshooting network security solutions and related monitoring tools including Layer 2 / Layer 3 network devices, Network Admission Control (NAC), 802.1x, Firewalls, IDS / IPS, VPN Solutions, Web Application Firewalls, Content Filtering, fault analysis.
- Advanced working knowledge of encryption algorithms, Operating Systems (Linux, windows), secure communications, SIEM technologies, and embedded systems security.
- Advanced working knowledge of network and data communication protocols.
- Familiar with standard concepts, practices, and procedures within a particular field such as NIST, FISMA and Common Criteria regulations and standards.
- Experience with Network based IDS / IPS technologies and affiliated modes of operation; experienced in evaluating new technologies and processes that enhance security capabilities.
- Supervise changes in software, hardware, facilities, telecommunications and user needs.
- Experience with testing security solutions using industry standard analysis criteria; experience with the delivery of technical reports and formal papers on test findings; experience responding to information security issues during each stage
for "Company Overview" but instruction says use those examples; but we can still use other headings? Safer to stick to given headings. However, we have company description that could go under "About the role"? Not exactly. Could treat as "About the role" includes company overview? Might be okay.
Alternatively, we could omit company description if not needed? But we must preserve ALL substantive information. So we need to include it somewhere.
We could create a section "About the company" using but not in list; risk of violating instruction? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we can use other headings as long as they are . Probably fine.
Thus we can have sections:
- About Agile Defense (company overview)
- Summary (maybe as part of About the role)
- Responsibilities
- Qualifications (or Requirements)
- Skills (maybe split Required and Preferred)
- Working Conditions (maybe brief)
- Core Values (Culture)
We need to avoid duplication.
Let's extract substantive content.
Company overview paragraph: "At Agile Defense we know that action defines the outcome and new challenges require new solutions. That’s why we always look to the future and embrace change with an unmovable spirit and the courage to build for what comes next. Our vision is to bring adaptive innovation to support our nation's most important missions through the seamless integration of advanced technologies, elite minds, and unparalleled agility—leveraging a foundation of speed, flexibility, and ingenuity to strengthen and protect our nation’s vital interests."
That's substantive.
Summary paragraph: as above.
Responsibilities: list:
- Engineer, integrate, and maintain CSOC capabilities and platforms, ensuring effective configuration management and performance optimization.
- Advance Zero Trust principles, automation, and telemetry coverage across both cloud and on-premises environments.
- Assess and test emerging technologies; develop comprehensive technical reports and implementation plans to support modernization initiatives.
We could also include "ensuring compliance with established standards, optimizing system performance, and driving continuous improvement across the enterprise security architecture." but that was in summary; but it's also a responsibility. We'll keep it maybe in responsibilities.
Qualifications:
- Required Certifications: Minimum required A+, Security+ or Network+; CISSP certification.
- Education, Background, and Years of Experience: Bachelor's Degree
Also maybe years of experience? Not explicitly stated besides "experienced". But we have "Minimum of 3 years’ experience security administration systems and support." under Required Skills.
Thus qualifications: Bachelor's Degree, certifications.
Skills:
Required Skills (list many):
- A minimum of 3 years’ experience security administration systems and support.
- Strong working knowledge of Security Services, Networking, Security Policy, and Consulting.
- Proven experience in installing, configuring, monitoring, and troubleshooting network security solutions and related monitoring tools including Layer 2 / Layer 3 network devices, Network Admission Control (NAC), 802.1x, Firewalls, IDS / IPS, VPN Solutions, Web Application Firewalls, Content Filtering, fault analysis.
- Advanced working knowledge of encryption algorithms, Operating Systems (Linux, windows), secure communications, SIEM technologies, and embedded systems security.
- Advanced working knowledge of network and data communication protocols.
- Familiar with standard concepts, practices, and procedures within a particular field such as NIST, FISMA and Common Criteria regulations and standards.
- Experience with Network based IDS / IPS technologies and affiliated modes of operation; experienced in evaluating new technologies and processes that enhance security capabilities.
- Supervise changes in software, hardware, facilities, telecommunications and user needs.
- Experience with Test security solutions using industry standard analysis criteria; experience with the delivery technical reports and formal papers on test findings; experience responding to information security issues during each stage of a project’s lifecycle to include.
- Strong scripting skills (bash PowerShell) and ability to use automation tools such as ansible, or puppet.
- Produce technical documentation, including architecture diagrams, and detailed root cause analysis reports.
Preferred Skills:
- CISSP certification (though already required? but listed as preferred)
- Experience with supporting Zero Trust Network and Operating Certifications (Cisco, Redhat, Microsoft)
- Cloud provider certifications (AWS Certified Solutions Architect, Azure Solutions Architect Expert, etc)
- Supervise changes in software, hardware, facilities, telecommunications and user needs. (duplicate)
- Excellent written and oral communication skills
Working Conditions:
- Environmental Conditions Hybrid in Reston, VA
- Strength Demands Physical Requirements (no detail) maybe we can omit as filler.
Core Values: description of 6Hs.
We need to avoid duplication: "Supervise changes..." appears twice; we can keep once.
We need to remove boilerplate: EEO, AI tools, etc.
Now produce HTML.
We'll use for each section heading.
Inside sections, use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not exclusive. So we can use other headings as long as they are . Probably fine.
Thus we can have sections:
- About Agile Defense (company overview)
- Summary (maybe as part of About the role)
- Responsibilities
- Qualifications (or Requirements)
- Skills (maybe split Required and Preferred)
- Working Conditions (maybe brief)
- Core Values (Culture)
We need to avoid duplication.
Let's extract substantive content.
Company overview paragraph: "At Agile Defense we know that action defines the outcome and new challenges require new solutions. That’s why we always look to the future and embrace change with an unmovable spirit and the courage to build for what comes next. Our vision is to bring adaptive innovation to support our nation's most important missions through the seamless integration of advanced technologies, elite minds, and unparalleled agility—leveraging a foundation of speed, flexibility, and ingenuity to strengthen and protect our nation’s vital interests."
That's substantive.
Summary paragraph: as above.
Responsibilities: list:
- Engineer, integrate, and maintain CSOC capabilities and platforms, ensuring effective configuration management and performance optimization.
- Advance Zero Trust principles, automation, and telemetry coverage across both cloud and on-premises environments.
- Assess and test emerging technologies; develop comprehensive technical reports and implementation plans to support modernization initiatives.
We could also include "ensuring compliance with established standards, optimizing system performance, and driving continuous improvement across the enterprise security architecture." but that was in summary; but it's also a responsibility. We'll keep it maybe in responsibilities.
Qualifications:
- Required Certifications: Minimum required A+, Security+ or Network+; CISSP certification.
- Education, Background, and Years of Experience: Bachelor's Degree
Also maybe years of experience? Not explicitly stated besides "experienced". But we have "Minimum of 3 years’ experience security administration systems and support." under Required Skills.
Thus qualifications: Bachelor's Degree, certifications.
Skills:
Required Skills (list many):
- A minimum of 3 years’ experience security administration systems and support.
- Strong working knowledge of Security Services, Networking, Security Policy, and Consulting.
- Proven experience in installing, configuring, monitoring, and troubleshooting network security solutions and related monitoring tools including Layer 2 / Layer 3 network devices, Network Admission Control (NAC), 802.1x, Firewalls, IDS / IPS, VPN Solutions, Web Application Firewalls, Content Filtering, fault analysis.
- Advanced working knowledge of encryption algorithms, Operating Systems (Linux, windows), secure communications, SIEM technologies, and embedded systems security.
- Advanced working knowledge of network and data communication protocols.
- Familiar with standard concepts, practices, and procedures within a particular field such as NIST, FISMA and Common Criteria regulations and standards.
- Experience with Network based IDS / IPS technologies and affiliated modes of operation; experienced in evaluating new technologies and processes that enhance security capabilities.
- Supervise changes in software, hardware, facilities, telecommunications and user needs.
- Experience with Test security solutions using industry standard analysis criteria; experience with the delivery technical reports and formal papers on test findings; experience responding to information security issues during each stage of a project’s lifecycle to include.
- Strong scripting skills (bash PowerShell) and ability to use automation tools such as ansible, or puppet.
- Produce technical documentation, including architecture diagrams, and detailed root cause analysis reports.
Preferred Skills:
- CISSP certification (though already required? but listed as preferred)
- Experience with supporting Zero Trust Network and Operating Certifications (Cisco, Redhat, Microsoft)
- Cloud provider certifications (AWS Certified Solutions Architect, Azure Solutions Architect Expert, etc)
- Supervise changes in software, hardware, facilities, telecommunications and user needs. (duplicate)
- Excellent written and oral communication skills
Working Conditions:
- Environmental Conditions Hybrid in Reston, VA
- Strength Demands Physical Requirements (no detail) maybe we can omit as filler.
Core Values: description of 6Hs.
We need to avoid duplication: "Supervise changes..." appears twice; we can keep once.
We need to remove boilerplate: EEO, AI tools, etc.
Now produce HTML.
We'll use for each section heading.
Inside sections, use
for each section heading. Inside sections, use
for prose,
- for lists.
We need to preserve all substantive info; we can combine some lists.
Let's structure:
About Agile Defense
At Agile Defense we know that action defines the outcome and new challenges require new solutions. That’s why we always look to the future and embrace change with an unmovable spirit and the courage to build for what comes next. Our vision is to bring adaptive innovation to support our nation's most important missions through the seamless integration of advanced technologies, elite minds, and unparalleled agility—leveraging a foundation of speed, flexibility, and ingenuity to strengthen and protect our nation’s vital interests.
Summary
Agile Defense is seeking experienced Security Engineering Lead to support an enterprise cybersecurity program delivering 24/7 Cybersecurity Operations Center (CSOC) services. This role serves as the technical lead for SOC security engineering and modernization efforts, including the integration and sustainment of SIEM, SOAR, EDR, and IDS/IPS platforms. Responsibilities include ensuring compliance with established standards, optimizing system performance, and driving continuous improvement across the enterprise security architecture. A highly technical self-starter with excellent analytical and problem-solving skills, flexibility, good judgment and the ability to coordinate multiple, concurrent tasks in an effective manner.
Responsibilities
- Engineer, integrate, and maintain CSOC capabilities and platforms, ensuring effective configuration management and performance optimization.
- Advance Zero Trust principles, automation, and telemetry coverage across both cloud and on-premises environments.
- Assess and test emerging technologies; develop comprehensive technical reports and implementation plans to support modernization initiatives.
- Ensure compliance with established standards, optimize system performance, and drive continuous improvement across the enterprise security architecture.
Qualifications
- Required Certifications: Minimum required A+, Security+ or Network+; CISSP certification.
- Education: Bachelor's Degree.
Required Skills
- A minimum of 3 years’ experience security administration systems and support.
- Strong working knowledge of Security Services, Networking, Security Policy, and Consulting.
- Proven experience in installing, configuring, monitoring, and troubleshooting network security solutions and related monitoring tools including Layer 2 / Layer 3 network devices, Network Admission Control (NAC), 802.1x, Firewalls, IDS / IPS, VPN Solutions, Web Application Firewalls, Content Filtering, fault analysis.
- Advanced working knowledge of encryption algorithms, Operating Systems (Linux, windows), secure communications, SIEM technologies, and embedded systems security.
- Advanced working knowledge of network and data communication protocols.
- Familiar with standard concepts, practices, and procedures within a particular field such as NIST, FISMA and Common Criteria regulations and standards.
- Experience with Network based IDS / IPS technologies and affiliated modes of operation; experienced in evaluating new technologies and processes that enhance security capabilities.
- Supervise changes in software, hardware, facilities, telecommunications and user needs.
- Experience with testing security solutions using industry standard analysis criteria; experience with the delivery of technical reports and formal papers on test findings; experience responding to information security issues during each stage