Splunk & Cyber Engineer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Include a section only when posting has real specific content for it; never emit heading with filler placeholder. Prefer few substantive sections over many thin ones.
We need to parse the job description.
Key content:
- Type of Requisition: Regular (metadata)
- Clearance Level Must Currently Possess: Secret
- Clearance Level Must Be Able To Obtain: Secret (maybe duplicate)
- Public Trust/Other Required: None
- Job Family: Cyber and IT Risk Management
- Skills: (list?) Actually "Skills:" then "Job Qualifications:" then list: Splunk Administration, Splunk Enterprise Security, Splunk Infrastructure Monitoring, Teamwork and Cooperation
- Certifications: None
- Experience: 5+ years of related experience
- US Citizenship Required: Yes
Then job description paragraphs: "MEANINGFUL WORK AND PERSONAL IMPACT ..." etc.
Then "HOW A SPLUNK & CYBER ENGINEER WILL MAKE AN IMPACT" (maybe heading but we treat as part of description)
Then "Duties And Responsibilities:" with bullet list (multiple lines). Then "Additional Responsibilities:" with bullet list.
Then "WHAT YOU’LL NEED TO SUCCEED" with sub-sections: Certification, Experience, Required Skills (list), Desired Skills (list). Also "Security clearance level: Secret", "US citizenship required".
Then "GDIT IS YOUR PLACE" with bullet-like paragraphs: Growth, Support, Rewards, Community, Access to cutting‑edge technology, salary range, Scheduled Weekly Hours: 40, Travel Required: Less than 10%, Telecommuting Options: Onsite Work Location: USA FL MacDill AFB, Additional Work Locations: (maybe none). Then "Total Rewards At GDIT:" with benefits description.
Then "Our Identity Verification Process:" etc (maybe boilerplate? It's about identity verification; could be considered boilerplate but it's specific to hiring process; but instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Identity verification might be considered legal? Might be considered boilerplate but it's specific. Safer to keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Identity verification is legal-ish but not exactly EEO. Might be considered legal boilerplate. Safer to remove? However it's part of hiring process details; but they said remove legal boilerplate. I'd remove that section.
Then "About Our Work:" etc (company description) maybe boilerplate but could be considered about the company; but it's generic. Might be considered boilerplate. Probably remove.
We need to decide sections: We can have sections: About the role (the meaningful work paragraph), Responsibilities (duties and responsibilities + additional responsibilities), Requirements (maybe combine qualifications, experience, citizenship, clearance), Skills (required and desired skills), Benefits (Total Rewards description), Pay (salary range), Schedule (Scheduled Weekly Hours, Travel, Telecommuting). Also maybe "Qualifications" separate? But we can combine.
We must not create sections with filler like "not specified". We have actual content for each.
We need to use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. So no heading for the job title.
We must not put Job ID/requisition numbers as headings.
We need to preserve all substantive info.
Let's extract substantive info:
About the role: "MEANINGFUL WORK AND PERSONAL IMPACT As a Splunk & Cyber Engineer supporting USCENTCOM, you will play a pivotal role in enabling data‑driven cyber operations and accelerating the command’s ability to detect, respond to, and mitigate threats. You will lead the engineering, deployment, and optimization of Splunk Enterprise and Splunk Enterprise Security (ES) solutions that support high‑tempo operations and mission‑critical decision‑making."
Also maybe "HOW A SPLUNK & CYBER ENGINEER WILL MAKE AN IMPACT" but that's just a heading; we can incorporate into about the role.
We could combine that paragraph as about the role.
Responsibilities: Duties And Responsibilities list:
- Lead the design, deployment, and administration of Splunk Enterprise, Splunk ES, and Splunk ITSI across complex, multi‑classification environments supporting CENTCOM missions.
- Engineer end‑to‑end data ingestion pipelines, including onboarding, parsing, CIM normalization, correlation rule development, and integration with enterprise security tools.
- Develop advanced dashboards, alerts, analytics, and automation to support threat hunting, incident response, and operational reporting for the Joint Cyber Center (JCC).
- Conduct performance tuning, capacity planning, system hardening, and lifecycle management of Splunk infrastructure to ensure high availability and resilience.
- Collaborate with cybersecurity, network, and systems engineering teams to integrate Splunk with SIEM/SOAR platforms, mission systems, and emerging technologies.
- Perform vulnerability analysis, risk assessments, and forensic support using Splunk‑based analytics and data models.
- Translate CENTCOM operational requirements into scalable, secure, and cost‑effective Splunk solutions aligned with mission priorities.
- Build trusted relationships with CENTCOM stakeholders, providing expert guidance and mentoring junior engineers.
- May serve as a team or task lead, guiding technical execution and ensuring alignment with operational and cybersecurity objectives.
Additional Responsibilities:
- Provide engineering support during system deployment and integration projects.
- Participate in performance tuning and optimization to maximize system efficiency and uptime.
- Research and implement best practices and new technologies to improve system capabilities.
We can combine both lists under Responsibilities.
Requirements/Qualifications: We have:
- Type of Requisition: Regular (maybe not needed)
- Clearance Level Must Currently Possess: Secret
- Clearance Level Must Be Able To Obtain: Secret (maybe redundant)
- Public Trust/Other Required: None (maybe not needed)
- Job Family: Cyber and IT Risk Management (maybe not needed)
- Skills: (list) Splunk Administration, Splunk Enterprise Security, Splunk Infrastructure Monitoring, Teamwork and Cooperation (these are under Job Qualifications)
- Certifications: None
- Experience: 5 + years of related experience
- US Citizenship Required: Yes
- Certification: DoD 8140 or DoD 8570 Certification (or equivalent) (under WHAT YOU’LL NEED TO SUCCEED)
- Experience: 5+ years of related experience (again)
- Required Skills list (under WHAT YOU’LL NEED TO SUCCEED):
- Extensive experience in systems engineering and infrastructure management.
- Strong understanding of virtualization technologies (e.g., VMware, Hyper-V) and cloud-based solutions.
- Expertise in networking protocols, security technologies, and firewalls.
- Advanced proficiency in scripting (PowerShell, Python) for automation and system management tasks.
- Demonstrated ability to troubleshoot and resolve complex infrastructure issues.
- Experience in preparing detailed system documentation and operational procedures.
- Familiarity with Infrastructure as Code (IaC) principles and tools.
- Strong collaboration and communication skills for working with cross-functional teams.
- Desired Skills list:
- Familiarity with USCENTCOM's mission and operations.
- Proficiency in SPL (Search Processing Language)
- Experience with CIM mapping, data modeling, and correlation searches
- Strong Linux administration skills
- Familiarity with Python, REST APIs, and automation frameworks
- Understanding of enterprise cybersecurity tools, SIEM/SOAR, and network architecture
- Experience supporting classified environments and secure enclaves
- Proven ability to design and implement disaster recovery strategies.
- Hands-on experience with configuration management tools (e.g., Ansible, Puppet).
Also Security clearance level: Secret (again)
US citizenship required (again)
We need to avoid duplication but preserve all substantive info. We can combine.
We should not include "Certifications: None" as a separate bullet if it's just "None". Might be considered filler? It's substantive but says none. Could be included as a note. But we could omit if it's just "None". However instruction: preserve ALL substantive information; do NOT invent or summarize away detail. "None" is substantive. So we should include it.
Similarly "Public Trust/Other Required: None" maybe we can include but it's not needed.
We need to decide sections: Perhaps we have:
- About the role (prose)
- Responsibilities (list)
- Qualifications (list) (including required skills, desired skills, certifications, experience, citizenship, clearance)
- Benefits (list) (Total Rewards description)
- Pay (salary range)
- Schedule (weekly hours, travel, telecommuting)
We must not create sections with filler placeholder. All have content.
Now we need to format.
We'll output HTML fragment like:
About the role
...
Responsibilities
- ...
...
Qualifications
- ...
...
But qualifications includes multiple subcategories; we could still list each as separate - . Could also have nested lists but not required.
We need to ensure we don't duplicate content. Let's compile unique bullet points.
First, gather all qualification-related items:
- Type of Requisition: Regular (maybe not needed but it's metadata; could be omitted as not substantive? It's a detail but maybe minor. The instruction says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So we can drop Type of Requisition.
- Clearance Level Must Currently Possess: Secret
- Clearance Level Must Be Able To Obtain: Secret (duplicate)
- Public Trust/Other Required: None (maybe drop as minor)
- Job Family: Cyber and IT Risk Management (maybe drop as minor)
- Skills: Splunk Administration, Splunk Enterprise Security, Splunk Infrastructure Monitoring, Teamwork and Cooperation (these are under Job Qualifications)
- Certifications: None
- Experience: 5+ years of related experience
- US Citizenship Required: Yes
- Certification: DoD 8140 or DoD 8570 Certification (or equivalent)
- Required Skills (list as above)
- Desired Skills (list as above)
- Security clearance level: Secret (duplicate)
- US citizenship required (duplicate)
We need to avoid duplication but preserve all substantive info. We can combine duplicates into one bullet.
Let's create a qualifications list with distinct items:
- Secret clearance (currently possess and able to obtain)
- US citizenship required
- 5+ years of related experience
- DoD 8140 or DoD 8570 Certification (or equivalent)
- Splunk Administration
- Splunk Enterprise Security
- Splunk Infrastructure Monitoring
- Teamwork and Cooperation
- Extensive experience in systems engineering and infrastructure management.
- Strong understanding of virtualization technologies (e.g., VMware, Hyper-V) and cloud-based solutions.
- Expertise in networking protocols, security technologies, and firewalls.
- Advanced proficiency in scripting (PowerShell, Python) for automation and system management tasks.
- Demonstrated ability to troubleshoot and resolve complex infrastructure issues.
- Experience in preparing detailed system documentation and operational procedures.
- Familiarity with Infrastructure as Code (IaC) principles and tools.
- Strong collaboration and communication skills for working with cross-functional teams.
- Famil
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Include a section only when posting has real specific content for it; never emit heading with filler placeholder. Prefer few substantive sections over many thin ones. We need to parse the job description. Key content: - Type of Requisition: Regular (metadata) - Clearance Level Must Currently Possess: Secret - Clearance Level Must Be Able To Obtain: Secret (maybe duplicate) - Public Trust/Other Required: None - Job Family: Cyber and IT Risk Management - Skills: (list?) Actually "Skills:" then "Job Qualifications:" then list: Splunk Administration, Splunk Enterprise Security, Splunk Infrastructure Monitoring, Teamwork and Cooperation - Certifications: None - Experience: 5+ years of related experience - US Citizenship Required: Yes Then job description paragraphs: "MEANINGFUL WORK AND PERSONAL IMPACT ..." etc. Then "HOW A SPLUNK & CYBER ENGINEER WILL MAKE AN IMPACT" (maybe heading but we treat as part of description) Then "Duties And Responsibilities:" with bullet list (multiple lines). Then "Additional Responsibilities:" with bullet list. Then "WHAT YOU’LL NEED TO SUCCEED" with sub-sections: Certification, Experience, Required Skills (list), Desired Skills (list). Also "Security clearance level: Secret", "US citizenship required". Then "GDIT IS YOUR PLACE" with bullet-like paragraphs: Growth, Support, Rewards, Community, Access to cutting‑edge technology, salary range, Scheduled Weekly Hours: 40, Travel Required: Less than 10%, Telecommuting Options: Onsite Work Location: USA FL MacDill AFB, Additional Work Locations: (maybe none). Then "Total Rewards At GDIT:" with benefits description. Then "Our Identity Verification Process:" etc (maybe boilerplate? It's about identity verification; could be considered boilerplate but it's specific to hiring process; but instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Identity verification might be considered legal? Might be considered boilerplate but it's specific. Safer to keep? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." Identity verification is legal-ish but not exactly EEO. Might be considered legal boilerplate. Safer to remove? However it's part of hiring process details; but they said remove legal boilerplate. I'd remove that section. Then "About Our Work:" etc (company description) maybe boilerplate but could be considered about the company; but it's generic. Might be considered boilerplate. Probably remove. We need to decide sections: We can have sections: About the role (the meaningful work paragraph), Responsibilities (duties and responsibilities + additional responsibilities), Requirements (maybe combine qualifications, experience, citizenship, clearance), Skills (required and desired skills), Benefits (Total Rewards description), Pay (salary range), Schedule (Scheduled Weekly Hours, Travel, Telecommuting). Also maybe "Qualifications" separate? But we can combine. We must not create sections with filler like "not specified". We have actual content for each. We need to use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. So no heading for the job title.
We must not put Job ID/requisition numbers as headings.
We need to preserve all substantive info.
Let's extract substantive info:
About the role: "MEANINGFUL WORK AND PERSONAL IMPACT As a Splunk & Cyber Engineer supporting USCENTCOM, you will play a pivotal role in enabling data‑driven cyber operations and accelerating the command’s ability to detect, respond to, and mitigate threats. You will lead the engineering, deployment, and optimization of Splunk Enterprise and Splunk Enterprise Security (ES) solutions that support high‑tempo operations and mission‑critical decision‑making."
Also maybe "HOW A SPLUNK & CYBER ENGINEER WILL MAKE AN IMPACT" but that's just a heading; we can incorporate into about the role.
We could combine that paragraph as about the role.
Responsibilities: Duties And Responsibilities list:
- Lead the design, deployment, and administration of Splunk Enterprise, Splunk ES, and Splunk ITSI across complex, multi‑classification environments supporting CENTCOM missions.
- Engineer end‑to‑end data ingestion pipelines, including onboarding, parsing, CIM normalization, correlation rule development, and integration with enterprise security tools.
- Develop advanced dashboards, alerts, analytics, and automation to support threat hunting, incident response, and operational reporting for the Joint Cyber Center (JCC).
- Conduct performance tuning, capacity planning, system hardening, and lifecycle management of Splunk infrastructure to ensure high availability and resilience.
- Collaborate with cybersecurity, network, and systems engineering teams to integrate Splunk with SIEM/SOAR platforms, mission systems, and emerging technologies.
- Perform vulnerability analysis, risk assessments, and forensic support using Splunk‑based analytics and data models.
- Translate CENTCOM operational requirements into scalable, secure, and cost‑effective Splunk solutions aligned with mission priorities.
- Build trusted relationships with CENTCOM stakeholders, providing expert guidance and mentoring junior engineers.
- May serve as a team or task lead, guiding technical execution and ensuring alignment with operational and cybersecurity objectives.
Additional Responsibilities:
- Provide engineering support during system deployment and integration projects.
- Participate in performance tuning and optimization to maximize system efficiency and uptime.
- Research and implement best practices and new technologies to improve system capabilities.
We can combine both lists under Responsibilities.
Requirements/Qualifications: We have:
- Type of Requisition: Regular (maybe not needed)
- Clearance Level Must Currently Possess: Secret
- Clearance Level Must Be Able To Obtain: Secret (maybe redundant)
- Public Trust/Other Required: None (maybe not needed)
- Job Family: Cyber and IT Risk Management (maybe not needed)
- Skills: (list) Splunk Administration, Splunk Enterprise Security, Splunk Infrastructure Monitoring, Teamwork and Cooperation (these are under Job Qualifications)
- Certifications: None
- Experience: 5 + years of related experience
- US Citizenship Required: Yes
- Certification: DoD 8140 or DoD 8570 Certification (or equivalent) (under WHAT YOU’LL NEED TO SUCCEED)
- Experience: 5+ years of related experience (again)
- Required Skills list (under WHAT YOU’LL NEED TO SUCCEED):
- Extensive experience in systems engineering and infrastructure management.
- Strong understanding of virtualization technologies (e.g., VMware, Hyper-V) and cloud-based solutions.
- Expertise in networking protocols, security technologies, and firewalls.
- Advanced proficiency in scripting (PowerShell, Python) for automation and system management tasks.
- Demonstrated ability to troubleshoot and resolve complex infrastructure issues.
- Experience in preparing detailed system documentation and operational procedures.
- Familiarity with Infrastructure as Code (IaC) principles and tools.
- Strong collaboration and communication skills for working with cross-functional teams.
- Desired Skills list:
- Familiarity with USCENTCOM's mission and operations.
- Proficiency in SPL (Search Processing Language)
- Experience with CIM mapping, data modeling, and correlation searches
- Strong Linux administration skills
- Familiarity with Python, REST APIs, and automation frameworks
- Understanding of enterprise cybersecurity tools, SIEM/SOAR, and network architecture
- Experience supporting classified environments and secure enclaves
- Proven ability to design and implement disaster recovery strategies.
- Hands-on experience with configuration management tools (e.g., Ansible, Puppet).
Also Security clearance level: Secret (again)
US citizenship required (again)
We need to avoid duplication but preserve all substantive info. We can combine.
We should not include "Certifications: None" as a separate bullet if it's just "None". Might be considered filler? It's substantive but says none. Could be included as a note. But we could omit if it's just "None". However instruction: preserve ALL substantive information; do NOT invent or summarize away detail. "None" is substantive. So we should include it.
Similarly "Public Trust/Other Required: None" maybe we can include but it's not needed.
We need to decide sections: Perhaps we have:
- About the role (prose)
- Responsibilities (list)
- Qualifications (list) (including required skills, desired skills, certifications, experience, citizenship, clearance)
- Benefits (list) (Total Rewards description)
- Pay (salary range)
- Schedule (weekly hours, travel, telecommuting)
We must not create sections with filler placeholder. All have content.
Now we need to format.
We'll output HTML fragment like:
About the role
...
Responsibilities
- ...
...
Qualifications
- ...
...
But qualifications includes multiple subcategories; we could still list each as separate - . Could also have nested lists but not required.
We need to ensure we don't duplicate content. Let's compile unique bullet points.
First, gather all qualification-related items:
- Type of Requisition: Regular (maybe not needed but it's metadata; could be omitted as not substantive? It's a detail but maybe minor. The instruction says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So we can drop Type of Requisition.
- Clearance Level Must Currently Possess: Secret
- Clearance Level Must Be Able To Obtain: Secret (duplicate)
- Public Trust/Other Required: None (maybe drop as minor)
- Job Family: Cyber and IT Risk Management (maybe drop as minor)
- Skills: Splunk Administration, Splunk Enterprise Security, Splunk Infrastructure Monitoring, Teamwork and Cooperation (these are under Job Qualifications)
- Certifications: None
- Experience: 5+ years of related experience
- US Citizenship Required: Yes
- Certification: DoD 8140 or DoD 8570 Certification (or equivalent)
- Required Skills (list as above)
- Desired Skills (list as above)
- Security clearance level: Secret (duplicate)
- US citizenship required (duplicate)
We need to avoid duplication but preserve all substantive info. We can combine duplicates into one bullet.
Let's create a qualifications list with distinct items:
- Secret clearance (currently possess and able to obtain)
- US citizenship required
- 5+ years of related experience
- DoD 8140 or DoD 8570 Certification (or equivalent)
- Splunk Administration
- Splunk Enterprise Security
- Splunk Infrastructure Monitoring
- Teamwork and Cooperation
- Extensive experience in systems engineering and infrastructure management.
- Strong understanding of virtualization technologies (e.g., VMware, Hyper-V) and cloud-based solutions.
- Expertise in networking protocols, security technologies, and firewalls.
- Advanced proficiency in scripting (PowerShell, Python) for automation and system management tasks.
- Demonstrated ability to troubleshoot and resolve complex infrastructure issues.
- Experience in preparing detailed system documentation and operational procedures.
- Familiarity with Infrastructure as Code (IaC) principles and tools.
- Strong collaboration and communication skills for working with cross-functional teams.
- Famil
for prose. We must not repeat job title as heading. So no heading for the job title. We must not put Job ID/requisition numbers as headings. We need to preserve all substantive info. Let's extract substantive info: About the role: "MEANINGFUL WORK AND PERSONAL IMPACT As a Splunk & Cyber Engineer supporting USCENTCOM, you will play a pivotal role in enabling data‑driven cyber operations and accelerating the command’s ability to detect, respond to, and mitigate threats. You will lead the engineering, deployment, and optimization of Splunk Enterprise and Splunk Enterprise Security (ES) solutions that support high‑tempo operations and mission‑critical decision‑making." Also maybe "HOW A SPLUNK & CYBER ENGINEER WILL MAKE AN IMPACT" but that's just a heading; we can incorporate into about the role. We could combine that paragraph as about the role. Responsibilities: Duties And Responsibilities list: - Lead the design, deployment, and administration of Splunk Enterprise, Splunk ES, and Splunk ITSI across complex, multi‑classification environments supporting CENTCOM missions. - Engineer end‑to‑end data ingestion pipelines, including onboarding, parsing, CIM normalization, correlation rule development, and integration with enterprise security tools. - Develop advanced dashboards, alerts, analytics, and automation to support threat hunting, incident response, and operational reporting for the Joint Cyber Center (JCC). - Conduct performance tuning, capacity planning, system hardening, and lifecycle management of Splunk infrastructure to ensure high availability and resilience. - Collaborate with cybersecurity, network, and systems engineering teams to integrate Splunk with SIEM/SOAR platforms, mission systems, and emerging technologies. - Perform vulnerability analysis, risk assessments, and forensic support using Splunk‑based analytics and data models. - Translate CENTCOM operational requirements into scalable, secure, and cost‑effective Splunk solutions aligned with mission priorities. - Build trusted relationships with CENTCOM stakeholders, providing expert guidance and mentoring junior engineers. - May serve as a team or task lead, guiding technical execution and ensuring alignment with operational and cybersecurity objectives. Additional Responsibilities: - Provide engineering support during system deployment and integration projects. - Participate in performance tuning and optimization to maximize system efficiency and uptime. - Research and implement best practices and new technologies to improve system capabilities. We can combine both lists under Responsibilities. Requirements/Qualifications: We have: - Type of Requisition: Regular (maybe not needed) - Clearance Level Must Currently Possess: Secret - Clearance Level Must Be Able To Obtain: Secret (maybe redundant) - Public Trust/Other Required: None (maybe not needed) - Job Family: Cyber and IT Risk Management (maybe not needed) - Skills: (list) Splunk Administration, Splunk Enterprise Security, Splunk Infrastructure Monitoring, Teamwork and Cooperation (these are under Job Qualifications) - Certifications: None - Experience: 5 + years of related experience - US Citizenship Required: Yes - Certification: DoD 8140 or DoD 8570 Certification (or equivalent) (under WHAT YOU’LL NEED TO SUCCEED) - Experience: 5+ years of related experience (again) - Required Skills list (under WHAT YOU’LL NEED TO SUCCEED): - Extensive experience in systems engineering and infrastructure management. - Strong understanding of virtualization technologies (e.g., VMware, Hyper-V) and cloud-based solutions. - Expertise in networking protocols, security technologies, and firewalls. - Advanced proficiency in scripting (PowerShell, Python) for automation and system management tasks. - Demonstrated ability to troubleshoot and resolve complex infrastructure issues. - Experience in preparing detailed system documentation and operational procedures. - Familiarity with Infrastructure as Code (IaC) principles and tools. - Strong collaboration and communication skills for working with cross-functional teams. - Desired Skills list: - Familiarity with USCENTCOM's mission and operations. - Proficiency in SPL (Search Processing Language) - Experience with CIM mapping, data modeling, and correlation searches - Strong Linux administration skills - Familiarity with Python, REST APIs, and automation frameworks - Understanding of enterprise cybersecurity tools, SIEM/SOAR, and network architecture - Experience supporting classified environments and secure enclaves - Proven ability to design and implement disaster recovery strategies. - Hands-on experience with configuration management tools (e.g., Ansible, Puppet). Also Security clearance level: Secret (again) US citizenship required (again) We need to avoid duplication but preserve all substantive info. We can combine. We should not include "Certifications: None" as a separate bullet if it's just "None". Might be considered filler? It's substantive but says none. Could be included as a note. But we could omit if it's just "None". However instruction: preserve ALL substantive information; do NOT invent or summarize away detail. "None" is substantive. So we should include it. Similarly "Public Trust/Other Required: None" maybe we can include but it's not needed. We need to decide sections: Perhaps we have: - About the role (prose) - Responsibilities (list) - Qualifications (list) (including required skills, desired skills, certifications, experience, citizenship, clearance) - Benefits (list) (Total Rewards description) - Pay (salary range) - Schedule (weekly hours, travel, telecommuting) We must not create sections with filler placeholder. All have content. Now we need to format. We'll output HTML fragment like:
About the role
...
Responsibilities
- ... ...
Qualifications
- ... ...
or drop it. So we can drop Type of Requisition. - Clearance Level Must Currently Possess: Secret - Clearance Level Must Be Able To Obtain: Secret (duplicate) - Public Trust/Other Required: None (maybe drop as minor) - Job Family: Cyber and IT Risk Management (maybe drop as minor) - Skills: Splunk Administration, Splunk Enterprise Security, Splunk Infrastructure Monitoring, Teamwork and Cooperation (these are under Job Qualifications) - Certifications: None - Experience: 5+ years of related experience - US Citizenship Required: Yes - Certification: DoD 8140 or DoD 8570 Certification (or equivalent) - Required Skills (list as above) - Desired Skills (list as above) - Security clearance level: Secret (duplicate) - US citizenship required (duplicate) We need to avoid duplication but preserve all substantive info. We can combine duplicates into one bullet. Let's create a qualifications list with distinct items: - Secret clearance (currently possess and able to obtain) - US citizenship required - 5+ years of related experience - DoD 8140 or DoD 8570 Certification (or equivalent) - Splunk Administration - Splunk Enterprise Security - Splunk Infrastructure Monitoring - Teamwork and Cooperation - Extensive experience in systems engineering and infrastructure management. - Strong understanding of virtualization technologies (e.g., VMware, Hyper-V) and cloud-based solutions. - Expertise in networking protocols, security technologies, and firewalls. - Advanced proficiency in scripting (PowerShell, Python) for automation and system management tasks. - Demonstrated ability to troubleshoot and resolve complex infrastructure issues. - Experience in preparing detailed system documentation and operational procedures. - Familiarity with Infrastructure as Code (IaC) principles and tools. - Strong collaboration and communication skills for working with cross-functional teams. - Famil