Cybersecurity Specialist

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to preserve all substantive info. Let's parse the posting. Key parts: - Remote, MUST reside in Washington, Florida or Texas, W2 hourly plus benefits. Actually later says: Applicants must be currently authorized to work in the United States on a full-time basis AND reside in either Washington state or Texas. So location requirement: Washington or Texas (not Florida). The first line says Remote, MUST reside in Washington, Florida or Texas, but later clarifies Washington or Texas. We'll preserve both? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to include both statements? There's a contradiction but we keep both as they appear. Probably we should include the location requirement as a paragraph. - W2 hourly plus benefits. - Applicants must be currently authorized to work in the United States on a full-time basis AND reside in either Washington state or Texas. - The employer will not sponsor applicants for work visas. - The employer may not have resources available to support STEM OPT training requirements. - No C2C - Pivotal does not accept unsolicited applications or resumes from third-party recruiters/agencies. - Why Clients Choose Pivotal Consulting (section). We'll make heading About the role? Actually "Why Clients Choose Pivotal Consulting" is about the company. Could be "About the role" or "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these headings. We have: - About the role: maybe the description of what we are looking for and what you will do. Could be "What We Are Looking For" and "What You Will Do". That fits under Responsibilities? Actually responsibilities are duties. So we can have a Responsibilities section with bullet list of duties. - Requirements: "Required Qualifications" bullet list. - Skills: maybe "Preferred Skills" bullet list. - Benefits: mention W2 hourly plus benefits, medical, dental, vision insurance, 401k, time to pursue certifications, supporting non-profits, core values? Actually benefits: "Pivotal Consulting offers a comprehensive benefit package, including medical, dental and vision insurance, and 401k." Also earlier: "W2 hourly plus benefits". Also "providing our employees with the time to pursue company-sponsored certifications, to supporting and partnering with multiple non-profit organizations". Could be part of benefits or culture. We'll include Benefits section with bullet list. - Pay: "The pay range for this position in Washington is $60-$75/hr. W2 plus benefits; however, base pay offered may vary depending on job-related knowledge, skills, candidate location, and experience." - Schedule: Not mentioned. So we should not include Schedule section. - About the role: maybe we can include a short paragraph summarizing role: "We are seeking an experienced Cybersecurity Specialist with strong AWS, Salesforce & Okta expertise to support ongoing security operations for a major global technology client." That's under "What We Are Looking For". Could be About the role. We also have "Why Clients Choose Pivotal Consulting" which is company description. Could be part of About the role? Or maybe we can include a section "About the company" but not in allowed headings. Since only allowed headings are those listed, we should map company description to maybe "About the role"? But that seems odd. However instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples, not exclusive? It says use those for section headings. Likely we should only use those headings. So we need to fit all content under those headings. Thus: - About the role: include company description and role overview. - Responsibilities: bullet list of duties. - Requirements: bullet list of required qualifications. - Skills: bullet list of preferred skills. - Benefits: bullet list of benefits. - Pay: paragraph with pay range. - Schedule: omit. We also need to include location and work authorization info etc. Where to put? Could be under About the role or maybe a separate section like "Requirements" includes location/auth? But those are not qualifications per se. Could be under Requirements as bullet items: "Must be authorized to work in the US full-time", "Must reside in Washington or Texas", "No visa sponsorship", "No STEM OPT support", "No C2C/third-party recruiters". Those are eligibility requirements. We'll include them under Requirements. Now we need to ensure we don't repeat boilerplate like EEO etc. The posting includes EEO statement at end: "Pivotal Consulting is committed to creating and supporting a diverse and inclusive team..." That's boilerplate; we should remove it. Also remove "Why Our Employees Love Working At Pivotal" maybe? That's culture/benefits; we can keep some parts as benefits. But the section includes core values etc. Might be considered benefits/culture. We'll extract benefits: medical, dental, vision, 401k, time to pursue certifications, support for non-profits, core values? The core values maybe not a benefit but we can include as part of Benefits? Might be okay. But we must not include filler like "commensurate with experience". Not present. Now produce HTML. Structure:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Skills

• ...
...

Benefits

• ...
...

Pay

...

Make sure no extra whitespace? It's fine. Now craft content. About the role paragraph: combine "Why Clients Choose Pivotal Consulting" and "What We Are Looking For". Let's write: Pivotal Consulting is a technology management consulting firm helping Fortune 500 companies improve performance by making People, Process, and Technology work together. Clients rely on us for business and technology strategy, technology modernization, and cloud transformation initiatives. We are seeking an experienced Cybersecurity Specialist with strong AWS, Salesforce & Okta expertise to support ongoing security operations for a major global technology client. That seems good. Responsibilities bullet list from "What You Will Do": - Monitor and analyze security events using AWS, Salesforce & Okta to identify potential threats and vulnerabilities. - Investigate and respond to security incidents, providing detailed root cause analysis and remediation support. - Develop and fine-tune Splunk queries, dashboards, alerts, and correlation rules to enhance threat visibility. - Conduct proactive threat hunting and anomaly detection across large data sets. - Document incident findings and create post-incident reports for stakeholders. - Collaborate with infrastructure and application teams to ensure proper log ingestion and data normalization. - Participate in security process improvements and recommend automation or workflow enhancements. Requirements bullet list from "Required Qualifications" plus eligibility: - 7+ years of experience working in a Security Operations Center (SOC) or cyber incident response role. - Advanced Splunk experience in both operational monitoring and content development. - Experience with AWS, Okta & Salesforce. - Strong understanding of SIEM and SOAR principles, detection engineering, and log correlation. - Solid knowledge of common security frameworks, including MITRE ATT&CK and NIST. - Familiarity with network protocols, firewalls, IDS/IPS, and endpoint protection tools. - Proven ability to handle high-volume security data and triage incidents efficiently. - Must be currently authorized to work in the United States on a full-time basis. - Must reside in Washington state or Texas. - Employer will not sponsor applicants for work visas. - Employer may not have resources available to support STEM OPT training requirements. - No C2C – Pivotal does not accept unsolicited applications or resumes from third-party recruiters/agencies. Skills bullet list from "Preferred Skills": - Industry certifications such as Security+, CEH, GCIA, or GCIH. - Experience in scripting (Python, PowerShell) for SOC automation. - Exposure to cloud security monitoring (AWS, Azure, or GCP). Benefits bullet list: - W2 hourly position with benefits. - Pay range $60-$75/hr (Washington) (note pay also in Pay section; maybe avoid duplication? But we need to include pay info somewhere; we have Pay section separate. Benefits can mention medical, dental, vision insurance, 401k, time to pursue company-sponsored certifications, support for employee-led non-profit partnerships (Food Lifeline, United Way, Seattle Humane Society), commitment to diversity and inclusion, core values (Be Engaged, Consistently Deliver, Always Better, Do Happy). However some of those may be more culture than benefit. We'll include tangible benefits: medical, dental, vision insurance, 401k, time to pursue certifications, support for non-profit organizations. We must not duplicate pay info in Benefits if we have Pay section. But we can mention "W2 hourly plus benefits" as a benefit. That's okay. Pay section: paragraph with pay range and note about variation. Now ensure we didn't include boilerplate: EEO statement removed. Also removed "Why Our Employees Love Working At Pivotal" except we extracted benefits. Now produce HTML. Check for any repeated lines: ensure we didn't include "Remote, MUST reside in Washington, Florida or Texas, W2 hourly plus benefits" as separate; we incorporated location in Requirements and pay in Pay. We need to ensure we didn't miss any substantive info: The line "Remote, MUST reside in Washington, Florida or Texas, W2 hourly plus benefits" is partially covered: we have W2 hourly plus benefits in Benefits, location in Requirements (Washington or Texas). The Florida mention is contradictory but we kept only Washington or Texas as per later statement. However we must preserve ALL substantive information; the earlier line includes Florida. If we drop Florida, we are omitting substantive info. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the Florida mention as well, even if contradictory. So we need to include that line somewhere. Perhaps we can include in Requirements: "Must reside in Washington, Florida, or Texas" but later says "Applicants must be currently authorized to work in the United States on a full-time basis AND reside in either Washington state or Texas." That's a contradiction; we must keep both statements. So we need to include both. We can put both as separate bullet points: "Must reside in Washington, Florida, or Texas" and "Must reside in Washington state or Texas". That preserves both. Or we could combine into a note: "Posting states residency must be in Washington, Florida, or Texas; later clarifies requirement is Washington or Texas." But that would be summarizing. Better to keep both statements verbatim. Thus we add two bullet points under Requirements: - Must reside in Washington, Florida, or Texas. - Must reside in Washington state or Texas. But that seems redundant; but it's preserving. Also the line "Remote, MUST reside in Washington, Florida or Texas, W2 hourly plus benefits" we can capture as: "Remote position; must reside in Washington, Florida, or Texas; W2 hourly plus benefits." We'll incorporate that in About the role or Benefits. Let's add a bullet in Benefits: "Remote position; W2 hourly plus benefits." And keep location statements in Requirements. Now ensure we didn't miss "The employer will not sponsor applicants for work visas." Already in Requirements. "The employer may not have resources available to support STEM OPT training requirements."