Microsoft Security - Security Operations & Threat Protection
or drop it." They didn't say to drop About Us. But earlier they said "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." About Us is not those. Could keep as a section maybe "About Slalom"? But they also said "About Slalom" at top is also descriptive. Might be considered boilerplate? It's generic marketing. I'd lean to keep only sections that have specific role content: About the Role, What You'll Do (Responsibilities), Required Qualifications (maybe split into sub-sections?), Preferred Certifications, Compensation and Benefits (including Benefits and Pay). Possibly also "About Us" could be omitted to keep thin. We must not create sections with filler like "commensurate with experience". We have actual salary ranges, so Pay section is valid. Benefits section: they list benefits. So we can have Benefits section. We need to use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. So headings: About the role, Responsibilities, Requirements, Qualifications? Actually they said use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can choose appropriate.
We have content for About the role (intro). Responsibilities (What You'll Do). Requirements (maybe combine Required Qualifications subpoints). Could also have Qualifications (Preferred Certifications). Benefits. Pay.
We must not create Schedule section because not present.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from those sections.
We need to convert paragraphs into
. For lists, we need
- . For subheadings inside sections? Not required but we could keep as
with bold? But we must not invent headings not allowed? Only allowed headings are those listed. So we cannot add extra headings like "Microsoft Security Expertise". We could embed that content in
or maybe within
- but it's not a list. Better to keep as
paragraphs.
Thus structure:
About the role
... (the intro paragraph about role)
Responsibilities
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.
But note we have a heading "Deliver Client Outcomes" as a subsection; we could keep as heading? Not allowed. Could treat as
with bold? But we can't add extra headings. So we could just make a
"Deliver Client Outcomes:" then list. Or we could incorporate into a single
with all items. However the instruction: Use - for any list of duties/requirements/benefits. So we can combine all duty items into one list. But we need to preserve the grouping? Not required. We'll just make a single list of all duties.
Thus:
Responsibilities
- 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.
- 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 Requirements section: we have Required Qualifications with subparts: Microsoft Security Expertise, Architecture, Go-to-Market. We'll combine into a list? But they are paragraphs describing expertise. Could treat each as list items? They are not exactly duties but qualifications. We'll use - for any list of duties/requirements/benefits. So we can make a list of qualification statements.
Thus:
Requirements
- 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.
- 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.
- 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.
Now Preferred Certifications: we could make a section "Qualifications" maybe? But we already used Requirements. Could add a section "Preferred Certifications" as Qualifications
maybe? The instruction list includes Qualifications as a possible heading. We'll use Qualifications
for preferred certifications.
Thus:
Qualifications
- 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 section: we have paragraph about benefits. We'll make Benefits
and then a with the benefits description. Also we could list specific benefits as
- . The instruction: Use
- for any list of duties/requirements/benefits. So we should list benefits as list items.
Thus:
Benefits
- 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
- Short/long-term disability
- Yearly $350 reimbursement account for any well-being-related expenses
- Discounted home, auto, and pet insurance
Now Pay section: we have salary ranges. We'll make Pay
and then a with the salary ranges and bonus info.
We must not include filler like "commensurate with experience". We have actual numbers.
Thus:
Pay
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
for prose. We must not repeat job title as heading. So headings: About the role, Responsibilities, Requirements, Qualifications? Actually they said use headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can choose appropriate. We have content for About the role (intro). Responsibilities (What You'll Do). Requirements (maybe combine Required Qualifications subpoints). Could also have Qualifications (Preferred Certifications). Benefits. Pay. We must not create Schedule section because not present. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from those sections. We need to convert paragraphs into
. For lists, we need
- . For subheadings inside sections? Not required but we could keep as
with bold? But we must not invent headings not allowed? Only allowed headings are those listed. So we cannot add extra headings like "Microsoft Security Expertise". We could embed that content in
or maybe within
- but it's not a list. Better to keep as
paragraphs. Thus structure:
About the role
... (the intro paragraph about role)
Responsibilities
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.
heading? Not allowed. Could treat as
with bold? But we can't add extra headings. So we could just make a
"Deliver Client Outcomes:" then list. Or we could incorporate into a single
- with all items. However the instruction: Use
- for any list of duties/requirements/benefits. So we can combine all duty items into one list. But we need to preserve the grouping? Not required. We'll just make a single list of all duties.
Thus:
Responsibilities
- 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.
- 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.
- for any list of duties/requirements/benefits. So we can make a list of qualification statements.
Thus:
Requirements
- 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.
- 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.
- 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.
Qualifications
maybe? The instruction list includes Qualifications as a possible heading. We'll useQualifications
for preferred certifications. Thus:Qualifications
- 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.
Benefits
and then awith the benefits description. Also we could list specific benefits as
- . The instruction: Use
- for any list of duties/requirements/benefits. So we should list benefits as list items.
Thus:
Benefits
- 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
- Short/long-term disability
- Yearly $350 reimbursement account for any well-being-related expenses
- Discounted home, auto, and pet insurance
Pay
and then awith the salary ranges and bonus info. We must not include filler like "commensurate with experience". We have actual numbers. Thus:
Pay
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
- for any list of duties/requirements/benefits. So we should list benefits as list items.
Thus:
- but it's not a list. Better to keep as