Splunk Consultant -Active (TS/SCI with a CI Poly)
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove EEO etc. Also remove "Please apply for immediate consideration." Also remove "Equal Opportunity Employer ..." and the PDF link. Also remove "Policy-Statement_EEO-EmployeesAndCandidates.pdf (vibrint.com)". Also remove "The pay range for this position is a general guideline only and not a guarantee of compensation or salary."? That is about pay; we need to include Pay section only if posting actually states them. The posting includes a paragraph about pay range being a guideline and considerations, and then a list of compensation package items. So we have pay info: they say "The pay range for this position is a general guideline only and not a guarantee of compensation or salary." Then they list considerations. Then they list comprehensive compensation package includes but not limited to: competitive salary; annual merit-based salary increase and discretionary bonus program; 401(k) plan with a company contribution; 11 paid federal holidays; 160 hours of paid time off; medical, dental, vision, life and short- & long-term disability insurance; employee assistance program; and a generous professional development allowance.
Thus we have Pay and Benefits sections. The "Pay" section could include the statement about pay range being a guideline and considerations? The instruction: "Prefer a few substantive sections over many thin ones." Also "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')". The pay range statement is generic but still substantive? It says it's a guideline only and not a guarantee. That's not a specific number, but it's still content about pay. However they also list compensation package details which are benefits. The "Pay" section could be just the statement about pay range being a guideline and considerations? Might be considered filler? It says "The pay range for this position is a general guideline only and not a guarantee of compensation or salary." That's somewhat generic but still about pay. The instruction says never emit a heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". This is not exactly those, but it's still vague. However we also have the list of compensation package items which are benefits. So we could combine Pay and Benefits into one section? But they said use headings for Benefits, Pay, Schedule etc. We could have a Benefits section that includes the list, and maybe a Pay section that includes the statement about pay range being a guideline and considerations. That seems okay.
Schedule: no info about schedule, so omit.
Now we need to parse the posting for sections: About the role (intro paragraph), Responsibilities (list of duties), Requirements (maybe required skills?), Qualifications (maybe TS/SCI + CI Poly), Skills (desired skills). However the posting lumps Required Skills and Desired Skills. Also there is a "Qualifications:" line with TS/SCI + CI Poly.
We need to decide how to map. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create sections that match the content.
We have an introductory paragraph about Vibrint and the role: "Vibrint is a trusted provider..." That's about the role/company. Could be About the role.
Then we have "Required Skills" bullet list (actually sentences). Those are responsibilities? They are more like required experience/skills. Could be Responsibilities? Or Requirements? The list includes: Minimum of four (4) years of experience serving as a Splunk SME, Solutions Architect, Senior Engineer, or similar role supporting enterprise security operations, SIEM, or cybersecurity initiatives within Federal Government or Intelligence Community (IC) environments. Demonstrated hands-on experience designing, implementing, administering, documenting and optimizing Splunk Enterprise and Splunk Enterprise Security (ES) environments. Experience assessing Splunk architecture and environment health, including data ingestion, indexing, search performance, capacity, configuration, and platform optimization, with the ability to develop actionable recommendations. Experience designing and configuring specialized SOC dashboards, searches, alerts, reports, data models, and security use cases aligned to customer mission requirements. Experience developing environment-specific as-built documentation, operational runbooks, and knowledge-management materials to support ongoing Splunk Operations & Maintenance (O&M). Experience conducting structured knowledge transfer and workforce training to enable customer administrators to assume day-to-day Splunk O&M responsibilities. Ability to provide senior-level Tier 3/4 architectural guidance, troubleshooting, and technical escalation support. Excellent written and verbal communication skills with the ability to communicate technical findings, architectural recommendations, operational procedures, and training content to engineering teams and customer stakeholders. Bachelor's degree in Computer Science, Information Systems, Engineering, Cybersecurity, or a related technical discipline, or equivalent experience.
These are requirements/qualifications. Could be Requirements section.
Then "Desired Skills" list: Experience supporting Splunk Enterprise Security within a Security Operations Center (SOC) and translating mission requirements into effective security monitoring and operational workflows. Experience leading Splunk platform assessments, optimization efforts, or O&M transition activities for Federal Government or Intelligence Community customers. Experience supporting highly regulated or classified environments. Relevant Splunk certifications, such as Splunk Core Certified Power User, Splunk Enterprise Certified Admin, Splunk Enterprise Certified Architect, or Splunk Enterprise Security Certified Admin.
These could be Skills section (desired skills). Or could be Qualifications? But we already have Qualifications line: "Qualifications: TS/SCI + CI Poly". That's a specific clearance requirement.
Thus we can have:
- About the role: intro paragraph.
- Responsibilities: maybe we could treat the required skills as responsibilities? But they are more like qualifications. However we have no explicit responsibilities list separate from required skills. The posting does not have a separate "Responsibilities" heading; it's all under Required Skills. So we could map Required Skills to Responsibilities? Or to Requirements? The instruction says use headings like Responsibilities, Requirements, Qualifications, Skills. We need to decide which to use.
We have content for Required Skills (list of experience/skills). That could go under Requirements. We have Desired Skills list that could go under Skills. We have Qualifications line (TS/SCI + CI Poly) that could go under Qualifications. We have About the role intro.
We could also include a Responsibilities section if we can derive responsibilities from the required skills (like designing, implementing, administering Splunk, assessing architecture, configuring SOC dashboards, developing documentation, conducting knowledge transfer, providing Tier 3/4 guidance, communicating). Those are indeed responsibilities. So we could put those under Responsibilities. Then Requirements could be the baseline: minimum 4 years experience, Bachelor's degree, etc. But the required skills list includes both experience and skills. Might be overlapping.
Given the instruction to preserve ALL substantive information, we need to ensure we don't lose any detail. We can split the required skills list into two sub-sections: Responsibilities (the action-oriented duties) and Requirements (the baseline qualifications). But we must not invent headings without content. We have content for both.
Let's extract:
From Required Skills list:
- Minimum of four (4) years of experience serving as a Splunk Subject Matter Expert (SME), Solutions Architect, Senior Engineer, or similar role supporting enterprise security operations, SIEM, or cybersecurity initiatives within Federal Government or Intelligence Community (IC) environments. (experience requirement)
- Demonstrated hands-on experience designing, implementing, administering, documenting and optimizing Splunk Enterprise and Splunk Enterprise Security (ES) environments. (responsibility)
- Experience assessing Splunk architecture and environment health, including data ingestion, indexing, search performance, capacity, configuration, and platform optimization, with the ability to develop actionable recommendations. (responsibility)
- Experience designing and configuring specialized SOC dashboards, searches, alerts, reports, data models, and security use cases aligned to customer mission requirements. (responsibility)
- Experience developing environment-specific as-built documentation, operational runbooks, and knowledge-management materials to support ongoing Splunk Operations & Maintenance (O&M). (responsibility)
- Experience conducting structured knowledge transfer and workforce training to enable customer administrators to assume day-to-day Splunk O&M responsibilities. (responsibility)
- Ability to provide senior-level Tier 3/4 architectural guidance, troubleshooting, and technical escalation support. (responsibility)
- Excellent written and verbal communication skills with the ability to communicate technical findings, architectural recommendations, operational procedures, and training content to engineering teams and customer stakeholders. (skill)
- Bachelor's degree in Computer Science, Information Systems, Engineering, Cybersecurity, or a related technical discipline, or equivalent experience. (education requirement)
Thus we could put the experience and education under Requirements, and the rest under Responsibilities. However the "Excellent written and verbal communication skills" is a skill, could go under Skills. But we already have Desired Skills separate.
Given the instruction to prefer few substantive sections over many thin ones, we might combine Requirements and Qualifications into one? But we have a specific Qualifications line (TS/SCI + CI Poly). That's a clearance requirement.
We could have:
- About the role (intro)
- Responsibilities (list of duties: designing, implementing, administering, assessing architecture, designing SOC dashboards, developing documentation, conducting knowledge transfer, providing Tier 3/4 guidance, communicating technical findings)
- Requirements (minimum 4 years experience, Bachelor's degree or equivalent)
- Qualifications (TS/SCI + CI Poly)
- Skills (Desired Skills list)
- Benefits (list of compensation package)
- Pay (statement about pay range being a guideline and considerations)
We need to ensure we don't create empty sections. All have content.
Now we need to format using
for each heading, then content: either
for prose or
- for lists.
We must not include boilerplate: remove EEO, PDF link, "Please apply for immediate consideration." Also remove "Equal Opportunity Employer..." lines. Also remove "Policy-Statement_EEO-EmployeesAndCandidates.pdf (vibrint.com)". Also remove "The pay range for this position is a general guideline only and not a guarantee of compensation or salary."? That is part of Pay section; we keep it as it's substantive about pay. Also remove "Our approach to crafting offers considers various factors to provide an equitable and competitive comprehensive compensation package. These considerations include, but are not limited to, contracted rates, education, certification(s), experience, specific competencies required for this position, and geographic location." That's also part of Pay considerations.
Thus Pay section will contain that paragraph plus maybe the list of considerations? Actually the list of considerations is part of the Pay paragraph. We'll keep it as prose.
Benefits section will contain the list of compensation package items.
Now we need to ensure we don't duplicate lines. The posting includes "Vibrint's comprehensive compensation package includes but is not limited to:" then list. We'll keep that as intro sentence then list.
Now we need to output only HTML fragment, no /, no markdown.
Let's craft:
About the role
Vibrint is a trusted provider of mission-critical systems and analysis that transform our customers' capacity and capability in harvesting and harnessing data. Working alongside many of the most talented professionals in public service, we work tirelessly to create and sustain new solutions and services that meet the stringent demands across a variety of customer missions. Our people know they'll be doing work that matters at the heart of the national security mission, exploring new possibilities at the cutting edge of technology
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove EEO etc. Also remove "Please apply for immediate consideration." Also remove "Equal Opportunity Employer ..." and the PDF link. Also remove "Policy-Statement_EEO-EmployeesAndCandidates.pdf (vibrint.com)". Also remove "The pay range for this position is a general guideline only and not a guarantee of compensation or salary."? That is about pay; we need to include Pay section only if posting actually states them. The posting includes a paragraph about pay range being a guideline and considerations, and then a list of compensation package items. So we have pay info: they say "The pay range for this position is a general guideline only and not a guarantee of compensation or salary." Then they list considerations. Then they list comprehensive compensation package includes but not limited to: competitive salary; annual merit-based salary increase and discretionary bonus program; 401(k) plan with a company contribution; 11 paid federal holidays; 160 hours of paid time off; medical, dental, vision, life and short- & long-term disability insurance; employee assistance program; and a generous professional development allowance. Thus we have Pay and Benefits sections. The "Pay" section could include the statement about pay range being a guideline and considerations? The instruction: "Prefer a few substantive sections over many thin ones." Also "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')". The pay range statement is generic but still substantive? It says it's a guideline only and not a guarantee. That's not a specific number, but it's still content about pay. However they also list compensation package details which are benefits. The "Pay" section could be just the statement about pay range being a guideline and considerations? Might be considered filler? It says "The pay range for this position is a general guideline only and not a guarantee of compensation or salary." That's somewhat generic but still about pay. The instruction says never emit a heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". This is not exactly those, but it's still vague. However we also have the list of compensation package items which are benefits. So we could combine Pay and Benefits into one section? But they said use headings for Benefits, Pay, Schedule etc. We could have a Benefits section that includes the list, and maybe a Pay section that includes the statement about pay range being a guideline and considerations. That seems okay. Schedule: no info about schedule, so omit. Now we need to parse the posting for sections: About the role (intro paragraph), Responsibilities (list of duties), Requirements (maybe required skills?), Qualifications (maybe TS/SCI + CI Poly), Skills (desired skills). However the posting lumps Required Skills and Desired Skills. Also there is a "Qualifications:" line with TS/SCI + CI Poly. We need to decide how to map. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create sections that match the content. We have an introductory paragraph about Vibrint and the role: "Vibrint is a trusted provider..." That's about the role/company. Could be About the role. Then we have "Required Skills" bullet list (actually sentences). Those are responsibilities? They are more like required experience/skills. Could be Responsibilities? Or Requirements? The list includes: Minimum of four (4) years of experience serving as a Splunk SME, Solutions Architect, Senior Engineer, or similar role supporting enterprise security operations, SIEM, or cybersecurity initiatives within Federal Government or Intelligence Community (IC) environments. Demonstrated hands-on experience designing, implementing, administering, documenting and optimizing Splunk Enterprise and Splunk Enterprise Security (ES) environments. Experience assessing Splunk architecture and environment health, including data ingestion, indexing, search performance, capacity, configuration, and platform optimization, with the ability to develop actionable recommendations. Experience designing and configuring specialized SOC dashboards, searches, alerts, reports, data models, and security use cases aligned to customer mission requirements. Experience developing environment-specific as-built documentation, operational runbooks, and knowledge-management materials to support ongoing Splunk Operations & Maintenance (O&M). Experience conducting structured knowledge transfer and workforce training to enable customer administrators to assume day-to-day Splunk O&M responsibilities. Ability to provide senior-level Tier 3/4 architectural guidance, troubleshooting, and technical escalation support. Excellent written and verbal communication skills with the ability to communicate technical findings, architectural recommendations, operational procedures, and training content to engineering teams and customer stakeholders. Bachelor's degree in Computer Science, Information Systems, Engineering, Cybersecurity, or a related technical discipline, or equivalent experience. These are requirements/qualifications. Could be Requirements section. Then "Desired Skills" list: Experience supporting Splunk Enterprise Security within a Security Operations Center (SOC) and translating mission requirements into effective security monitoring and operational workflows. Experience leading Splunk platform assessments, optimization efforts, or O&M transition activities for Federal Government or Intelligence Community customers. Experience supporting highly regulated or classified environments. Relevant Splunk certifications, such as Splunk Core Certified Power User, Splunk Enterprise Certified Admin, Splunk Enterprise Certified Architect, or Splunk Enterprise Security Certified Admin. These could be Skills section (desired skills). Or could be Qualifications? But we already have Qualifications line: "Qualifications: TS/SCI + CI Poly". That's a specific clearance requirement. Thus we can have: - About the role: intro paragraph. - Responsibilities: maybe we could treat the required skills as responsibilities? But they are more like qualifications. However we have no explicit responsibilities list separate from required skills. The posting does not have a separate "Responsibilities" heading; it's all under Required Skills. So we could map Required Skills to Responsibilities? Or to Requirements? The instruction says use headings like Responsibilities, Requirements, Qualifications, Skills. We need to decide which to use. We have content for Required Skills (list of experience/skills). That could go under Requirements. We have Desired Skills list that could go under Skills. We have Qualifications line (TS/SCI + CI Poly) that could go under Qualifications. We have About the role intro. We could also include a Responsibilities section if we can derive responsibilities from the required skills (like designing, implementing, administering Splunk, assessing architecture, configuring SOC dashboards, developing documentation, conducting knowledge transfer, providing Tier 3/4 guidance, communicating). Those are indeed responsibilities. So we could put those under Responsibilities. Then Requirements could be the baseline: minimum 4 years experience, Bachelor's degree, etc. But the required skills list includes both experience and skills. Might be overlapping. Given the instruction to preserve ALL substantive information, we need to ensure we don't lose any detail. We can split the required skills list into two sub-sections: Responsibilities (the action-oriented duties) and Requirements (the baseline qualifications). But we must not invent headings without content. We have content for both. Let's extract: From Required Skills list: - Minimum of four (4) years of experience serving as a Splunk Subject Matter Expert (SME), Solutions Architect, Senior Engineer, or similar role supporting enterprise security operations, SIEM, or cybersecurity initiatives within Federal Government or Intelligence Community (IC) environments. (experience requirement) - Demonstrated hands-on experience designing, implementing, administering, documenting and optimizing Splunk Enterprise and Splunk Enterprise Security (ES) environments. (responsibility) - Experience assessing Splunk architecture and environment health, including data ingestion, indexing, search performance, capacity, configuration, and platform optimization, with the ability to develop actionable recommendations. (responsibility) - Experience designing and configuring specialized SOC dashboards, searches, alerts, reports, data models, and security use cases aligned to customer mission requirements. (responsibility) - Experience developing environment-specific as-built documentation, operational runbooks, and knowledge-management materials to support ongoing Splunk Operations & Maintenance (O&M). (responsibility) - Experience conducting structured knowledge transfer and workforce training to enable customer administrators to assume day-to-day Splunk O&M responsibilities. (responsibility) - Ability to provide senior-level Tier 3/4 architectural guidance, troubleshooting, and technical escalation support. (responsibility) - Excellent written and verbal communication skills with the ability to communicate technical findings, architectural recommendations, operational procedures, and training content to engineering teams and customer stakeholders. (skill) - Bachelor's degree in Computer Science, Information Systems, Engineering, Cybersecurity, or a related technical discipline, or equivalent experience. (education requirement) Thus we could put the experience and education under Requirements, and the rest under Responsibilities. However the "Excellent written and verbal communication skills" is a skill, could go under Skills. But we already have Desired Skills separate. Given the instruction to prefer few substantive sections over many thin ones, we might combine Requirements and Qualifications into one? But we have a specific Qualifications line (TS/SCI + CI Poly). That's a clearance requirement. We could have: - About the role (intro) - Responsibilities (list of duties: designing, implementing, administering, assessing architecture, designing SOC dashboards, developing documentation, conducting knowledge transfer, providing Tier 3/4 guidance, communicating technical findings) - Requirements (minimum 4 years experience, Bachelor's degree or equivalent) - Qualifications (TS/SCI + CI Poly) - Skills (Desired Skills list) - Benefits (list of compensation package) - Pay (statement about pay range being a guideline and considerations) We need to ensure we don't create empty sections. All have content. Now we need to format using
for each heading, then content: either
for prose or
- for lists.
We must not include boilerplate: remove EEO, PDF link, "Please apply for immediate consideration." Also remove "Equal Opportunity Employer..." lines. Also remove "Policy-Statement_EEO-EmployeesAndCandidates.pdf (vibrint.com)". Also remove "The pay range for this position is a general guideline only and not a guarantee of compensation or salary."? That is part of Pay section; we keep it as it's substantive about pay. Also remove "Our approach to crafting offers considers various factors to provide an equitable and competitive comprehensive compensation package. These considerations include, but are not limited to, contracted rates, education, certification(s), experience, specific competencies required for this position, and geographic location." That's also part of Pay considerations.
Thus Pay section will contain that paragraph plus maybe the list of considerations? Actually the list of considerations is part of the Pay paragraph. We'll keep it as prose.
Benefits section will contain the list of compensation package items.
Now we need to ensure we don't duplicate lines. The posting includes "Vibrint's comprehensive compensation package includes but is not limited to:" then list. We'll keep that as intro sentence then list.
Now we need to output only HTML fragment, no /, no markdown.
Let's craft:
About the role
Vibrint is a trusted provider of mission-critical systems and analysis that transform our customers' capacity and capability in harvesting and harnessing data. Working alongside many of the most talented professionals in public service, we work tirelessly to create and sustain new solutions and services that meet the stringent demands across a variety of customer missions. Our people know they'll be doing work that matters at the heart of the national security mission, exploring new possibilities at the cutting edge of technology