Sr Director, Security Operations (Technology)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real specific content. The posting includes description of role, responsibilities, etc. No explicit Pay or Schedule details (just says compensation depends on factors, competitive total rewards, but no specific numbers). So we should NOT include Pay or Schedule sections because they are not specific. Benefits: there is a "What We’ll Provide" section describing benefits: medical, dental, vision, 401(k) match, paid time off, PTO cash out, family resources, EAP, Headspace, backup child/elder care, maternity/paternity leave, professional development programs, etc. That's specific enough to include Benefits section. We need About the role? The posting starts with description: "The Head of Security Operations is a senior leadership role responsible for defining, executing, and continuously evolving the organization’s security operations strategy." That's about the role. Could be About the role section. Responsibilities: many bullet points under sections like Security Operations Leadership, Player/Coach Execution, Team Development & Organizational Maturity, Operational Excellence & Continuous Improvement, Incident & Crisis Management, Technology & Tooling, Cross-Functional Collaboration. Those are responsibilities. Requirements/Qualifications/Skills: The posting does not explicitly list qualifications like years of experience, education, certifications. It mentions ideal candidate comfortable setting strategic direction, hands-on, etc. Might be considered qualifications but not explicit list. We could include a Qualifications section summarizing the ideal candidate traits? But we must not invent or summarize away detail; we must preserve ALL substantive information. The posting includes statements about ideal candidate: "The ideal candidate is equally comfortable setting strategic direction, rolling up their sleeves during critical incidents, and building high-performing, scalable teams." Also earlier: "This role requires a hands-on “player/coach” leader who combines deep technical expertise with strong operational leadership." Those are qualifications/requirements. Could be placed under Requirements or Qualifications. Since we need to decide which heading to use. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can choose whichever fits. The posting includes responsibilities and also some qualification statements. We could have a Requirements section that includes the hands-on player/coach leader, deep technical expertise, strong operational leadership, comfortable setting strategic direction, etc. Also maybe Skills: could list technical domains: threat detection and response, security engineering, vulnerability management, security monitoring, SIEM, SOAR, EDR/XDR, vulnerability scanners, etc. But those are more responsibilities. However we could still create a Skills section listing those technical skills. But we must not create sections with filler. If we have specific content, we can. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all the bullet points etc. We'll output HTML with sections: About the role (p), Responsibilities (ul), Requirements (ul) maybe, Benefits (ul). Possibly also Qualifications? But we might combine Requirements and Qualifications? Better to separate: Requirements (what is required) and Qualifications (what is ideal). However the posting doesn't have separate list; it's mixed. To avoid duplication, we could have one section "Requirements & Qualifications". But instruction says use headings like Requirements, Qualifications, Skills. It didn't forbid combining but says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we can use those headings if we have content. We could have Requirements and Qualifications separate if we can split content logically. Let's see: The posting includes: "The Head of Security Operations is a senior leadership role responsible for defining, executing, and continuously evolving the organization’s security operations strategy." That's about role. Then: "Reporting to the Vice President, I&O (under the CIO organization), this leader oversees a multi-layered security operations function, managing a team of security operations leaders and engineers across key domains such as threat detection and response, security engineering, vulnerability management, and security monitoring." That's also about role/responsibilities. Then: "This role requires a hands-on “player/coach” leader who combines deep technical expertise with strong operational leadership." That's a requirement. Then: "The ideal candidate is equally comfortable setting strategic direction, rolling up their sleeves during critical incidents, and building high-performing, scalable teams." That's qualification/ideal candidate. Then the bullet sections are responsibilities. Thus we can have: - About the role: maybe a short paragraph summarizing role (the first two sentences). - Responsibilities: list of duties (the bullet points grouped under headings like Security Operations Leadership etc). We'll need to convert each bullet into

. The posting uses headings like "Security Operations Leadership", then sentences. We'll treat each sentence as a list item? The instruction: Use

• for any list of duties/requirements/benefits. So we need to make a list for responsibilities. We'll capture each distinct duty as an
• . Could be many. - Requirements: list of requirements: hands-on player/coach leader, deep technical expertise, strong operational leadership. - Qualifications: list of qualifications: comfortable setting strategic direction, rolling up sleeves during incidents, building high-performing scalable teams. - Skills: maybe list technical domains and tools: threat detection and response, security engineering, vulnerability management, security monitoring, SIEM, SOAR, EDR/XDR, vulnerability scanners, etc. Also maybe "partner with engineering teams", "optimize processes", etc. But those are more responsibilities. However we can still list skills: threat detection and response, security engineering, vulnerability management, security monitoring, SIEM, SOAR, EDR/XDR, vulnerability scanners, etc. Also maybe "incident response", "crisis management", "process optimization", "KPI/KRI definition", "frameworks (NIST CSF, MITRE ATT&CK, ISO 27001)". We'll include those as skills. - Benefits: list from "What We’ll Provide": Comprehensive benefits: Medical, dental, vision, 401(k) match, paid time off, PTO cash out; Support for you and your family: Family resources, EAP counseling sessions, access Headspace®, backup child and elder care, maternity/paternity leave and more; Professional development programs: DaVita offers a variety of programs to help strong performers grow within their career and also offers on-demand virtual leadership and development courses through DaVita’s online training platform StarLearning.; At DaVita, we strive to be a community first and a company second... That's more culture, not benefit. We'll include the concrete benefits. We must not include boilerplate like EEO, equal opportunity, scam warning, etc. Also remove location header, posting date, address? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. The posting includes "Posting Date 09/18/2026 5200 Virginia Way, Brentwood, Tennessee, 37027, United States of America". That's minor metadata; we can either drop it or put in a short

  . Probably drop it as it's not substantive. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." The address is not substantive for the role? It's location info; could be considered substantive but maybe minor. However we could include a short

  with location. But they said fold minor metadata into a short

  or drop it. So we could include a

  with location and date. But we need to decide. The location is somewhat substantive but maybe not needed. I'd include a short

  at top: "Posted 09/18/2026 – Brentwood, TN". That preserves location and date. Now produce HTML fragment. Structure:

  Posted 09/18/2026 – Brentwood, TN

  About the role

  The Head of Security Operations is a senior leadership role responsible for defining, executing, and continuously evolving the organization’s security operations strategy. Reporting to the Vice President, I&O (under the CIO organization), this leader oversees a multi-layered security operations function, managing a team of security operations leaders and engineers across key domains such as threat detection and response, security engineering, vulnerability management, and security monitoring.

  Responsibilities

  • Drive operational excellence across Security Operations Center (SOC), Incident Response, Threat Intelligence, and Vulnerability Management.
  • Lead and manage a distributed organization of security operations leaders and their teams.
  • Define and execute the enterprise security operations strategy aligned with business and technology objectives.
  • Act as a senior technical authority across all security operations domains.
  • Provide hands-on leadership during incidents and high-severity security events.
  • Guide teams in solving complex security challenges, including advanced threat detection and response.
  • Build, mentor, and retain a high-performing security operations organization.
  • Assess current team capabilities and proactively enhance talent through hiring, training, and restructuring where needed.
  • Establish clear career paths, succession planning, and leadership development programs.
  • Implement and optimize processes, playbooks, and automation to improve detection and response times.
  • Define and track KPIs/KRIs (e.g., MTTR, MTTD, incident containment rates).
  • Drive maturity improvements using frameworks such as NIST CSF, MITRE ATT&CK, and ISO 27001.
  • Own enterprise incident response strategy and execution.
  • Lead crisis management efforts for major security incidents.
  • Ensure robust communication protocols and executive reporting during incidents.
  • Oversee security tools and platforms (SIEM, SOAR, EDR/XDR, vulnerability scanners, etc.).
  • Ensure effective integration and optimization of security technologies.
  • Partner with broad range of engineering teams to modernize and scale the security operations stack.
  • Partner closely with Technology Operations, Infrastructure, Cloud, and Application teams.
  • Collaborate with IT Security, Risk, Compliance, and Legal on regulatory and audit requirements.
  • Serve as a key advisor to executive leadership on security posture and risk.

  Requirements

  • Hands‑on “player/coach” leader who combines deep technical expertise with strong operational leadership.

  Qualifications

  • Comfortable setting strategic direction, rolling up sleeves during critical incidents, and building high‑performing, scalable teams.

  Skills

  • Threat detection and response
  • Security engineering
  • Vulnerability management
  • Security monitoring
  • SIEM, SOAR, EDR/XDR, vulnerability scanners
  • Incident and crisis management
  • Process optimization, playbooks, automation
  • KPI/KRI definition and tracking (MTTR, MTTD, containment rates)
  • Frameworks: NIST CSF, MITRE ATT&CK, ISO 27001
  • Cross‑functional collaboration with Technology Operations, Infrastructure, Cloud, Application, IT Security, Risk, Compliance, Legal
  • Advising executive leadership on security posture and risk

  Benefits

  • Medical, dental, vision
  • 401(k) match
  • Paid time off, PTO cash out
  • Family resources, E