Microsoft Security - Security Operations & Threat Protection

We need to output only HTML fragment, no /, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We need to extract content. The posting includes: - About Slalom (intro) – maybe not needed as heading? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). 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. We need to preserve all substantive information; remove boilerplate like EEO, legal, etc. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to include sections only when posting has real specific content. Let's parse the content: - About Slalom: description of company. Could be considered "About the role"? Actually "About Slalom" is company overview. Might be considered "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could have "About the role" heading containing description of role (the "About the Role" section). The "About Slalom" could be omitted? It's not required but maybe we can include as a short paragraph under "About the role"? But we must preserve all substantive information. The "About Slalom" is substantive about company; but not required heading. Could we put it under a

before any heading? The instruction says output ONLY the HTML fragment; we can include

elements not under headings? Probably yes. But they said use

for section headings (list). It doesn't forbid other elements. We can include a

for company overview before headings. But we need to avoid boilerplate like EEO etc. So we will strip those sections. Let's identify substantive sections: - About Slalom (company description) - About the Role (role description) - What You'll Do (Responsibilities) – includes bullet points: Build the Microsoft SecOps Capability (with subpoints), Deliver Client Outcomes (subpoints) - Required Qualifications (with sub-sections: Microsoft Security Expertise, Architecture, Go-to-Market) - Preferred Certifications (list) - About Us (company culture) – maybe we can include as "About Us" but not in heading list; could be omitted? It's substantive but not required heading; we could include as a

after headings. - Compensation and Benefits (Pay and Benefits) – includes salary ranges, bonus, benefits description. - EEO and Accommodations (boilerplate) – remove. - Also note: "We will accept applicants until 10/15 date, or until the position is filled." That's application instruction; remove. - "Please note, this recipient is not able to support recruitment inquiries beyond this purpose." Also remove. - "If you have questions or concerns about the pay range or other compensation information in this posting, please contact us at: peopleone@slalom.com." That's contact info; maybe we can keep as minor metadata? It's not boilerplate but it's application instruction? Might be considered contact for compensation questions; could be kept as a short

maybe under Pay? But instruction says fold minor metadata into a short

or drop it. Could include as a

after Pay section. We need to avoid duplication. Now decide headings: - About the role: we can combine "About the Role" description (the paragraph after "About the Role") plus maybe "About Slalom"? But "About Slalom" is company overview; maybe we can put that as a separate

before heading. - Responsibilities: from "What You'll Do" – we can make a Responsibilities section with

• for each bullet and sub-bullets. - Requirements: maybe combine Required Qualifications and Preferred Certifications? The instruction lists Requirements and Qualifications as separate possible headings. We could have Requirements (maybe for required qualifications) and Qualifications (maybe for preferred certifications). Or we could have Requirements covering both required and preferred? But better to follow typical: Requirements = required qualifications; Qualifications = preferred certifications. We'll do that. - Skills: maybe we can extract skills from required qualifications? Could be redundant. The instruction says prefer a few substantive sections over many thin ones. If we have Requirements and Qualifications, maybe we can skip Skills unless there is explicit skills list. There's no separate skills list; we could omit Skills. - Benefits: we have benefits description in Compensation and Benefits section. We'll make Benefits heading. - Pay: we have salary range details. We'll make Pay heading. - Schedule: not mentioned; omit. Now we need to ensure we don't include headings with filler text like "commensurate with experience". Not present. Now craft HTML. We'll start with a

  for company overview (About Slalom). Then

  About the role

  with

  containing the role description paragraph. Then

  Responsibilities

  with
  • for each top-level bullet: "Build the Microsoft SecOps Capability" and "Deliver Client Outcomes". Under each, we need subpoints. Could nest
    • inside
    • . That's acceptable. Then

      Requirements

      with
      • for each required qualification category: Microsoft Security Expertise, Architecture, Go-to-Market. Each may have subpoints; we can nest. Then

        Qualifications

        for Preferred Certifications: list. Then

        Benefits

        with

        describing benefits (time off, parental leave, 401k, health, etc.) plus the $350 reimbursement account and discounted insurance. Then

        Pay

        with

        containing salary ranges and bonus note, plus contact email maybe. We must not include application instructions like "We will accept applicants until 10/15 date". Remove. We must not include EEO etc. Now ensure we preserve all substantive information: Let's extract details. About Slalom paragraph: "Slalom is a global business and technology consulting company committed to helping people and organizations dream bigger, move faster, and build better tomorrows. Our Microsoft Security organization brings together deep expertise across Microsoft's security, identity, data protection, compliance, cloud, and AI security ecosystem." That's it. About the Role paragraph: "We are seeking a Senior Principal – Microsoft Security, Security Operations & Threat Protection to establish and lead Slalom's next-generation Defender, Microsoft Sentinel, and Project Perception capability. This is a strategic leadership role for an experienced Microsoft security practitioner who combines deep technical expertise in Security Operations with enterprise and security architecture, consulting leadership, business development, and Microsoft ecosystem experience. You will be responsible for building this capability from the ground up—developing the technical vision, creating differentiated offerings and intellectual property, developing client relationships, partnering with Microsoft, supporting sales pursuits, and building the skills necessary to scale the capability across Slalom. This is not simply an implementation role. You will build the capability, sell the capability, deliver the capability, and develop the people who will scale it." That's the role description. Now Responsibilities: Under "What You'll Do": - Build the Microsoft SecOps Capability - Establish Slalom's Microsoft Security Operations and Threat Protection capability across Microsoft Defender, Microsoft Sentinel, and Project Perception. - Define the capability's technical strategy, architecture, service offerings, delivery methodology, and roadmap. - Develop a differentiated point of view for modern Microsoft SecOps and XDR. - Establish repeatable implementation patterns, accelerators, reference architectures, playbooks, and delivery assets. - Define how Defender, Sentinel, Entra, Intune, Purview, Defender for Cloud, Security Copilot, and other Microsoft Security technologies work together as an enterprise security platform. - Establish the technical standards and architectural principles for the capability. - Deliver Client Outcomes - Serve as a senior technical leader on strategic client engagements. - Lead complex Microsoft Security transformations from strategy through implementation and operationalization. - Establish security operations target operating models. - Assess existing SOC capabilities and develop transformation roadmaps. - Lead implementation of Defender and Sentinel solutions. - Design detection engineering and incident response capabilities. - Establish security monitoring and operational processes. - Help clients transition from implementation to sustainable security operations. Now Required Qualifications categories: Microsoft Security Expertise: - Advise CISOs, CIOs, security executives, and enterprise architects on modernizing security operations. - Design security monitoring, detection, response, automation, and operating models. - Translate complex technical capabilities into business outcomes and executive-level recommendations. - Deep, hands-on expertise with architecting Microsoft Security technologies, particularly: - Microsoft Defender XDR and Defender Suite - Microsoft Sentinel - Graph Security Copilot and Project Perception - Strong understanding of Security Operations Center (SOC) processes, technologies, and operating models. - Experience designing and implementing enterprise-scale SIEM/SOAR/XDR solutions. - Strong understanding of detection engineering, threat intelligence, incident response, security monitoring, and security analytics. - Experience integrating Microsoft Security with broader enterprise security ecosystems. Architecture: - Demonstrated experience developing enterprise security architectures. - Strong understanding of Zero Trust architecture and modern security operating models. - Ability to translate business and security requirements into enterprise-scale technical architectures. - Experience leading architecture decisions across complex, global environments. - Ability to communicate technical architecture effectively to both executives and engineering teams. - Significant experience leading complex cybersecurity transformation programs. Go-to-Market: - Demonstrated business development and sales experience within the Microsoft ecosystem. - Proven experience creating and selling cybersecurity offerings. - Experience leading technical sales pursuits and executive presentations - Experience developing proposals, SOWs, solution architectures, demos, and GTM assets. - Strong understanding of Microsoft partner and co-sell motions. Preferred Certifications: - Microsoft security certifications such as: SC-100: Cybersecurity Architect Expert, SC-200: Security Operations Analyst, SC-300: Identity and Access Administrator, AZ-500: Azure Security Engineer Associate, MS-500 / equivalent security credentials, CISSP, CCSP, or equivalent cybersecurity certification. Now Benefits paragraph from "Compensation and Benefits": "Slalom prides itself on helping team members thrive in their work and life. As a result, Slalom is proud to invest in benefits that include meaningful time off and paid holidays, parental leave, 401(k) with a match, a range of choices for highly subsidized health, dental, & vision coverage, adoption and fertility assistance, and short/long-term disability. We also offer yearly $350 reimbursement account for any well-being-related expenses, as well as discounted home, auto, and pet insurance." Now Pay paragraph: "Slalom is committed to fair and equitable compensation practices. For this role, we are hiring at the following levels and targeted base pay salary ranges: The targeted base salary pay range for Senior Principal in San Diego, Los Angeles, Orange County, Seattle, Houston, New Jersey, New York City, Westchester, Boston, Washington DC is $186,000 to $233,000. The target base salary range for Senior Principal in all other markets where Slalom is, except San Francisco and Silicon Valley is $171,000 to $214,000. In addition, individuals may be eligible for an annual discretionary bonus. Actual compensation will depend upon an individual’s skills, experience, qualifications, location, and other relevant factors. The salary pay range is subject to change and