812262 Cyber Security Engineer $255,000.00
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists of duties/requirements/benefits, and
for prose
3. Do NOT repeat the job title as a heading (page already shows it)
4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it
5. Preserve ALL substantive information; do NOT invent or summarize away detail
6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text
8. Never create Pay/Schedule/Benefits sections unless the posting actually states them
9. Prefer a few substantive sections over many thin ones
10. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the job posting content:
**Job Title:** Cyber Security Engineer– Technical Lead (already shown on page, so don't repeat as heading)
**Metadata:**
- Labor Category: Cyber Security Engineer
- Position Level: Level 1 – Subject Matter Expert
- Salary: Up to $255,000.00 per year
- Core Hours: 9am to 4pm
- Location: Bethesda MD
- Requires Top Secret (TS/SCI) Clearance with Polygraph
- Internal Tracking: LH-SEM-003 (this is a job ID, should fold into
or drop)
**Description:** Several paragraphs about the role
**Primary Responsibilities:** List of duties
**Mandatory Requirements:** List of requirements with experience levels
**Optional Requirements:** List of optional requirements
**Company Information:** About B4Corp
**Compensation/Benefits:** Detailed benefits package
**Application instructions:** Link to application form, EEO statement, etc. (should remove)
Now I need to structure this into sections. Let me think about appropriate sections:
1. **About the role** - for the description paragraphs
2. **Responsibilities** - for primary responsibilities
3. **Requirements** - for mandatory requirements
4. **Qualifications** - could combine mandatory and optional, but they're distinct. Maybe "Requirements" for mandatory and "Preferred qualifications" for optional? The rules mention "Qualifications" as a possible heading.
5. **Benefits** - for the compensation/benefits package
6. **Pay** - salary is mentioned
7. **Schedule** - core hours mentioned
8. **Location** - Bethesda MD
9. **Clearance** - TS/SCI with polygraph
The rules say use
for section headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So I should use those standard headings where appropriate.
I need to include a section ONLY when there's real content. All these have real content.
Let me structure:
- About the role: description paragraphs
- Responsibilities: primary responsibilities list
- Requirements: mandatory requirements
- Qualifications: optional requirements (or could be "Preferred qualifications")
- Benefits: compensation and benefits details
- Pay: salary info
- Schedule: core hours
- Location: Bethesda MD
- Clearance: TS/SCI with polygraph
But the rules say "Prefer a few substantive sections over many thin ones." So maybe combine some? For example, Pay, Schedule, Location, Clearance could be in a "Position details" section? But the rules specifically list them as separate possible headings. However, the instruction says "include a section ONLY when the posting has real, specific content for it". Each has specific content.
But also "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state them.
I think I'll create sections for each distinct area. Let me map:
1. **About the role** - description
2. **Responsibilities** - primary responsibilities
3. **Requirements** - mandatory requirements
4. **Qualifications** - optional requirements (or "Preferred qualifications")
5. **Benefits** - benefits package
6. **Pay** - salary
7. **Schedule** - core hours
8. **Location** - Bethesda MD
9. **Clearance** - TS/SCI with polygraph
But "Clearance" isn't in the suggested headings list. The list includes "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". Clearance could be under "Requirements" or separate. Since it's a specific requirement, maybe include in Requirements section? But it's a clearance requirement, not a skill/experience requirement. Could be a separate "Clearance" section, but not in the suggested list. The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests these are examples, not exhaustive. But to be safe, I could include clearance in Requirements or create a "Clearance" heading. I think it's fine to have a "Clearance" heading as it's substantive.
Also, the job ID "Internal Tracking -LH-SEM-003" should be folded into a short
or dropped. I'll include it in a brief metadata paragraph at the top maybe.
The company information "B4Corp Company Information" is boilerplate about the company. Could be included in "About the role" or separate "Company" section. But the rules say remove boilerplate. However, it's specific to this company and describes their benefits philosophy. Might be worth keeping as part of benefits or a brief company note. I'll include a short paragraph in Benefits or separate.
The application instructions and EEO statement should be removed.
Now, let's write the HTML.
I'll start with a brief metadata paragraph: location, clearance, salary, schedule, job ID.
Then sections.
Let me draft:
Location: Bethesda, MD. Requires Top Secret (TS/SCI) clearance with polygraph. Salary up to $255,000/year. Core hours: 9 am–4 pm. Requisition: LH-SEM-003.
About the role
This role is responsible for protecting the customer’s information systems and networks from potential cyber-attacks. The Cyber Security Engineer– Technical Lead SME will serve in a hands-on “player-coach” capacity, dedicating approximately 75% of time to direct technical engineering, troubleshooting, and implementation work, while providing technical leadership and coordination across the security team. The candidate must display an excellent understanding of technology and utilization of Firewalls (Security Groups), VPNs, Data Loss Prevention (DPS), IDS/IPS, Web-Proxy, Security tools, and Security Audits. Candidate will work directly with Team leads, developers, operations personnel, and other Technical Leads throughout a DevSecOps life cycle both on policy and technical implementation of technologies. This is not a supervisory management role. Success in this position is measured by individual technical contribution and resolution of complex security issues, in addition to technical leadership impact.
Responsibilities
- Plan, implement, manage, monitor, and upgrade security controls and tools used to protect enterprise systems and networks, while identifying opportunities to automate repeatable operations tasks.
- Design, configure, implement, troubleshoot, and maintain security technologies such as firewalls (security groups), endpoint protection tools (HBSS/Trellix), SIEM platforms (Splunk).
- Formulate systems and methodologies as well as respond to security related events and assist in remediation efforts of cyber security incidents (system and/or network breaches, malware attacks).
- Participate in change management processes to ensure system changes maintain security compliance and do not introduce new vulnerabilities.
- Conduct routine vulnerability scanning and assessment activities, provide formal and informal reports to technical teams, and track remediation efforts to closure.
- Provide technical leadership and subject matter expertise to the security engineering team while coordinating with peer Technical Leads across infrastructure and application domains to ensure alignment of architecture and security controls.
- Serve as the primary technical escalation point for complex or cross-domain security issues while mentoring junior engineers through collaborative troubleshooting and hands-on technical guidance.
Requirements
- Experience implementing and managing Security Information and Event Management (SIEM) tools such as Splunk or similar platforms.
- Experience working with endpoint and network security technologies, including IDS/IPS, HBSS/Trellix, and related defensive security tools.
- Expert with automation (e.g., Ansible, CloudFormation).
- Demonstrated history of personally implementing, troubleshooting, and maintaining security technologies in production environments.
- Proven ability to balance technical leadership responsibilities with significant hands-on engineering work.
- Strong attention to detail with analytical mind and outstanding problem-solving skills.
- Monitor security advisories, bulletins, and industry threat intelligence to stay informed of current vulnerabilities, threats, and trends.
- Requires BS degree and 16 or more years of prior relevant experience, or MS degree and 14 or more years of prior relevant experience.
Qualifications
- Experience with additional security tools and processes such as IDS/IPS, VPN, GitHub, GitLab, SonarQube.
- Experience with implementing and managing network and application firewalls, virtual private networks, firewalls, web protocols, incident detection, incident response, and forensics activities.
- Experience with Agile software development processes/environments, scripting/programming languages such as Python or PowerShell.
- Experience with DevOpsSec pipelines and tools.
- Familiar with Cloud Computing Technologies and Services (AWS, Oracle, Google).
- Knowledge of potential attack vectors such as XSS, injection, hijacking and social engineering.
- Experience with health monitoring tools (SolarWinds) and using STIG viewers/tools to assess compliance with standards.
- Experience with database systems, search engines, web applications, Linux Red Hat environments, Windows environment.
Benefits
B4Corp provides a low overhead, highly efficient, high salary environment with a cafeteria-style benefit plan that allows employees to maximize their Benefit Dollars.
- Outstanding salaries
- Retirement: Full Vanguard 401k Plan – 100% employer matched contribution up to 6% of employee’s salary; ability to max out 401k savings $57k ($63.5k if over 50)
- Employees receive B4Corp phantom stock each year (2-year vesting period)
- Insurance: Medical – United Health Care (multiple plan options); Dental – United Concordia Flex Plan; Vision – Vision Service Plan Signature Plans
- Mutual of Omaha short-term disability (60% of salary up to $2,000/week)
- Mutual of Omaha long-term disability (60% of salary up to $10,000/month)
for prose 3. Do NOT repeat the job title as a heading (page already shows it) 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: **Job Title:** Cyber Security Engineer– Technical Lead (already shown on page, so don't repeat as heading) **Metadata:** - Labor Category: Cyber Security Engineer - Position Level: Level 1 – Subject Matter Expert - Salary: Up to $255,000.00 per year - Core Hours: 9am to 4pm - Location: Bethesda MD - Requires Top Secret (TS/SCI) Clearance with Polygraph - Internal Tracking: LH-SEM-003 (this is a job ID, should fold into
or drop) **Description:** Several paragraphs about the role **Primary Responsibilities:** List of duties **Mandatory Requirements:** List of requirements with experience levels **Optional Requirements:** List of optional requirements **Company Information:** About B4Corp **Compensation/Benefits:** Detailed benefits package **Application instructions:** Link to application form, EEO statement, etc. (should remove) Now I need to structure this into sections. Let me think about appropriate sections: 1. **About the role** - for the description paragraphs 2. **Responsibilities** - for primary responsibilities 3. **Requirements** - for mandatory requirements 4. **Qualifications** - could combine mandatory and optional, but they're distinct. Maybe "Requirements" for mandatory and "Preferred qualifications" for optional? The rules mention "Qualifications" as a possible heading. 5. **Benefits** - for the compensation/benefits package 6. **Pay** - salary is mentioned 7. **Schedule** - core hours mentioned 8. **Location** - Bethesda MD 9. **Clearance** - TS/SCI with polygraph The rules say use
for section headings like "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". So I should use those standard headings where appropriate.
I need to include a section ONLY when there's real content. All these have real content.
Let me structure:
- About the role: description paragraphs
- Responsibilities: primary responsibilities list
- Requirements: mandatory requirements
- Qualifications: optional requirements (or could be "Preferred qualifications")
- Benefits: compensation and benefits details
- Pay: salary info
- Schedule: core hours
- Location: Bethesda MD
- Clearance: TS/SCI with polygraph
But the rules say "Prefer a few substantive sections over many thin ones." So maybe combine some? For example, Pay, Schedule, Location, Clearance could be in a "Position details" section? But the rules specifically list them as separate possible headings. However, the instruction says "include a section ONLY when the posting has real, specific content for it". Each has specific content.
But also "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting does state them.
I think I'll create sections for each distinct area. Let me map:
1. **About the role** - description
2. **Responsibilities** - primary responsibilities
3. **Requirements** - mandatory requirements
4. **Qualifications** - optional requirements (or "Preferred qualifications")
5. **Benefits** - benefits package
6. **Pay** - salary
7. **Schedule** - core hours
8. **Location** - Bethesda MD
9. **Clearance** - TS/SCI with polygraph
But "Clearance" isn't in the suggested headings list. The list includes "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". Clearance could be under "Requirements" or separate. Since it's a specific requirement, maybe include in Requirements section? But it's a clearance requirement, not a skill/experience requirement. Could be a separate "Clearance" section, but not in the suggested list. The rules say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". The "e.g." suggests these are examples, not exhaustive. But to be safe, I could include clearance in Requirements or create a "Clearance" heading. I think it's fine to have a "Clearance" heading as it's substantive.
Also, the job ID "Internal Tracking -LH-SEM-003" should be folded into a short
or dropped. I'll include it in a brief metadata paragraph at the top maybe. The company information "B4Corp Company Information" is boilerplate about the company. Could be included in "About the role" or separate "Company" section. But the rules say remove boilerplate. However, it's specific to this company and describes their benefits philosophy. Might be worth keeping as part of benefits or a brief company note. I'll include a short paragraph in Benefits or separate. The application instructions and EEO statement should be removed. Now, let's write the HTML. I'll start with a brief metadata paragraph: location, clearance, salary, schedule, job ID. Then sections. Let me draft:
Location: Bethesda, MD. Requires Top Secret (TS/SCI) clearance with polygraph. Salary up to $255,000/year. Core hours: 9 am–4 pm. Requisition: LH-SEM-003.
About the role
This role is responsible for protecting the customer’s information systems and networks from potential cyber-attacks. The Cyber Security Engineer– Technical Lead SME will serve in a hands-on “player-coach” capacity, dedicating approximately 75% of time to direct technical engineering, troubleshooting, and implementation work, while providing technical leadership and coordination across the security team. The candidate must display an excellent understanding of technology and utilization of Firewalls (Security Groups), VPNs, Data Loss Prevention (DPS), IDS/IPS, Web-Proxy, Security tools, and Security Audits. Candidate will work directly with Team leads, developers, operations personnel, and other Technical Leads throughout a DevSecOps life cycle both on policy and technical implementation of technologies. This is not a supervisory management role. Success in this position is measured by individual technical contribution and resolution of complex security issues, in addition to technical leadership impact.
Responsibilities
- Plan, implement, manage, monitor, and upgrade security controls and tools used to protect enterprise systems and networks, while identifying opportunities to automate repeatable operations tasks.
- Design, configure, implement, troubleshoot, and maintain security technologies such as firewalls (security groups), endpoint protection tools (HBSS/Trellix), SIEM platforms (Splunk).
- Formulate systems and methodologies as well as respond to security related events and assist in remediation efforts of cyber security incidents (system and/or network breaches, malware attacks).
- Participate in change management processes to ensure system changes maintain security compliance and do not introduce new vulnerabilities.
- Conduct routine vulnerability scanning and assessment activities, provide formal and informal reports to technical teams, and track remediation efforts to closure.
- Provide technical leadership and subject matter expertise to the security engineering team while coordinating with peer Technical Leads across infrastructure and application domains to ensure alignment of architecture and security controls.
- Serve as the primary technical escalation point for complex or cross-domain security issues while mentoring junior engineers through collaborative troubleshooting and hands-on technical guidance.
Requirements
- Experience implementing and managing Security Information and Event Management (SIEM) tools such as Splunk or similar platforms.
- Experience working with endpoint and network security technologies, including IDS/IPS, HBSS/Trellix, and related defensive security tools.
- Expert with automation (e.g., Ansible, CloudFormation).
- Demonstrated history of personally implementing, troubleshooting, and maintaining security technologies in production environments.
- Proven ability to balance technical leadership responsibilities with significant hands-on engineering work.
- Strong attention to detail with analytical mind and outstanding problem-solving skills.
- Monitor security advisories, bulletins, and industry threat intelligence to stay informed of current vulnerabilities, threats, and trends.
- Requires BS degree and 16 or more years of prior relevant experience, or MS degree and 14 or more years of prior relevant experience.
Qualifications
- Experience with additional security tools and processes such as IDS/IPS, VPN, GitHub, GitLab, SonarQube.
- Experience with implementing and managing network and application firewalls, virtual private networks, firewalls, web protocols, incident detection, incident response, and forensics activities.
- Experience with Agile software development processes/environments, scripting/programming languages such as Python or PowerShell.
- Experience with DevOpsSec pipelines and tools.
- Familiar with Cloud Computing Technologies and Services (AWS, Oracle, Google).
- Knowledge of potential attack vectors such as XSS, injection, hijacking and social engineering.
- Experience with health monitoring tools (SolarWinds) and using STIG viewers/tools to assess compliance with standards.
- Experience with database systems, search engines, web applications, Linux Red Hat environments, Windows environment.
Benefits
B4Corp provides a low overhead, highly efficient, high salary environment with a cafeteria-style benefit plan that allows employees to maximize their Benefit Dollars.
- Outstanding salaries
- Retirement: Full Vanguard 401k Plan – 100% employer matched contribution up to 6% of employee’s salary; ability to max out 401k savings $57k ($63.5k if over 50)
- Employees receive B4Corp phantom stock each year (2-year vesting period)
- Insurance: Medical – United Health Care (multiple plan options); Dental – United Concordia Flex Plan; Vision – Vision Service Plan Signature Plans
- Mutual of Omaha short-term disability (60% of salary up to $2,000/week)
- Mutual of Omaha long-term disability (60% of salary up to $10,000/month)