Senior Manager, Azure Architect
for headings. Use - for lists. Use
for prose.
We need to not repeat job title as heading.
We need to not include Job ID etc.
We need to include sections: About the role (maybe from Job Overview). Responsibilities. Qualifications (maybe includes Required Skills). Could also have Skills separate but we can combine.
We need to ensure we don't create empty sections.
Let's extract content:
Job Overview paragraph: "Deloitte Cloud Services, reporting to the Office of the Global CTO, is responsible for delivering cloud solutions that accelerate the development of both client-facing and internal applications. The team enables software development through cloud engineering best practices and fully automated release management processes. As the Senior Manager, Azure Cloud Architect, you will lead the design and delivery of enterprise-scale cloud solutions, providing deep expertise across Azure infrastructure, architecture, and engineering practices. You will drive cloud adoption, modernization, and automation initiatives while partnering with business and technology teams to deliver secure, scalable, and innovative solutions. This role requires strong technical leadership, strategic thinking, and the ability to solve complex business and technology challenges in a global cloud environment."
That's prose.
Responsibilities list: bullet points:
- Define cloud architecture standards and solutions across hybrid and cloud-native environments.
- Serve as the subject matter expert for Azure cloud architecture, leveraging deep knowledge of IaaS and PaaS services to design scalable, secure, and resilient solutions.
- Ensure cloud solutions adhere to security, compliance, governance, and operational standards.
- Lead the design and evolution of automated DevOps and release management pipelines supporting application development and production operations.
- Promote and champion Continuous Integration and Continuous Delivery (CI/CD) practices across development teams.
- En (looks truncated? maybe "En" is incomplete; but we keep as is? It might be a mistake; but we must preserve all substantive information; we cannot invent. The "En" appears incomplete; maybe it's "Enable"? But we should keep as given? The text: "En The team Deloitte Technology works at the forefront..." Actually after "Promote and champion Continuous Integration and Continuous Delivery (CI/CD) practices across development teams." there is "En The team Deloitte Technology works at the forefront..." So "En" is start of next sentence but cut off. We'll keep as is? Probably it's a formatting error; but we must preserve content exactly as given. We'll include the line "En" as a bullet? Actually it's not a bullet; it's part of paragraph. The original:
"Promote and champion Continuous Integration and Continuous Delivery (CI/CD) practices across development teams. En The team Deloitte Technology works at the forefront of technology development and processes to support and protect Deloitte around the world. In this truly global environment, we operate not in "what is" but rather "what can be" to help Deloitte deliver and connect with its clients, its communities, and one another in ways not previously conceived."
Thus after responsibilities, there is a paragraph about the team. That could be part of About the role or separate section? Might be "About the team". But we only have headings list; we could treat as About the role (or About the team). Since we have no specific heading for team, we could incorporate into About the role prose.
Thus after responsibilities, we have a paragraph: "The team Deloitte Technology works at the forefront of technology development and processes to support and protect Deloitte around the world. In this truly global environment, we operate not in "what is" but rather "what can be" to help Deloitte deliver and connect with its clients, its communities, and one another in ways not previously conceived."
We'll include that as prose after responsibilities maybe as part of About the role or separate section "About the team". But we only allowed headings list; we could add a heading "About the team" but not in list. The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive. So we could add other headings if appropriate. But better to stick to given list. We could treat that paragraph as part of About the role.
Now Qualifications/Required Skills list: bullet points:
- Bachelor's degree in Computer Science, Business Information Systems, or equivalent experience.
- 8+ years of progressive IT experience, including senior-level architecture and technical leadership roles.
- 5+ years of experience architecting and delivering enterprise Azure cloud solutions across governance, security, networking, identity, compute, storage, monitoring, container platforms, and Infrastructure as Code (Management Groups, Azure Policy, Defender for Cloud, Entra ID, AKS, Azure Monitor, Bicep/ARM).
- Experience managing large, complex Azure environments across multiple global regions.
- Strong understanding of Azure Enterprise Agreement billing, including billing analysis and reporting.
- Knowledge of SQL and NoSQL database technologies.
- Experience implementing CI/CD practices and working with DevOps and release management tools.
- Experience working in Agile Scrum environments.
- Strong understanding of networking concepts, including firewalls, load balancing, and network security.
- Knowledge of operational best practices for highly available, enterprise-scale cloud environments.
- Exceptional communication and stakeholder management skills, with the ability to engage effectively with executive and technical audiences.
- Strong analytical, problem-solving, influencing, conflict resolution, and consensus-building skills.
- Ability to travel approximately 10%.
- Limited immigration sponsorship may be available.
We could split into Requirements and Qualifications and Skills. But we have only one list; we could put under Qualifications. Or we could separate: Requirements (education, years experience) and Skills (technical). But to keep simple, we can have one section Qualifications containing all.
We must not include Pay/Benefits/Schedule.
Thus final HTML:
About the role
Deloitte Cloud Services, reporting to the Office of the Global CTO, is responsible for delivering cloud solutions that accelerate the development of both client-facing and internal applications. The team enables software development through cloud engineering best practices and fully automated release management processes. As the Senior Manager, Azure Cloud Architect, you will lead the design and delivery of enterprise-scale cloud solutions, providing deep expertise across Azure infrastructure, architecture, and engineering practices. You will drive cloud adoption, modernization, and automation initiatives while partnering with business and technology teams to deliver secure, scalable, and innovative solutions. This role requires strong technical leadership, strategic thinking, and the ability to solve complex business and technology challenges in a global cloud environment.
The team Deloitte Technology works at the forefront of technology development and processes to support and protect Deloitte around the world. In this truly global environment, we operate not in "what is" but rather "what can be" to help Deloitte deliver and connect with its clients, its communities, and one another in ways not previously conceived.
Responsibilities
- Define cloud architecture standards and solutions across hybrid and cloud-native environments.
- Serve as the subject matter expert for Azure cloud architecture, leveraging deep knowledge of IaaS and PaaS services to design scalable, secure, and resilient solutions.
- Ensure cloud solutions adhere to security, compliance, governance, and operational standards.
- Lead the design and evolution of automated DevOps and release management pipelines supporting application development and production operations.
- Promote and champion Continuous Integration and Continuous Delivery (CI/CD) practices across development teams.
- En
But the "En" bullet seems odd; maybe it's part of next sentence; but we must preserve. However it's not a proper bullet; maybe it's a stray. Could we treat it as part of paragraph? The original had "En The team..." So "En" is start of "Enable"? Actually maybe the original text was "Enable the team..." but got cut. We'll keep as is.
But maybe better to not create a bullet for "En". Instead we could treat the responsibilities list ending before "En". Then after the list we could have a paragraph starting with "En The team...". However that would split the sentence. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep the exact text. If we split, we change meaning? The original had "Promote and champion Continuous Integration and Continuous Delivery (CI/CD) practices across development teams. En The team Deloitte Technology works at the forefront..." So "En" is likely a typo for "The". But we must keep as given. So we could keep "En" as a separate sentence? It's weird but we must keep.
Thus we could add a after responsibilities:
En The team Deloitte Technology works at the forefront of technology development and processes to support and protect Deloitte around the world. In this truly global environment, we operate not in "what is" but rather "what can be" to help Deloitte deliver and connect with its clients, its communities, and one another in ways not previously conceived.
But then we duplicate team paragraph. Actually we already have team paragraph earlier. Might be duplication. Let's examine original text after responsibilities:
"Promote and champion Continuous Integration and Continuous Delivery (CI/CD) practices across development teams. En The team Deloitte Technology works at the forefront of technology development and processes to support and protect Deloitte around the world. In this truly global environment, we operate not in "what is" but rather "what can be" to help Deloitte deliver and connect with its clients, its communities, and one another in ways not previously conceived."
Thus the sentence "En The team..." is actually the start of a paragraph about the team. So we should not have duplicated team paragraph earlier. The earlier "About the role" paragraph ended before responsibilities. So we should not include the team paragraph in About the role; we should include it after responsibilities as part of the description. So we need to adjust.
Thus About the role paragraph ends at "This role requires strong technical leadership, strategic thinking, and the ability to solve complex business and technology challenges in a global cloud environment."
Then Responsibilities list.
Then after responsibilities, we have a paragraph: "En The team Deloitte Technology works at the forefront of technology development and processes to support and protect Deloitte around the world. In this truly global environment, we operate not in "what is" but rather "what can be" to help Deloitte deliver and connect with its clients, its communities, and one another in ways not previously conceived."
We'll keep that as a paragraph.
Then Qualifications list.
Thus final HTML:
About the role
Deloitte Cloud Services, reporting to the Office of the Global CTO, is responsible for delivering cloud solutions that accelerate the development of both client-facing and internal applications. The team enables software development through cloud engineering best practices and fully automated release management processes. As the Senior Manager, Azure Cloud Architect, you will lead the design and delivery of enterprise-scale cloud solutions, providing deep expertise across Azure infrastructure, architecture, and engineering practices. You will drive cloud adoption, modernization, and automation initiatives while partnering with business and technology teams to deliver secure, scalable, and innovative solutions. This role requires strong technical leadership, strategic thinking, and the ability to solve complex business and technology challenges in a global cloud environment.
Responsibilities
- Define cloud architecture standards and solutions across hybrid and cloud-native environments.
- Serve as the subject matter expert for Azure cloud architecture, leveraging
for prose. We need to not repeat job title as heading. We need to not include Job ID etc. We need to include sections: About the role (maybe from Job Overview). Responsibilities. Qualifications (maybe includes Required Skills). Could also have Skills separate but we can combine. We need to ensure we don't create empty sections. Let's extract content: Job Overview paragraph: "Deloitte Cloud Services, reporting to the Office of the Global CTO, is responsible for delivering cloud solutions that accelerate the development of both client-facing and internal applications. The team enables software development through cloud engineering best practices and fully automated release management processes. As the Senior Manager, Azure Cloud Architect, you will lead the design and delivery of enterprise-scale cloud solutions, providing deep expertise across Azure infrastructure, architecture, and engineering practices. You will drive cloud adoption, modernization, and automation initiatives while partnering with business and technology teams to deliver secure, scalable, and innovative solutions. This role requires strong technical leadership, strategic thinking, and the ability to solve complex business and technology challenges in a global cloud environment." That's prose. Responsibilities list: bullet points: - Define cloud architecture standards and solutions across hybrid and cloud-native environments. - Serve as the subject matter expert for Azure cloud architecture, leveraging deep knowledge of IaaS and PaaS services to design scalable, secure, and resilient solutions. - Ensure cloud solutions adhere to security, compliance, governance, and operational standards. - Lead the design and evolution of automated DevOps and release management pipelines supporting application development and production operations. - Promote and champion Continuous Integration and Continuous Delivery (CI/CD) practices across development teams. - En (looks truncated? maybe "En" is incomplete; but we keep as is? It might be a mistake; but we must preserve all substantive information; we cannot invent. The "En" appears incomplete; maybe it's "Enable"? But we should keep as given? The text: "En The team Deloitte Technology works at the forefront..." Actually after "Promote and champion Continuous Integration and Continuous Delivery (CI/CD) practices across development teams." there is "En The team Deloitte Technology works at the forefront..." So "En" is start of next sentence but cut off. We'll keep as is? Probably it's a formatting error; but we must preserve content exactly as given. We'll include the line "En" as a bullet? Actually it's not a bullet; it's part of paragraph. The original: "Promote and champion Continuous Integration and Continuous Delivery (CI/CD) practices across development teams. En The team Deloitte Technology works at the forefront of technology development and processes to support and protect Deloitte around the world. In this truly global environment, we operate not in "what is" but rather "what can be" to help Deloitte deliver and connect with its clients, its communities, and one another in ways not previously conceived." Thus after responsibilities, there is a paragraph about the team. That could be part of About the role or separate section? Might be "About the team". But we only have headings list; we could treat as About the role (or About the team). Since we have no specific heading for team, we could incorporate into About the role prose. Thus after responsibilities, we have a paragraph: "The team Deloitte Technology works at the forefront of technology development and processes to support and protect Deloitte around the world. In this truly global environment, we operate not in "what is" but rather "what can be" to help Deloitte deliver and connect with its clients, its communities, and one another in ways not previously conceived." We'll include that as prose after responsibilities maybe as part of About the role or separate section "About the team". But we only allowed headings list; we could add a heading "About the team" but not in list. The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not exclusive. So we could add other headings if appropriate. But better to stick to given list. We could treat that paragraph as part of About the role.
Now Qualifications/Required Skills list: bullet points:
- Bachelor's degree in Computer Science, Business Information Systems, or equivalent experience.
- 8+ years of progressive IT experience, including senior-level architecture and technical leadership roles.
- 5+ years of experience architecting and delivering enterprise Azure cloud solutions across governance, security, networking, identity, compute, storage, monitoring, container platforms, and Infrastructure as Code (Management Groups, Azure Policy, Defender for Cloud, Entra ID, AKS, Azure Monitor, Bicep/ARM).
- Experience managing large, complex Azure environments across multiple global regions.
- Strong understanding of Azure Enterprise Agreement billing, including billing analysis and reporting.
- Knowledge of SQL and NoSQL database technologies.
- Experience implementing CI/CD practices and working with DevOps and release management tools.
- Experience working in Agile Scrum environments.
- Strong understanding of networking concepts, including firewalls, load balancing, and network security.
- Knowledge of operational best practices for highly available, enterprise-scale cloud environments.
- Exceptional communication and stakeholder management skills, with the ability to engage effectively with executive and technical audiences.
- Strong analytical, problem-solving, influencing, conflict resolution, and consensus-building skills.
- Ability to travel approximately 10%.
- Limited immigration sponsorship may be available.
We could split into Requirements and Qualifications and Skills. But we have only one list; we could put under Qualifications. Or we could separate: Requirements (education, years experience) and Skills (technical). But to keep simple, we can have one section Qualifications containing all.
We must not include Pay/Benefits/Schedule.
Thus final HTML:
About the role
Deloitte Cloud Services, reporting to the Office of the Global CTO, is responsible for delivering cloud solutions that accelerate the development of both client-facing and internal applications. The team enables software development through cloud engineering best practices and fully automated release management processes. As the Senior Manager, Azure Cloud Architect, you will lead the design and delivery of enterprise-scale cloud solutions, providing deep expertise across Azure infrastructure, architecture, and engineering practices. You will drive cloud adoption, modernization, and automation initiatives while partnering with business and technology teams to deliver secure, scalable, and innovative solutions. This role requires strong technical leadership, strategic thinking, and the ability to solve complex business and technology challenges in a global cloud environment.
The team Deloitte Technology works at the forefront of technology development and processes to support and protect Deloitte around the world. In this truly global environment, we operate not in "what is" but rather "what can be" to help Deloitte deliver and connect with its clients, its communities, and one another in ways not previously conceived.
Responsibilities
- Define cloud architecture standards and solutions across hybrid and cloud-native environments.
- Serve as the subject matter expert for Azure cloud architecture, leveraging deep knowledge of IaaS and PaaS services to design scalable, secure, and resilient solutions.
- Ensure cloud solutions adhere to security, compliance, governance, and operational standards.
- Lead the design and evolution of automated DevOps and release management pipelines supporting application development and production operations.
- Promote and champion Continuous Integration and Continuous Delivery (CI/CD) practices across development teams.
- En
after responsibilities:
En The team Deloitte Technology works at the forefront of technology development and processes to support and protect Deloitte around the world. In this truly global environment, we operate not in "what is" but rather "what can be" to help Deloitte deliver and connect with its clients, its communities, and one another in ways not previously conceived.
But then we duplicate team paragraph. Actually we already have team paragraph earlier. Might be duplication. Let's examine original text after responsibilities: "Promote and champion Continuous Integration and Continuous Delivery (CI/CD) practices across development teams. En The team Deloitte Technology works at the forefront of technology development and processes to support and protect Deloitte around the world. In this truly global environment, we operate not in "what is" but rather "what can be" to help Deloitte deliver and connect with its clients, its communities, and one another in ways not previously conceived." Thus the sentence "En The team..." is actually the start of a paragraph about the team. So we should not have duplicated team paragraph earlier. The earlier "About the role" paragraph ended before responsibilities. So we should not include the team paragraph in About the role; we should include it after responsibilities as part of the description. So we need to adjust. Thus About the role paragraph ends at "This role requires strong technical leadership, strategic thinking, and the ability to solve complex business and technology challenges in a global cloud environment." Then Responsibilities list. Then after responsibilities, we have a paragraph: "En The team Deloitte Technology works at the forefront of technology development and processes to support and protect Deloitte around the world. In this truly global environment, we operate not in "what is" but rather "what can be" to help Deloitte deliver and connect with its clients, its communities, and one another in ways not previously conceived." We'll keep that as a paragraph. Then Qualifications list. Thus final HTML:About the role
Deloitte Cloud Services, reporting to the Office of the Global CTO, is responsible for delivering cloud solutions that accelerate the development of both client-facing and internal applications. The team enables software development through cloud engineering best practices and fully automated release management processes. As the Senior Manager, Azure Cloud Architect, you will lead the design and delivery of enterprise-scale cloud solutions, providing deep expertise across Azure infrastructure, architecture, and engineering practices. You will drive cloud adoption, modernization, and automation initiatives while partnering with business and technology teams to deliver secure, scalable, and innovative solutions. This role requires strong technical leadership, strategic thinking, and the ability to solve complex business and technology challenges in a global cloud environment.
Responsibilities
- Define cloud architecture standards and solutions across hybrid and cloud-native environments.
- Serve as the subject matter expert for Azure cloud architecture, leveraging