Director Engineering, Cybersecurity Architecture
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting: It includes company description, then "Life @ToryBurch is Special Because: ..." which describes benefits, culture, etc. Then "This Role Is Tailor-Made For You Because ..." then "A Day In The Life" describing responsibilities. Then "To Land This Role" describing qualifications/requirements.
We need to decide sections: Possibly "About the role" (or "About the company") could contain the company description and culture. "Responsibilities" from "A Day In The Life". "Requirements" or "Qualifications" from "To Land This Role". Benefits maybe from "Life @ToryBurch is Special Because:" includes benefits: generous employee discount, exclusive sample sales, free executive coaching, volunteer days, etc. Also mention competitive pay, rewarding high performance, well-being benefits, mental/physical health, financial security, wellness. So we have benefits content. Pay: they say "believe in paying competitively and rewarding for high performance." Not specific numbers, but it's a statement about pay. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. They do state paying competitively, but not specific numbers. Is that enough? It says "believe in paying competitively and rewarding for high performance." That's a statement about pay. Could include a Pay section with that statement. However they also say "generous benefits". So we can include Benefits section.
Schedule: not mentioned. So omit Schedule.
We need to avoid filler like "commensurate with experience". Not present.
We need to use
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include details from each part.
Let's extract sections:
1. About the role / About the company: The initial paragraph: "We are an American luxury lifestyle brand, founded in 2004. Anchored in the casual elegance of American sportswear, Tory’s design philosophy is defined by effortless silhouettes, innovative materials, eclectic juxtapositions of color, and the tension of past and present. The collections include ready-to-wear, handbags, footwear, accessories, jewelry, home and beauty. Empowering women is the company’s guiding principle, expressed through Tory’s collections and reflected in the company culture as well as the work of the Tory Burch Foundation. Established in 2009, the Foundation provides women entrepreneurs in the United States with access to capital, education and community. You are seeking a work environment where people are encouraged to dream, explore, discover and, as important, laugh together. If you’re prepared to work hard, create impact, and have fun while doing it, we would love to have you join #TeamTory. Apply today!" This is marketing fluff but substantive. We'll put under
About the role
maybe.
2. Life @ToryBurch is Special Because: This includes benefits and culture. Let's extract:
"When you join us, you’re joining a global, purpose-led company on an exciting growth journey with an amazing culture and great benefits. Our culture is welcoming and inclusive -- everyone is empowered to make a difference.We have the best team in the world and believe in paying competitively and rewarding for high performance.Your overall well-being is important to us; we offer generous benefits to help you take care of your mental and physical health, create financial security, and achieve wellness in all areas of your life.We love seeing our employees wear our beautiful collections. You’ll receive a generous employee discount and access to exclusive sample sales.We are invested in your professional growth – you’ll have access to free executive coaching on-demand.We believe in the importance of giving back and you’ll have many opportunities to do just that through the Tory Burch Foundation and paid volunteer days."
We can split into Benefits (maybe also culture). Since we have a Benefits section, we can put that here. Also we could have a separate "About the role" for culture. But we need to avoid thin sections. Perhaps combine culture and benefits into one "About the role" or "Life at ToryBurch". However instructions say use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have About the role (company overview), Responsibilities (day in the life), Requirements/Qualifications (to land this role), Benefits (life @ ToryBurch), Pay (statement about paying competitively). We'll avoid Schedule.
Now Responsibilities: from "A Day In The Life". That's a long paragraph with many duties. We need to turn into - list items. We must preserve all substantive information, not summarize away detail. So we need to break the long paragraph into list items each covering a duty. However we must not lose detail. Could create many list items, each representing a duty. That's okay.
We need to extract each duty sentence. Let's parse:
"Lead the Cybersecurity Architecture & Engineering function and provide direction, coaching, prioritization, performance support, and professional development for the Cybersecurity Architect and Cybersecurity Engineer."
"Own the end-to-end Cybersecurity Architecture & Engineering service offering, including service scope, intake, engagement model, standards, deliverables, roadmaps, metrics, and continuous improvement."
"Define and maintain enterprise security architecture principles, standards, reference architectures, reusable patterns, engineering requirements, and security guardrails."
"Partner closely with Infrastructure, Digital, Data, Enterprise Architecture, and Application teams to integrate security into planning, architecture, design, build, deployment, migration, change, and operational processes."
"Design and establish new security architecture and engineering processes where existing processes do not adequately support secure technology delivery."
"Establish security participation in architecture review boards and related technology governance forums."
"Develop practical, low-friction intake, triage, review, escalation, exception, and approval processes that engage security early and provide clear, timely guidance."
"Ensure security architecture reviews and design decisions occur early enough to influence solution direction, reduce rework, improve supportability, and avoid unnecessary delivery delays."
"Lead security architecture reviews for cloud initiatives, infrastructure changes, identity services, endpoint platforms, digital capabilities, applications, integrations, APIs, data flows, collaboration services, and emerging technologies."
"Guide the design of secure end-to-end solutions that connect distributed systems and business processes through integrations, APIs, event flows, orchestration, and automated workflows."
"Ensure end-to-end designs address identity, authentication, authorization, device trust, secrets, encryption, network controls, data protection, logging, monitoring, resilience, third-party dependencies, user experience, and secure failure behavior."
"Define security architecture and engineering requirements for networks, secure connectivity, segmentation, remote access, cloud networking, platform services, and hybrid technology environments."
"Provide architecture and engineering leadership across the Microsoft ecosystem, including Microsoft Entra, Microsoft Intune, Microsoft 365, Azure, and related identity, endpoint, collaboration, and security capabilities."
"Guide the design of modern identity and access capabilities, including adaptive and risk-based access, device trust, authentication strength, passwordless authentication, passkeys, privileged access, application access, and identity lifecycle integration."
"Establish reusable security patterns and guardrails for managed devices, conditional access, authentication, administrative access, application access, secure collaboration, and platform configuration."
"Ensure identity, endpoint, and collaboration controls are risk-based, forward-looking, and designed to minimize unnecessary user friction while maintaining appropriate protection, governance, visibility, and resilience."
"Lead security architecture and engineering considerations for platform modernization and technology transitions, ensuring integrations, dependencies, user impact, operational readiness, control design, and support requirements are addressed as part of the end-to-end solution."
"Evaluate new and evolving platform capabilities and determine how they should be adopted, configured, integrated, and governed to improve security outcomes, operational efficiency, and user experience."
"Establish and mature application security capabilities, including secure software development lifecycle practices, threat modeling, application architecture reviews, secure coding requirements, and engineering standards."
"Implement and govern DevSecOps practices, including static application security testing, dynamic application security testing, software composition analysis, secrets scanning, container security, API security, and Infrastructure-as-Code security controls."
"Ensure code scanning and automated security validation are embedded into CI/CD pipelines, supported by actionable remediation workflows, and measured for effectiveness."
"Define cloud security requirements and reusable patterns for Microsoft Azure and Google Cloud Platform services, identities, networks, workloads, data services, APIs, logging, monitoring, and platform configurations."
"Drive remediation of architectural and engineering risks through collaboration with technology owners and business stakeholders."
"Develop architecture and engineering roadmaps aligned to cybersecurity strategy, enterprise technology direction, platform modernization, and business objectives."
"Establish metrics, KPIs, and maturity measures that demonstrate early security engagement, review efficiency, adoption of secure patterns, control coverage, user impact, and measurable risk reduction."
That's many items. We'll output as
- each.
Now Requirements/Qualifications: from "To Land This Role". It lists many bullet-like sentences but not formatted as list. We need to turn into
- list.
Let's extract each requirement:
"Bachelor's degree in Cybersecurity, Information Technology, Computer Science, Engineering, or a related discipline, or equivalent practical experience."
"Ten or more years of progressive cybersecurity experience with significant security architecture, engineering, and technical leadership responsibilities."
"Experience managing technical security professionals and leading complex cross-functional initiatives."
"Demonstrated ownership of a broad security architecture and engineering service portfolio spanning infrastructure, network, identity, endpoint, cloud, application, data protection, and enterprise technology domains."
"Strong architecture and engineering experience in cloud environments, including Microsoft Azure and Google Cloud Platform."
"Experience defining cloud security architectures, guardrails, reusable patterns, and controls across identities, networks, workloads, platforms, applications, APIs, logging, monitoring, and data services."
"Advanced architecture and engineering experience across the Microsoft ecosystem, including Microsoft Entra, Microsoft Intune, Microsoft 365, Azure, and related identity, endpoint, device management, collaboration, and security capabilities."
"Demonstrated experience designing identity-first security architectures using adaptive and risk-based access controls, managed-device signals, modern authentication, authentication-strength requirements, passwordless authentication, passkeys, privileged access controls, and application access policies."
"Strong knowledge of modern identity architecture, including authentication, authorization, federation, application integration, identity lifecycle management, device trust, privileged access, and phishing-resistant authentication."
"Experience developing secure and usable access patterns that balance risk, business requirements, operational supportability, and user experience."
"Experience designing security architecture for enterprise endpoints, collaboration platforms, network services, cloud services, SaaS applications, and hybrid technology environments."
for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting: It includes company description, then "Life @ToryBurch is Special Because: ..." which describes benefits, culture, etc. Then "This Role Is Tailor-Made For You Because ..." then "A Day In The Life" describing responsibilities. Then "To Land This Role" describing qualifications/requirements. We need to decide sections: Possibly "About the role" (or "About the company") could contain the company description and culture. "Responsibilities" from "A Day In The Life". "Requirements" or "Qualifications" from "To Land This Role". Benefits maybe from "Life @ToryBurch is Special Because:" includes benefits: generous employee discount, exclusive sample sales, free executive coaching, volunteer days, etc. Also mention competitive pay, rewarding high performance, well-being benefits, mental/physical health, financial security, wellness. So we have benefits content. Pay: they say "believe in paying competitively and rewarding for high performance." Not specific numbers, but it's a statement about pay. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. They do state paying competitively, but not specific numbers. Is that enough? It says "believe in paying competitively and rewarding for high performance." That's a statement about pay. Could include a Pay section with that statement. However they also say "generous benefits". So we can include Benefits section. Schedule: not mentioned. So omit Schedule. We need to avoid filler like "commensurate with experience". Not present. We need to use
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include details from each part.
Let's extract sections:
1. About the role / About the company: The initial paragraph: "We are an American luxury lifestyle brand, founded in 2004. Anchored in the casual elegance of American sportswear, Tory’s design philosophy is defined by effortless silhouettes, innovative materials, eclectic juxtapositions of color, and the tension of past and present. The collections include ready-to-wear, handbags, footwear, accessories, jewelry, home and beauty. Empowering women is the company’s guiding principle, expressed through Tory’s collections and reflected in the company culture as well as the work of the Tory Burch Foundation. Established in 2009, the Foundation provides women entrepreneurs in the United States with access to capital, education and community. You are seeking a work environment where people are encouraged to dream, explore, discover and, as important, laugh together. If you’re prepared to work hard, create impact, and have fun while doing it, we would love to have you join #TeamTory. Apply today!" This is marketing fluff but substantive. We'll put under
About the role
maybe.
2. Life @ToryBurch is Special Because: This includes benefits and culture. Let's extract:
"When you join us, you’re joining a global, purpose-led company on an exciting growth journey with an amazing culture and great benefits. Our culture is welcoming and inclusive -- everyone is empowered to make a difference.We have the best team in the world and believe in paying competitively and rewarding for high performance.Your overall well-being is important to us; we offer generous benefits to help you take care of your mental and physical health, create financial security, and achieve wellness in all areas of your life.We love seeing our employees wear our beautiful collections. You’ll receive a generous employee discount and access to exclusive sample sales.We are invested in your professional growth – you’ll have access to free executive coaching on-demand.We believe in the importance of giving back and you’ll have many opportunities to do just that through the Tory Burch Foundation and paid volunteer days."
We can split into Benefits (maybe also culture). Since we have a Benefits section, we can put that here. Also we could have a separate "About the role" for culture. But we need to avoid thin sections. Perhaps combine culture and benefits into one "About the role" or "Life at ToryBurch". However instructions say use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have About the role (company overview), Responsibilities (day in the life), Requirements/Qualifications (to land this role), Benefits (life @ ToryBurch), Pay (statement about paying competitively). We'll avoid Schedule.
Now Responsibilities: from "A Day In The Life". That's a long paragraph with many duties. We need to turn into - list items. We must preserve all substantive information, not summarize away detail. So we need to break the long paragraph into list items each covering a duty. However we must not lose detail. Could create many list items, each representing a duty. That's okay.
We need to extract each duty sentence. Let's parse:
"Lead the Cybersecurity Architecture & Engineering function and provide direction, coaching, prioritization, performance support, and professional development for the Cybersecurity Architect and Cybersecurity Engineer."
"Own the end-to-end Cybersecurity Architecture & Engineering service offering, including service scope, intake, engagement model, standards, deliverables, roadmaps, metrics, and continuous improvement."
"Define and maintain enterprise security architecture principles, standards, reference architectures, reusable patterns, engineering requirements, and security guardrails."
"Partner closely with Infrastructure, Digital, Data, Enterprise Architecture, and Application teams to integrate security into planning, architecture, design, build, deployment, migration, change, and operational processes."
"Design and establish new security architecture and engineering processes where existing processes do not adequately support secure technology delivery."
"Establish security participation in architecture review boards and related technology governance forums."
"Develop practical, low-friction intake, triage, review, escalation, exception, and approval processes that engage security early and provide clear, timely guidance."
"Ensure security architecture reviews and design decisions occur early enough to influence solution direction, reduce rework, improve supportability, and avoid unnecessary delivery delays."
"Lead security architecture reviews for cloud initiatives, infrastructure changes, identity services, endpoint platforms, digital capabilities, applications, integrations, APIs, data flows, collaboration services, and emerging technologies."
"Guide the design of secure end-to-end solutions that connect distributed systems and business processes through integrations, APIs, event flows, orchestration, and automated workflows."
"Ensure end-to-end designs address identity, authentication, authorization, device trust, secrets, encryption, network controls, data protection, logging, monitoring, resilience, third-party dependencies, user experience, and secure failure behavior."
"Define security architecture and engineering requirements for networks, secure connectivity, segmentation, remote access, cloud networking, platform services, and hybrid technology environments."
"Provide architecture and engineering leadership across the Microsoft ecosystem, including Microsoft Entra, Microsoft Intune, Microsoft 365, Azure, and related identity, endpoint, collaboration, and security capabilities."
"Guide the design of modern identity and access capabilities, including adaptive and risk-based access, device trust, authentication strength, passwordless authentication, passkeys, privileged access, application access, and identity lifecycle integration."
"Establish reusable security patterns and guardrails for managed devices, conditional access, authentication, administrative access, application access, secure collaboration, and platform configuration."
"Ensure identity, endpoint, and collaboration controls are risk-based, forward-looking, and designed to minimize unnecessary user friction while maintaining appropriate protection, governance, visibility, and resilience."
"Lead security architecture and engineering considerations for platform modernization and technology transitions, ensuring integrations, dependencies, user impact, operational readiness, control design, and support requirements are addressed as part of the end-to-end solution."
"Evaluate new and evolving platform capabilities and determine how they should be adopted, configured, integrated, and governed to improve security outcomes, operational efficiency, and user experience."
"Establish and mature application security capabilities, including secure software development lifecycle practices, threat modeling, application architecture reviews, secure coding requirements, and engineering standards."
"Implement and govern DevSecOps practices, including static application security testing, dynamic application security testing, software composition analysis, secrets scanning, container security, API security, and Infrastructure-as-Code security controls."
"Ensure code scanning and automated security validation are embedded into CI/CD pipelines, supported by actionable remediation workflows, and measured for effectiveness."
"Define cloud security requirements and reusable patterns for Microsoft Azure and Google Cloud Platform services, identities, networks, workloads, data services, APIs, logging, monitoring, and platform configurations."
"Drive remediation of architectural and engineering risks through collaboration with technology owners and business stakeholders."
"Develop architecture and engineering roadmaps aligned to cybersecurity strategy, enterprise technology direction, platform modernization, and business objectives."
"Establish metrics, KPIs, and maturity measures that demonstrate early security engagement, review efficiency, adoption of secure patterns, control coverage, user impact, and measurable risk reduction."
That's many items. We'll output as
- each.
Now Requirements/Qualifications: from "To Land This Role". It lists many bullet-like sentences but not formatted as list. We need to turn into
- list.
Let's extract each requirement:
"Bachelor's degree in Cybersecurity, Information Technology, Computer Science, Engineering, or a related discipline, or equivalent practical experience."
"Ten or more years of progressive cybersecurity experience with significant security architecture, engineering, and technical leadership responsibilities."
"Experience managing technical security professionals and leading complex cross-functional initiatives."
"Demonstrated ownership of a broad security architecture and engineering service portfolio spanning infrastructure, network, identity, endpoint, cloud, application, data protection, and enterprise technology domains."
"Strong architecture and engineering experience in cloud environments, including Microsoft Azure and Google Cloud Platform."
"Experience defining cloud security architectures, guardrails, reusable patterns, and controls across identities, networks, workloads, platforms, applications, APIs, logging, monitoring, and data services."
"Advanced architecture and engineering experience across the Microsoft ecosystem, including Microsoft Entra, Microsoft Intune, Microsoft 365, Azure, and related identity, endpoint, device management, collaboration, and security capabilities."
"Demonstrated experience designing identity-first security architectures using adaptive and risk-based access controls, managed-device signals, modern authentication, authentication-strength requirements, passwordless authentication, passkeys, privileged access controls, and application access policies."
"Strong knowledge of modern identity architecture, including authentication, authorization, federation, application integration, identity lifecycle management, device trust, privileged access, and phishing-resistant authentication."
"Experience developing secure and usable access patterns that balance risk, business requirements, operational supportability, and user experience."
"Experience designing security architecture for enterprise endpoints, collaboration platforms, network services, cloud services, SaaS applications, and hybrid technology environments."
for prose. We need to preserve all substantive information, not invent or summarize away detail. So we need to include details from each part. Let's extract sections: 1. About the role / About the company: The initial paragraph: "We are an American luxury lifestyle brand, founded in 2004. Anchored in the casual elegance of American sportswear, Tory’s design philosophy is defined by effortless silhouettes, innovative materials, eclectic juxtapositions of color, and the tension of past and present. The collections include ready-to-wear, handbags, footwear, accessories, jewelry, home and beauty. Empowering women is the company’s guiding principle, expressed through Tory’s collections and reflected in the company culture as well as the work of the Tory Burch Foundation. Established in 2009, the Foundation provides women entrepreneurs in the United States with access to capital, education and community. You are seeking a work environment where people are encouraged to dream, explore, discover and, as important, laugh together. If you’re prepared to work hard, create impact, and have fun while doing it, we would love to have you join #TeamTory. Apply today!" This is marketing fluff but substantive. We'll put under
About the role
maybe. 2. Life @ToryBurch is Special Because: This includes benefits and culture. Let's extract: "When you join us, you’re joining a global, purpose-led company on an exciting growth journey with an amazing culture and great benefits. Our culture is welcoming and inclusive -- everyone is empowered to make a difference.We have the best team in the world and believe in paying competitively and rewarding for high performance.Your overall well-being is important to us; we offer generous benefits to help you take care of your mental and physical health, create financial security, and achieve wellness in all areas of your life.We love seeing our employees wear our beautiful collections. You’ll receive a generous employee discount and access to exclusive sample sales.We are invested in your professional growth – you’ll have access to free executive coaching on-demand.We believe in the importance of giving back and you’ll have many opportunities to do just that through the Tory Burch Foundation and paid volunteer days." We can split into Benefits (maybe also culture). Since we have a Benefits section, we can put that here. Also we could have a separate "About the role" for culture. But we need to avoid thin sections. Perhaps combine culture and benefits into one "About the role" or "Life at ToryBurch". However instructions say use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have About the role (company overview), Responsibilities (day in the life), Requirements/Qualifications (to land this role), Benefits (life @ ToryBurch), Pay (statement about paying competitively). We'll avoid Schedule. Now Responsibilities: from "A Day In The Life". That's a long paragraph with many duties. We need to turn into- list items. We must preserve all substantive information, not summarize away detail. So we need to break the long paragraph into list items each covering a duty. However we must not lose detail. Could create many list items, each representing a duty. That's okay.
We need to extract each duty sentence. Let's parse:
"Lead the Cybersecurity Architecture & Engineering function and provide direction, coaching, prioritization, performance support, and professional development for the Cybersecurity Architect and Cybersecurity Engineer."
"Own the end-to-end Cybersecurity Architecture & Engineering service offering, including service scope, intake, engagement model, standards, deliverables, roadmaps, metrics, and continuous improvement."
"Define and maintain enterprise security architecture principles, standards, reference architectures, reusable patterns, engineering requirements, and security guardrails."
"Partner closely with Infrastructure, Digital, Data, Enterprise Architecture, and Application teams to integrate security into planning, architecture, design, build, deployment, migration, change, and operational processes."
"Design and establish new security architecture and engineering processes where existing processes do not adequately support secure technology delivery."
"Establish security participation in architecture review boards and related technology governance forums."
"Develop practical, low-friction intake, triage, review, escalation, exception, and approval processes that engage security early and provide clear, timely guidance."
"Ensure security architecture reviews and design decisions occur early enough to influence solution direction, reduce rework, improve supportability, and avoid unnecessary delivery delays."
"Lead security architecture reviews for cloud initiatives, infrastructure changes, identity services, endpoint platforms, digital capabilities, applications, integrations, APIs, data flows, collaboration services, and emerging technologies."
"Guide the design of secure end-to-end solutions that connect distributed systems and business processes through integrations, APIs, event flows, orchestration, and automated workflows."
"Ensure end-to-end designs address identity, authentication, authorization, device trust, secrets, encryption, network controls, data protection, logging, monitoring, resilience, third-party dependencies, user experience, and secure failure behavior."
"Define security architecture and engineering requirements for networks, secure connectivity, segmentation, remote access, cloud networking, platform services, and hybrid technology environments."
"Provide architecture and engineering leadership across the Microsoft ecosystem, including Microsoft Entra, Microsoft Intune, Microsoft 365, Azure, and related identity, endpoint, collaboration, and security capabilities."
"Guide the design of modern identity and access capabilities, including adaptive and risk-based access, device trust, authentication strength, passwordless authentication, passkeys, privileged access, application access, and identity lifecycle integration."
"Establish reusable security patterns and guardrails for managed devices, conditional access, authentication, administrative access, application access, secure collaboration, and platform configuration."
"Ensure identity, endpoint, and collaboration controls are risk-based, forward-looking, and designed to minimize unnecessary user friction while maintaining appropriate protection, governance, visibility, and resilience."
"Lead security architecture and engineering considerations for platform modernization and technology transitions, ensuring integrations, dependencies, user impact, operational readiness, control design, and support requirements are addressed as part of the end-to-end solution."
"Evaluate new and evolving platform capabilities and determine how they should be adopted, configured, integrated, and governed to improve security outcomes, operational efficiency, and user experience."
"Establish and mature application security capabilities, including secure software development lifecycle practices, threat modeling, application architecture reviews, secure coding requirements, and engineering standards."
"Implement and govern DevSecOps practices, including static application security testing, dynamic application security testing, software composition analysis, secrets scanning, container security, API security, and Infrastructure-as-Code security controls."
"Ensure code scanning and automated security validation are embedded into CI/CD pipelines, supported by actionable remediation workflows, and measured for effectiveness."
"Define cloud security requirements and reusable patterns for Microsoft Azure and Google Cloud Platform services, identities, networks, workloads, data services, APIs, logging, monitoring, and platform configurations."
"Drive remediation of architectural and engineering risks through collaboration with technology owners and business stakeholders."
"Develop architecture and engineering roadmaps aligned to cybersecurity strategy, enterprise technology direction, platform modernization, and business objectives."
"Establish metrics, KPIs, and maturity measures that demonstrate early security engagement, review efficiency, adoption of secure patterns, control coverage, user impact, and measurable risk reduction."
That's many items. We'll output as
- each.
Now Requirements/Qualifications: from "To Land This Role". It lists many bullet-like sentences but not formatted as list. We need to turn into
- list. Let's extract each requirement: "Bachelor's degree in Cybersecurity, Information Technology, Computer Science, Engineering, or a related discipline, or equivalent practical experience." "Ten or more years of progressive cybersecurity experience with significant security architecture, engineering, and technical leadership responsibilities." "Experience managing technical security professionals and leading complex cross-functional initiatives." "Demonstrated ownership of a broad security architecture and engineering service portfolio spanning infrastructure, network, identity, endpoint, cloud, application, data protection, and enterprise technology domains." "Strong architecture and engineering experience in cloud environments, including Microsoft Azure and Google Cloud Platform." "Experience defining cloud security architectures, guardrails, reusable patterns, and controls across identities, networks, workloads, platforms, applications, APIs, logging, monitoring, and data services." "Advanced architecture and engineering experience across the Microsoft ecosystem, including Microsoft Entra, Microsoft Intune, Microsoft 365, Azure, and related identity, endpoint, device management, collaboration, and security capabilities." "Demonstrated experience designing identity-first security architectures using adaptive and risk-based access controls, managed-device signals, modern authentication, authentication-strength requirements, passwordless authentication, passkeys, privileged access controls, and application access policies." "Strong knowledge of modern identity architecture, including authentication, authorization, federation, application integration, identity lifecycle management, device trust, privileged access, and phishing-resistant authentication." "Experience developing secure and usable access patterns that balance risk, business requirements, operational supportability, and user experience." "Experience designing security architecture for enterprise endpoints, collaboration platforms, network services, cloud services, SaaS applications, and hybrid technology environments."
- each.
Now Requirements/Qualifications: from "To Land This Role". It lists many bullet-like sentences but not formatted as list. We need to turn into