Threat Emulation Engineer - Blue/Purple Team

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. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate. Must preserve all substantive info. We need to parse the posting. Job title: Threat Emulation Engineer (but we don't repeat as heading). We'll have sections. First, "General Description" paragraph: "We are looking for a skilled Threat Emulation Engineer to support service delivery and be a product subject-matter expert, working independently on small projects and collaboratively on large-scale enterprise deployments. This role will engage in large internal support group with extensive experience and benefit from our internal training program designed to increase your skills and keep pace with technology changes. We focus on enabling our engineers to become complete security professionals able to analyze security solutions, not just install and configure products. You'll gain a broad spectrum of knowledge and skills that allow you to give advice and direction relevant to today's threats. No Prior Experience with Automated Security Validation Required: While experience with Mandiant Security Validation Tool would be great, we'll train you on the tool if you have a solid foundation in cybersecurity. We're vendor neutral security engineers providing services that meet customer needs, not our own or that of vendors." That's about the role. Could be "About the role" section. Then "About the Federal Region" paragraph: describing GuidePoint Security as trusted partner for defense and civilian government agencies, etc. That could be part of About the role or maybe separate? But we only have set headings; we could put that under About the role as well. Then "Roles and Responsibilities" list: bullet points. Then "Required Experience and Education": list of mandatory requirements. Then "Preferred Experience and Education": list. Then "Travel Requirements: This position requires 100% onsite support in Chantilly, VA". That's location, maybe part of Requirements or Qualifications? Could be under Requirements. Then "Physical Requirements": bullet points. Then "Why GuidePoint?" paragraph about company, perks: includes benefits: remote workforce primarily, group medical insurance options, dental, holidays, FTO, mobile/internet allowance, retirement eligibility, pet benefit option. That's benefits. Pay: not mentioned. Schedule: not mentioned (though maybe implied 100% onsite). But we should not create Pay/Schedule sections unless posting actually states them. No pay info. So omit Pay and Schedule. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits. Possibly also include "Qualifications" separate from Requirements? The posting has Required Experience and Education (mandatory) and Preferred Experience and Education (preferred). Could map Required to Requirements, Preferred to Qualifications? Or Skills could be derived from required/preferred. But we must not invent sections with filler. We need to decide which sections have real content. We have content for About the role (general description + Federal region). Responsibilities (list). Requirements (mandatory). Qualifications (preferred). Skills (maybe we could list specific skills like proficiency with Windows, macOS, Linux, networking, scripting languages, etc.) But those are already in Requirements/Preferred. Could combine. Better to follow typical structure: About the role, Responsibilities, Requirements, Qualifications, Benefits. Skills maybe not needed if covered. But the instruction says use those headings if content exists. We can include Skills if we have specific skill list not covered elsewhere. The posting includes: "Proficiency with Windows, macOS, and Linux systems.", "Experience with networking and security troubleshooting (firewalls, routing, NAT, etc.)", "Ability to manage and deliver multiple projects independently.", "Embraces emerging technologies, including AI tools". Also "Familiarity with various scripting languages (bash, python, powershell, perl)". Those could be skills. We could put them under Skills. Requirements: mandatory clearance, 5-10 years experience, DoD 8570 IAT Level II+, understanding of cyber threat techniques, MITRE ATT&CK, log ingestion, key security events, etc. Qualifications: preferred: bachelor's degree, SIEM, OS auditing, Mandiant Security Validation, red/purple team, SOC runbooks, scripting languages (already maybe), etc. But we must avoid duplication. Let's decide: - About the role: combine general description and Federal region paragraph. - Responsibilities: list from "Roles and Responsibilities". - Requirements: mandatory items (clearance, years experience, DoD 8570, understanding of threat techniques, MITRE ATT&CK, log ingestion, key security events, proficiency with OS, networking troubleshooting, manage multiple projects, embraces emerging tech). Also maybe "Active DoD 8570 IAT Level II+ certification (e.g., Security+, CEH)". Also "Strong understanding of cyber threat techniques, intelligence analysis, and adversary TTPs." etc. - Qualifications: preferred items (Bachelor's degree, SIEM, OS auditing, Mandiant Security Validation, red/purple team, SOC runbooks, scripting languages). Also maybe "Experience configuring and utilizing enterprise SIEM platforms." etc. - Skills: maybe we could list specific technical skills: Windows/macOS/Linux proficiency, networking/security troubleshooting, scripting languages, etc. But some overlap with Requirements/Qualifications. To avoid duplication, we could put skills that are not already covered: e.g., "Proficiency with Windows, macOS, and Linux systems." is in Requirements? Actually we have "Proficiency with Windows, macOS, and Linux systems." under Required Experience and Education? Yes it's listed there. So it's already in Requirements. Similarly networking troubleshooting is there. Scripting languages is in Preferred. So Skills may be redundant. Could omit Skills section. - Benefits: from "Why GuidePoint?" includes remote workforce primarily (U.S. based only, some travel may be required for certain positions, working on-site may be required for Federal positions) – but note this position requires 100% onsite support in Chantilly, VA, so remote not applicable? But still it's a benefit description. We'll include the benefits as listed: Group Medical Insurance options (Zero Deductible PPO Plan, High Deductible Health Plan with HSA), Group Dental Insurance, 12 corporate holidays and Flexible Time Off (FTO) program, Healthy mobile phone and home internet allowance, Eligibility for retirement plan after 2 months at open enrollment, Pet Benefit Option. Also mention "Remote workforce primarily (U.S. based only, some travel may be required for certain positions, working on-site may be required for Federal positions)" but given this role is 100% onsite, maybe we still include but note it's not applicable? Better to include as is; it's part of benefits description. We must not include boilerplate like EEO, legal, etc. Also remove "Applicants selected will be subject to a security investigation..." that's maybe part of Requirements? It's about clearance; but it's a statement about security investigation. Could be included under Requirements as note. But it's not a requirement per se; it's a condition. Might keep as part of Requirements. Also remove "We use Greenhouse Software..." and scheduling instructions. Now craft HTML. We'll use

for each section heading. Inside sections: use

for prose,

• for lists. We need to preserve all substantive information; do not invent or summarize away detail. Let's extract exact sentences. About the role: Paragraph 1: "We are looking for a skilled Threat Emulation Engineer to support service delivery and be a product subject-matter expert, working independently on small projects and collaboratively on large-scale enterprise deployments. This role will engage in large internal support group with extensive experience and benefit from our internal training program designed to increase your skills and keep pace with technology changes. We focus on enabling our engineers to become complete security professionals able to analyze security solutions, not just install and configure products. You'll gain a broad spectrum of knowledge and skills that allow you to give advice and direction relevant to today's threats. No Prior Experience with Automated Security Validation Required: While experience with Mandiant Security Validation Tool would be great, we'll train you on the tool if you have a solid foundation in cybersecurity. We're vendor neutral security engineers providing services that meet customer needs, not our own or that of vendors." Paragraph 2 (About the Federal Region): "GuidePoint Security is the trusted partner that defense and civilian government agencies rely on to lead their cybersecurity efforts and protect their organizations. We help solve their most complex security challenges, mature security architectures, and proactively reduce risk. Our purpose-built solutions ensure compliance, safeguard critical assets, and align security with organizational objectives. Backed by deep expertise, strong partnerships, and advanced technologies, we deliver scalable, adaptive capabilities that evolve with the threat landscape so Federal agencies can lead with confidence and protect what's next." We'll combine into one

  maybe two paragraphs. Responsibilities: list from "Roles and Responsibilities": - Complete internal training for Automated Security Validation (ASV). - Lead complex ASV deployments and partner with customers to address diverse security use cases. - Assess customer security posture and requirements to guide solution design. - Maximize ASV value by enabling customers and supporting their cybersecurity strategy. - Collaborate with internal product and technical teams to deliver solutions and drive innovation. - Apply prior experience, share best practices, and develop creative approaches to increase adoption. - Empower customers to independently address future security questions. Each as

• . Requirements (mandatory): - Candidates MUST have an active Top Secret/SCI clearance with a CI Poly within 10 years for consideration. - 5–10 years of security systems engineering and troubleshooting experience. - Active DoD 8570 IAT Level II+ certification (e.g., Security+, CEH). - Strong understanding of cyber threat techniques, intelligence analysis, and adversary TTPs. - Familiarity with MITRE ATT&CK and similar threat frameworks. - Experience designing log ingestion and aggregation strategies. - Knowledge of key security events across common IT platforms. - Proficiency with Windows, macOS, and Linux systems. - Experience with networking and security troubleshooting (firewalls, routing, NAT, etc.). - Ability to manage and deliver multiple projects independently. - Embraces emerging technologies, including AI tools, to work smarter, solve problems, and drive better business outcomes. - Applicants selected will be subject to a security investigation and must meet eligibility requirements for access to classified information. (maybe include as note) Qualifications (preferred): - Bachelor's degree in a relevant field or equivalent experience. - Experience configuring and utilizing enterprise SIEM platforms. - Understanding of OS auditing (Syslog, Windows Event Logs). - Experience with Mandiant Security Validation or other Breach and Attack Simulation (BAS) tools. - Red or purple team experience. - Experience developing SOC runbooks, workflows, and policy documentation. - Familiarity with various scripting languages (bash, python, powershell, perl). Travel Requirements: "This position requires 100% onsite support in Chantilly, VA". Could be under Requirements or maybe a separate note. Since we have no specific heading for location, we could add a

  under Requirements or maybe under About the role? Probably better to add a short note under Requirements as a paragraph: "Travel Requirements: This position requires 100% onsite support in Chantilly, VA." Physical Requirements: list: - Sedentary work - Substantial movement of the wrists, hands, and/or fingers for a minimum of 8 hours a day - Required to have close visual acuity to view computer terminal and/or extensive reading for a minimum of 8 hours a day - If you have additional physical requirements/changes, please discuss with HR first We could include Physical Requirements under Requirements or maybe as its own section? Not in list of allowed headings; but we could fold into Requirements as a paragraph. However the instruction says we can only use those headings; we can still include other content under those headings. So we can add Physical Requirements as a

  under Requirements. Benefits: from "Why GuidePoint?" paragraph: - Remote workforce primarily (