Cloud Security Architect
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose. Do not include boilerplate like EEO, legal, application instructions, cookie/navigation, etc. Also remove duplicated lines. Must preserve all substantive info.
We need to decide which sections to include based on presence of real content.
We have:
- Who We Are Looking For: description of role responsibilities? Actually it's intro: "We are looking for a Cloud Security Architect. You will be responsible for defining, implementing, and governing cloud security architectures, standards, and security controls across public cloud, private cloud, and SaaS environments. You will partner with cloud engineering, application development, infrastructure, cybersecurity, and business stakeholders to deliver secure, resilient, and scalable cloud solutions that support the firm's digital transformation initiatives."
That's a prose paragraph. Could be under "About the role" or "Who We Are Looking For". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to those headings. Use only those headings if they have real content.
We have responsibilities: "What You Will Be Responsible For" list of duties.
We have qualifications: "Education & Preferred Qualifications" includes degree, years experience, certifications.
We have skills: "What We Value" list of skills/expertise.
We have additional requirements: "Additional Requirements" includes experience supporting enterprise cloud migration, ability to collaborate, limited travel.
We have work requirement: "Work Requirement Hybrid: Expected to work in accordance with State Street's hybrid work model. Shift: Standard business hours with flexibility to support global stakeholders across multiple time zones."
We have salary range: "Salary Range $90,000 - $157,500 Annual". Also note about location.
We have benefits: paragraph about benefits program.
We have "About State Street" description.
We need to decide which sections to include: About the role (intro), Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule? Also maybe Work Requirement could be under Schedule? Actually schedule is about shift/hours. Work requirement includes hybrid and shift. Could be under Schedule heading. But we need to only include sections if posting has real specific content. We have schedule info: "Hybrid: Expected to work in accordance with State Street's hybrid work model. Shift: Standard business hours with flexibility to support global stakeholders across multiple time zones." That's specific enough.
Pay: we have salary range.
Benefits: we have description.
About the role: we have intro paragraph.
Responsibilities: we have list.
Qualifications: we have Education & Preferred Qualifications.
Skills: we have What We Value.
We could also include Additional Requirements as part of Qualifications or maybe as separate Requirements? The instruction list includes Requirements as a possible heading. Could treat Additional Requirements as Requirements.
But we must not create thin sections. Let's see if we can combine.
We have:
- About the role: intro paragraph.
- Responsibilities: bullet list.
- Qualifications: includes education, years experience, certifications, etc.
- Skills: list of expertise.
- Benefits: paragraph.
- Pay: salary range.
- Schedule: hybrid and shift.
We should not include About State Street? That's company description, maybe not needed but could be considered "About the role"? Actually "About State Street" is generic company info, not specific to role. Might be considered boilerplate? It's not EEO/legal but still generic. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those, but it's still generic company description. Might be considered not substantive to the role? However it's part of posting. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it. Where to place? Could be under a heading like "About the company" but not in allowed headings. The allowed headings list does not include About the company. But we could embed it in a
without a heading? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, not exclusive? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those headings for sections. It doesn't forbid other headings, but suggests using those. Safer to stick to those.
Thus we can put About State Street content under About the role? Might be odd but we could include as a paragraph after the intro. Or we could create a separate section "About the company" but not in list; risk of being considered not following instruction. Better to incorporate into About the role as additional paragraph.
We must not repeat job title as heading. So no heading "Cloud Security Architect". Good.
We must not put Job ID/requisition numbers as headings; we can drop them.
We must not include boilerplate like EEO, legal, application instructions. So remove the Equal Opportunity Employer paragraph, the Job Application Disclosure, the CEO Statement, etc.
Also remove duplicated lines.
Now craft HTML.
Structure:
About the role
We are looking for a Cloud Security Architect. You will be responsible for defining, implementing, and governing cloud security architectures, standards, and security controls across public cloud, private cloud, and SaaS environments. You will partner with cloud engineering, application development, infrastructure, cybersecurity, and business stakeholders to deliver secure, resilient, and scalable cloud solutions that support the firm's digital transformation initiatives.
As the firm's adoption of cloud technologies continues to expand, this role is responsible for ensuring cloud environments are designed and operated securely, aligned with regulatory requirements, enterprise standards, and industry best practices. The team you will be joining is part of the Security Architecture organization, a function that is critical to protecting the firm's cloud platforms, applications, data, and technology services.
Across the globe, institutional investors rely on us to help them manage risk, respond to challenges, and drive performance and profitability. We keep our clients at the heart of everything we do, and smart, engaged employees are essential to our continued success. We are committed to fostering an environment where every employee feels valued and empowered to reach their full potential. As an essential partner in our shared success, you’ll benefit from inclusive development opportunities, flexible work-life support, paid volunteer days, and vibrant employee networks that keep you connected to what matters most.
But note we duplicated some sentences from "Why This Role Is Important To Us" and "About State Street". We need to preserve all substantive info, not invent. So we should include those paragraphs exactly as they appear (or close). Let's extract:
"Why This Role Is Important To Us" paragraph:
"The team you will be joining is part of the Security Architecture organization, a function that is critical to protecting the firm's cloud platforms, applications, data, and technology services. As the firm's adoption of cloud technologies continues to expand, this role is responsible for ensuring cloud environments are designed and operated securely, aligned with regulatory requirements, enterprise standards, and industry best practices."
"About State Street" paragraph:
"Across the globe, institutional investors rely on us to help them manage risk, respond to challenges, and drive performance and profitability. We keep our clients at the heart of everything we do, and smart, engaged employees are essential to our continued success. We are committed to fostering an environment where every employee feels valued and empowered to reach their full potential. As an essential partner in our shared success, you’ll benefit from inclusive development opportunities, flexible work-life support, paid volunteer days, and vibrant employee networks that keep you connected to what matters most."
We can combine them.
Now Responsibilities: list from "What You Will Be Responsible For". It's a sentence with semicolons? Actually it's a paragraph with each duty separated by periods? Let's copy:
"Design and maintain cloud security architectures, standards, patterns, and reference models across multi-cloud and hybrid-cloud environments.
Partner with cloud engineering, infrastructure, and application teams to integrate security controls into cloud platforms and services.
Lead security architecture reviews for cloud transformation initiatives, cloud-native applications, containers, Kubernetes platforms, and SaaS solutions.
Define and govern cloud security capabilities including identity and access management, network security, data protection, encryption, logging, monitoring, and security automation.
Identify cloud security risks and develop mitigation strategies aligned with enterprise risk management and regulatory requirements.
Drive adoption of Zero Trust, secure-by-design, and cloud-native security principles.
Evaluate emerging cloud security technologies and industry trends to support future-state architecture strategies."
We'll make - each.
Now Qualifications: from "Education & Preferred Qualifications". Let's extract:
"Degree in Computer Science, Cybersecurity, Information Technology, Engineering, or a related discipline.
8 years or more of experience leading large-scale cybersecurity architecture, engineering, security operations, or technology transformation functions in complex, global environments, with at least 8 years of cybersecurity experience preferred.
Demonstrated experience designing and implementing enterprise-scale cloud security architectures across AWS, Azure, and/or Google Cloud Platform environments.
Deep expertise in cloud security, security architecture, network security, identity and access management, data protection, encryption, and infrastructure security.
Strong understanding of cloud-native architectures, containers, Kubernetes, DevSecOps, CI/CD pipelines, and Infrastructure as Code (IaC).
Experience developing enterprise security standards, governance frameworks, architecture patterns, and secure-by-design practices.
Professional certifications such as CISSP, CCSP, AWS Security Specialty, Azure Security Engineer, Azure Solutions Architect, TOGAF, SABSA, or equivalent certifications are highly desirable.
Experience within financial services or other highly regulated industries is preferred."
We'll make
- .
Now Skills: from "What We Value". Extract:
"Strong expertise in cloud security architecture, cloud-native technologies, and modern infrastructure platforms.
Deep understanding of AWS, Microsoft Azure, and Google Cloud security services and architectures.
Strong analytical, problem-solving, and risk-based decision-making skills.
Experience working on large-scale cloud transformation initiatives within complex global organizations.
Strong communication and stakeholder management skills with the ability to influence engineering, architecture, and business teams."
Make
- .
Now Additional Requirements: from "Additional Requirements". Extract:
"Experience supporting enterprise cloud migration and modernization initiatives.
Ability to collaborate effectively with cloud engineering, infrastructure, security, risk, and business teams globally.
Limited travel may be required based on business needs."
We could treat as Requirements heading.
Now Work Requirement: from "Work Requirement". Extract:
"Hybrid: Expected to work in accordance with State Street's hybrid work model.
Shift: Standard business hours with flexibility to support global stakeholders across multiple time zones."
We'll put under Schedule heading.
Now Pay: from "Salary Range". Extract:
"Salary Range $90,000 - $157,500 Annual
The range quoted above applies to the role in the primary location specified. If the candidate would ultimately work outside of the primary location above, the applicable range could differ."
We'll put under Pay heading.
Now Benefits: from benefits paragraph. Extract:
"Employees are eligible to participate in State Street’s comprehensive benefits program, which includes: our retirement savings plan (401K) with company match; insurance coverage including basic life, medical, dental, vision, long-term disability, and other optional additional coverages; paid-time off including vacation, sick leave, short term disability, and family care responsibilities; access to our Employee Assistance Program; incentive compensation including eligibility for annual performance-based awards (excluding certain sales roles subject to sales incentive plans); and, eligibility for certain tax
for prose. Do not include boilerplate like EEO, legal, application instructions, cookie/navigation, etc. Also remove duplicated lines. Must preserve all substantive info. We need to decide which sections to include based on presence of real content. We have: - Who We Are Looking For: description of role responsibilities? Actually it's intro: "We are looking for a Cloud Security Architect. You will be responsible for defining, implementing, and governing cloud security architectures, standards, and security controls across public cloud, private cloud, and SaaS environments. You will partner with cloud engineering, application development, infrastructure, cybersecurity, and business stakeholders to deliver secure, resilient, and scalable cloud solutions that support the firm's digital transformation initiatives." That's a prose paragraph. Could be under "About the role" or "Who We Are Looking For". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to those headings. Use only those headings if they have real content. We have responsibilities: "What You Will Be Responsible For" list of duties. We have qualifications: "Education & Preferred Qualifications" includes degree, years experience, certifications. We have skills: "What We Value" list of skills/expertise. We have additional requirements: "Additional Requirements" includes experience supporting enterprise cloud migration, ability to collaborate, limited travel. We have work requirement: "Work Requirement Hybrid: Expected to work in accordance with State Street's hybrid work model. Shift: Standard business hours with flexibility to support global stakeholders across multiple time zones." We have salary range: "Salary Range $90,000 - $157,500 Annual". Also note about location. We have benefits: paragraph about benefits program. We have "About State Street" description. We need to decide which sections to include: About the role (intro), Responsibilities, Qualifications, Skills, Benefits, Pay, Schedule? Also maybe Work Requirement could be under Schedule? Actually schedule is about shift/hours. Work requirement includes hybrid and shift. Could be under Schedule heading. But we need to only include sections if posting has real specific content. We have schedule info: "Hybrid: Expected to work in accordance with State Street's hybrid work model. Shift: Standard business hours with flexibility to support global stakeholders across multiple time zones." That's specific enough. Pay: we have salary range. Benefits: we have description. About the role: we have intro paragraph. Responsibilities: we have list. Qualifications: we have Education & Preferred Qualifications. Skills: we have What We Value. We could also include Additional Requirements as part of Qualifications or maybe as separate Requirements? The instruction list includes Requirements as a possible heading. Could treat Additional Requirements as Requirements. But we must not create thin sections. Let's see if we can combine. We have: - About the role: intro paragraph. - Responsibilities: bullet list. - Qualifications: includes education, years experience, certifications, etc. - Skills: list of expertise. - Benefits: paragraph. - Pay: salary range. - Schedule: hybrid and shift. We should not include About State Street? That's company description, maybe not needed but could be considered "About the role"? Actually "About State Street" is generic company info, not specific to role. Might be considered boilerplate? It's not EEO/legal but still generic. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those, but it's still generic company description. Might be considered not substantive to the role? However it's part of posting. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep it. Where to place? Could be under a heading like "About the company" but not in allowed headings. The allowed headings list does not include About the company. But we could embed it in a
without a heading? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples, not exclusive? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should use those headings for sections. It doesn't forbid other headings, but suggests using those. Safer to stick to those.
Thus we can put About State Street content under About the role? Might be odd but we could include as a paragraph after the intro. Or we could create a separate section "About the company" but not in list; risk of being considered not following instruction. Better to incorporate into About the role as additional paragraph.
We must not repeat job title as heading. So no heading "Cloud Security Architect". Good.
We must not put Job ID/requisition numbers as headings; we can drop them.
We must not include boilerplate like EEO, legal, application instructions. So remove the Equal Opportunity Employer paragraph, the Job Application Disclosure, the CEO Statement, etc.
Also remove duplicated lines.
Now craft HTML.
Structure:
About the role
About the role
We are looking for a Cloud Security Architect. You will be responsible for defining, implementing, and governing cloud security architectures, standards, and security controls across public cloud, private cloud, and SaaS environments. You will partner with cloud engineering, application development, infrastructure, cybersecurity, and business stakeholders to deliver secure, resilient, and scalable cloud solutions that support the firm's digital transformation initiatives.
As the firm's adoption of cloud technologies continues to expand, this role is responsible for ensuring cloud environments are designed and operated securely, aligned with regulatory requirements, enterprise standards, and industry best practices. The team you will be joining is part of the Security Architecture organization, a function that is critical to protecting the firm's cloud platforms, applications, data, and technology services.
Across the globe, institutional investors rely on us to help them manage risk, respond to challenges, and drive performance and profitability. We keep our clients at the heart of everything we do, and smart, engaged employees are essential to our continued success. We are committed to fostering an environment where every employee feels valued and empowered to reach their full potential. As an essential partner in our shared success, you’ll benefit from inclusive development opportunities, flexible work-life support, paid volunteer days, and vibrant employee networks that keep you connected to what matters most.
But note we duplicated some sentences from "Why This Role Is Important To Us" and "About State Street". We need to preserve all substantive info, not invent. So we should include those paragraphs exactly as they appear (or close). Let's extract: "Why This Role Is Important To Us" paragraph: "The team you will be joining is part of the Security Architecture organization, a function that is critical to protecting the firm's cloud platforms, applications, data, and technology services. As the firm's adoption of cloud technologies continues to expand, this role is responsible for ensuring cloud environments are designed and operated securely, aligned with regulatory requirements, enterprise standards, and industry best practices." "About State Street" paragraph: "Across the globe, institutional investors rely on us to help them manage risk, respond to challenges, and drive performance and profitability. We keep our clients at the heart of everything we do, and smart, engaged employees are essential to our continued success. We are committed to fostering an environment where every employee feels valued and empowered to reach their full potential. As an essential partner in our shared success, you’ll benefit from inclusive development opportunities, flexible work-life support, paid volunteer days, and vibrant employee networks that keep you connected to what matters most." We can combine them. Now Responsibilities: list from "What You Will Be Responsible For". It's a sentence with semicolons? Actually it's a paragraph with each duty separated by periods? Let's copy: "Design and maintain cloud security architectures, standards, patterns, and reference models across multi-cloud and hybrid-cloud environments. Partner with cloud engineering, infrastructure, and application teams to integrate security controls into cloud platforms and services. Lead security architecture reviews for cloud transformation initiatives, cloud-native applications, containers, Kubernetes platforms, and SaaS solutions. Define and govern cloud security capabilities including identity and access management, network security, data protection, encryption, logging, monitoring, and security automation. Identify cloud security risks and develop mitigation strategies aligned with enterprise risk management and regulatory requirements. Drive adoption of Zero Trust, secure-by-design, and cloud-native security principles. Evaluate emerging cloud security technologies and industry trends to support future-state architecture strategies." We'll make- each.
Now Qualifications: from "Education & Preferred Qualifications". Let's extract:
"Degree in Computer Science, Cybersecurity, Information Technology, Engineering, or a related discipline.
8 years or more of experience leading large-scale cybersecurity architecture, engineering, security operations, or technology transformation functions in complex, global environments, with at least 8 years of cybersecurity experience preferred.
Demonstrated experience designing and implementing enterprise-scale cloud security architectures across AWS, Azure, and/or Google Cloud Platform environments.
Deep expertise in cloud security, security architecture, network security, identity and access management, data protection, encryption, and infrastructure security.
Strong understanding of cloud-native architectures, containers, Kubernetes, DevSecOps, CI/CD pipelines, and Infrastructure as Code (IaC).
Experience developing enterprise security standards, governance frameworks, architecture patterns, and secure-by-design practices.
Professional certifications such as CISSP, CCSP, AWS Security Specialty, Azure Security Engineer, Azure Solutions Architect, TOGAF, SABSA, or equivalent certifications are highly desirable.
Experience within financial services or other highly regulated industries is preferred."
We'll make
- .
Now Skills: from "What We Value". Extract:
"Strong expertise in cloud security architecture, cloud-native technologies, and modern infrastructure platforms.
Deep understanding of AWS, Microsoft Azure, and Google Cloud security services and architectures.
Strong analytical, problem-solving, and risk-based decision-making skills.
Experience working on large-scale cloud transformation initiatives within complex global organizations.
Strong communication and stakeholder management skills with the ability to influence engineering, architecture, and business teams."
Make
- . Now Additional Requirements: from "Additional Requirements". Extract: "Experience supporting enterprise cloud migration and modernization initiatives. Ability to collaborate effectively with cloud engineering, infrastructure, security, risk, and business teams globally. Limited travel may be required based on business needs." We could treat as Requirements heading. Now Work Requirement: from "Work Requirement". Extract: "Hybrid: Expected to work in accordance with State Street's hybrid work model. Shift: Standard business hours with flexibility to support global stakeholders across multiple time zones." We'll put under Schedule heading. Now Pay: from "Salary Range". Extract: "Salary Range $90,000 - $157,500 Annual The range quoted above applies to the role in the primary location specified. If the candidate would ultimately work outside of the primary location above, the applicable range could differ." We'll put under Pay heading. Now Benefits: from benefits paragraph. Extract: "Employees are eligible to participate in State Street’s comprehensive benefits program, which includes: our retirement savings plan (401K) with company match; insurance coverage including basic life, medical, dental, vision, long-term disability, and other optional additional coverages; paid-time off including vacation, sick leave, short term disability, and family care responsibilities; access to our Employee Assistance Program; incentive compensation including eligibility for annual performance-based awards (excluding certain sales roles subject to sales incentive plans); and, eligibility for certain tax
- .
Now Skills: from "What We Value". Extract:
"Strong expertise in cloud security architecture, cloud-native technologies, and modern infrastructure platforms.
Deep understanding of AWS, Microsoft Azure, and Google Cloud security services and architectures.
Strong analytical, problem-solving, and risk-based decision-making skills.
Experience working on large-scale cloud transformation initiatives within complex global organizations.
Strong communication and stakeholder management skills with the ability to influence engineering, architecture, and business teams."
Make