Senior Security Engineer I, Advanced Response
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which headings to use based on content.
We have content about what you'll do (duties) and about the role (description). Could map to "Responsibilities" for duties, and "About the role" for overview. Or we could put duties under "Responsibilities". The "About The Role" section includes leading incidents, etc. That seems like responsibilities. The "What You’ll Do" also lists duties. So we could combine them under Responsibilities.
But we also have "Who You Are" which lists qualifications/requirements. That could go under Requirements or Qualifications. Also "Preferred Experience" etc.
We have "Investing in our people..." paragraph about qualities.
We have "Why CoreWeave?" about culture, values.
We have "The base salary range for this role is $139,000 to $204,000." plus details about compensation. That's Pay.
We have benefits list under "What We Offer". That's Benefits.
We have schedule? Not explicitly mentioned except "Please note that this role is not a typical 9-5 job. There will be instances where your skills are needed outside of business hours. On-call hours (including weekends and holidays) and leadership during active incidents is expected." That's schedule/on-call expectations. So we can include Schedule section.
We have no explicit "Qualifications" separate from Requirements; but we can treat "Who You Are" as Requirements (or Qualifications). The instruction says we can have both Requirements and Qualifications sections if content exists. We have "Who You Are" (extensive experience, etc.) and "Preferred Experience". Could split: Requirements = mandatory; Preferred Experience = preferred. But we need to decide headings.
We have "Proficiency in at least one query language..." etc. Those are requirements.
We have "Preferred Experience building or materially maturing an IR program..." etc.
Thus we can have:
About the role
maybe a brief overview: "CoreWeave powers the world's most demanding AI infrastructure..." but that's more company description. Actually the first paragraph about CoreWeave is company overview, not role. Could be omitted? It's substantive but not about role. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." The company overview could be considered minor metadata? It's not about the role but maybe we can include as a short paragraph under About the role? However the instruction says include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. The company overview is specific content but not about the role; but we could still include it as part of About the role? Might be okay. Better to follow typical structure: About the role (overview), Responsibilities (duties), Requirements (mandatory), Qualifications (maybe preferred), Skills (maybe technical skills), Benefits, Pay, Schedule. But we need to avoid duplication. Let's extract content: Company overview (first paragraph): "CoreWeave is The Essential Cloud for AI™. Built for pioneers by pioneers, CoreWeave delivers a platform of technology, tools, and teams that enables innovators to build and scale AI with confidence. Trusted by leading AI labs, startups, and global enterprises, CoreWeave combines superior infrastructure performance with deep technical expertise to accelerate breakthroughs and turn compute into capability. Founded in 2017, CoreWeave became a publicly traded company (Nasdaq: CRWV) in March 2025. Learn more at www.coreweave.com." That's generic but could be placed under About the role? Might be considered boilerplate? It's not navigation/legal/EEO. It's substantive about the company. I'd keep it as a short paragraph under About the role. Next: "What You’ll Do" bullet list (actually sentences separated by em dash?). Let's capture: - Counter threat actors at a scale most practitioners never encounter — and build the capabilities to stay left of boom - Work alongside security partners who hold a high bar and expect you to raise it - Shape how CoreWeave finds and responds to the threats that matter most, with the autonomy to build and execute at the highest level Then "About The Role" heading with paragraphs: - Leading the most complex, highest severity cybersecurity incidents at CoreWeave end-to-end – with full ownership of outcomes, not just coordination - Reading smoke — authoritatively forming hypotheses about what's burning and a strategy to attack it before you can see the fire directly - Serving as a clear, credible voice to senior leadership during active incidents — translating fast-moving technical situations into risk and decision frameworks that drive action - Conducting deep technical investigations and hunts across endpoint, cloud, identity, and network data sources to establish scope, timeline, and root cause - Producing rigorous, risk-driven post-incident reviews that go beyond surface-level timelines and result in concrete, durable improvements - Running a structured threat hunting program informed by operationalized intelligence — turning actor profiles, campaign reporting, and TTP gaps into hunts, and turning hunt findings into durable actions to harden CoreWeave and improve our response posture - Architecting and building AI-powered tooling that drives how CoreWeave counters threats — accelerating work left and right of boom - Developing and running incident simulations and tabletop exercises that stress-test real-world response capabilities before a real incident does These are responsibilities/duties. Next: "Investing in our people is one of our top priorities, and we value candidates who can bring their diversified experiences to our teams. Here are some qualities we’ve found compatible with our teams. We'd love to talk about whether this aligns with your experience and interests and what you’re excited to work on next." Then "Who You Are" bullet list (actually sentences): - Extensive experience in incident response, security operations roles, and/or threat hunting at scale, with demonstrated ownership of complex, high-impact incidents from start to finish - Strong technical investigation and hunting skills — comfortable working hands-on with logs, telemetry, and raw system data to form and validate hypotheses, not just direct others to do it - Deep familiarity with attacker TTPs and how they manifest across cloud, endpoint, identity, and network environments - Experience briefing senior leadership and non-technical stakeholders during active incidents with clarity and composure - Comfort leading and operating across organizational boundaries — pulling the right people in at the right time without losing ownership of the outcome - Proficiency in at least one query language (e.g., SQL, Splunk Query Language, HiveQL) - Ability to script or automate in Python, Go, or similar to close operational gaps and accelerate response and hunting workflows Then "Preferred Experience" bullet list: - Experience building or materially maturing an IR program at a cloud-native organization - Familiarity with Kubernetes or containerized environments, with appetite to go deeper - Experience building and leveraging AI-assisted tooling in investigation or triage workflows - Familiarity with SOAR platforms and case management tooling in an operational IR context Then "Please note that this role is not a typical 9-5 job. There will be instances where your skills are needed outside of business hours. On-call hours (including weekends and holidays) and leadership during active incidents is expected." Then "Why CoreWeave?" section with culture values etc. Then "The base salary range for this role is $139,000 to $204,000. The starting salary will be determined based on job-related knowledge, skills, experience, and market location. We strive for both market alignment and internal equity when determining compensation. In addition to base salary, our total rewards package includes a discretionary bonus, equity awards, and a comprehensive benefits program (all based on eligibility)." Then "What We Offer" bullet list of benefits. Then California Applicants etc (EEO) - we need to remove EEO boilerplate. Also Export Control Compliance - maybe keep? It's not EEO but it's a requirement. Might be considered substantive? It's about eligibility. Could be included under Requirements? But it's a legal requirement. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Export Control Compliance is legal. Likely should be removed. Also California Applicants etc is EEO/legal. Remove. Thus we keep: company overview, What You’ll Do, About The Role, Investing in our people (intro), Who You Are, Preferred Experience, schedule note, Why CoreWeave? (culture), Pay, Benefits. Now we need to map to headings. We could do:
About the role
CoreWeave is The Essential Cloud for AI™....
Responsibilities
- ... (combined from What You’ll Do and About The Role)
Requirements
- ... (Who You Are)
Preferred Qualifications
maybe use Qualifications heading? The instruction list includes Qualifications as a possible heading. We'll useQualifications
for Preferred Experience.Skills
maybe we could list technical skills like proficiency in query language, scripting, etc. But those are already in Requirements. Could keep them there. Might not need separate Skills.Benefits
- ... (What We Offer)
Pay
The base salary range for this role is $139,000 to $204,000....
Schedule
Please note that this role is not a typical 9-5 job....
We might also include a section for "About CoreWeave" or "Company Overview" but not required. Could fold into About the role. We must not include headings with filler text. Ensure each heading has substantive content. Now we need to preserve ALL substantive information; do not invent or summarize away detail. So we must keep all details from the sections we include. Let's extract exact text for each bullet. Responsibilities: combine both lists. From "What You’ll Do": - Counter threat actors at a scale most practitioners never encounter — and build the capabilities to stay left of boom - Work alongside security partners who hold a high bar and expect you to raise it - Shape how CoreWeave finds and responds to the threats that matter most, with the autonomy to build and execute at the highest level From "About The Role": - Leading the most complex, highest severity cybersecurity incidents at CoreWeave end-to-end – with full ownership of outcomes, not just coordination - Reading smoke — authoritatively forming hypotheses about what's burning and a strategy to attack it before you can see the fire directly - Serving as a clear, credible voice to senior leadership during active incidents — translating fast-moving technical situations into risk and decision frameworks that drive action - Conducting deep technical investigations and hunts across endpoint, cloud, identity, and network data sources to