Sr. Azure Cloud Architect III (6796)
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. Must include only sections with real content. Must not include boilerplate like EEO, legal, etc. Must preserve all substantive info.
We need to parse the posting.
Content:
- Intro: "As Sr. Azure Cloud Architect III, you’ll design secure, scalable, and resilient cloud solutions for complex enterprise environments. You will lead Azure architecture decisions, automate infrastructure, strengthen cloud governance, and collaborate with engineering and security teams to modernize critical technology platforms."
- Then paragraph about MetroStar people.
- Then "What you’ll do:" then list of duties.
- Then "What you’ll need to succeed:" then list of requirements.
- Then "SALARY RANGE: $150,000.00 - $200,000.00" plus explanation.
- Then "Additional Compensation: ..."
- Then "Benefits: All full-time employees are eligible to participate in our benefits programs:" then list.
- Then other paragraphs about culture etc (maybe not needed). Also "Commitment to Non-Discrimination" etc is boilerplate to remove.
- Also "What we want you to know: In compliance with federal law..." is boilerplate to remove.
- Also "Not ready to apply now? Sign up to join our newsletter here." remove.
We need sections: About the role (intro paragraph), Responsibilities (the "What you’ll do:" list), Requirements (the "What you’ll need to succeed:" list), Qualifications (maybe combine with Requirements? but we can have Qualifications separate if content). Skills (maybe list of specific technical skills). Benefits (list). Pay (salary range). Schedule? Not present, so omit.
We must not create sections with filler. So we include only those with content.
We need to use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive info; do not invent or summarize away detail. So we need to include all bullet points from duties and requirements and benefits.
We need to ensure we don't repeat the job title as heading. So we don't put "Sr. Azure Cloud Architect III" as heading.
We need to include meta like Job ID? Not present.
We need to drop duplicated lines.
Let's extract duties list:
From "What you’ll do:" then bullet points (though not bullet formatted but sentences separated by periods). We need to convert each duty into list items.
List:
- Cloud Infrastructure Management: Design, implement, and maintain Azure cloud infrastructure using Azure Virtual Machines (VMs), Virtual Networks (VNets), Azure SQL Database, Blob Storage, Managed Disks, and Azure Active Directory (AAD).
- Infrastructure as Code (IaC): Automate Azure resource provisioning and configuration using Terraform, Azure Resource Manager (ARM) templates, and Ansible.
- Security & Compliance: Implement Azure cloud security best practices, including role-based access control (RBAC), Azure DDoS Protection, Microsoft Defender for Cloud, encryption at rest/in transit, and alignment with FedRAMP, NIST, and DoD compliance standards.
- CI/CD Pipeline Management: Develop and manage CI/CD pipelines using GitLab, Jenkins, and Azure DevOps Pipelines to streamline deployments and improve delivery velocity.
- Monitoring & Optimization: Utilize Azure Monitor, Azure Log Analytics, Azure Application Insights, and Azure Activity Logs to track system health, troubleshoot issues, and enhance performance.
- Networking & Load Balancing: Configure and optimize Azure Virtual Networks (VNets), Azure DNS, Azure Load Balancer, Application Gateway, and ExpressRoute for secure and scalable connectivity.
- Hybrid Cloud & Migration: Support Azure cloud migrations and hybrid environments, integrating with on-premises infrastructure using Azure Arc, Azure Migrate, and Azure Site Recovery.
- Automation & Scripting: Develop automation scripts using Python, PowerShell, and Bash to improve operational efficiency and reduce manual workloads.
- Disaster Recovery & Backup Solutions: Implement Azure backup strategies, including Azure Backup, blob lifecycle management, and snapshot automation.
- Stakeholder Collaboration: Work closely with client organizations, DevOps teams, and security engineers to align Azure-based solutions with organizational objectives and compliance requirements.
Now requirements list from "What you’ll need to succeed:":
- Active Secret security clearance.
- Azure Solutions Architect certification (preferred) or equivalent Azure certification.
- 10+ years of experience in cloud engineering, DevOps, or systems administration, with a strong focus on Microsoft Azure environments.
- 5+ years of experience with Azure Cloud Engineering, IaC (Terraform), GiLab, and CI/CD pipelines. (Note: GiLab likely typo for GitLab)
- 4+ years of experience with PowerShell scripting.
- Hands-on experience with Ansible, Jenkins, GitHub, and Azure DevOps services.
- Experience working in multi-cloud and hybrid environments integrating Azure and on-premise infrastructure.
- Strong proficiency in Azure networking services (e.g., Virtual Networks, Azure DNS, VPN Gateway, ExpressRoute, or Azure Load Balancer/Application Gateway).
- Strong knowledge of Azure Active Directory (AAD), encryption, security monitoring, and compliance frameworks (e.g., FedRAMP, NIST, and applicable security standards).
- Proficiency in Python, PowerShell, Bash, and YAML/JSON for cloud automation and system management.
Now Benefits list:
- Health, dental, and vision insurance
- 401(k) retirement plan with company match
- Paid time off (PTO) and holidays
- Parental Leave and dependent care
- Flexible work arrangements
- Professional development opportunities
- Employee assistance and wellness programs
Now Pay: Salary range $150,000.00 - $200,000.00 plus explanation about determination. We need to preserve all substantive info; we can include the explanation as prose.
We also have "Additional Compensation: This role may also be eligible for bonuses and/or additional incentives based on individual and company performance." plus earlier mention of performance-based bonuses, company-paid training, referral bonuses. We could incorporate into Pay section or maybe a separate "Compensation" but we only have Pay heading allowed. We can include all compensation details under Pay section.
We also have intro paragraph about role and MetroStar people. That could be "About the role" section.
We also have paragraph about MetroStar people: "We know that you can’t have great technology services without amazing people. At MetroStar, we are obsessed with our people and have led a two-decade legacy of building the best and brightest teams. Because we know our future relies on our deep understanding and relentless focus on our people, we live by our mission: A passion for our people. Value for our customers." plus "If you think you can see yourself delivering our mission and pursuing our goals with us, then check out the job description below!" That's fluff but substantive? It's about company mission. Could be part of About the role.
We should not include boilerplate like EEO, legal, etc.
Now we need to output HTML fragment only.
Structure:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Skills
maybe we can list specific technical skills extracted from requirements? But we already have Requirements covering experience and certifications. Skills could be separate list of technical proficiencies: Python, PowerShell, Bash, YAML/JSON, Terraform, ARM, Ansible, Jenkins, GitLab, GitHub, Azure DevOps, Azure services, etc. However we risk duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Skills into one section? But we have headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could use Requirements for experience and certifications, Skills for technical proficiencies. That seems reasonable.
Let's extract technical skills from requirements:
- Azure Solutions Architect certification (preferred) or equivalent Azure certification.
- Experience with Azure Cloud Engineering, IaC (Terraform), GitLab, CI/CD pipelines.
- PowerShell scripting.
- Experience with Ansible, Jenkins, GitHub, Azure DevOps services.
- Multi-cloud and hybrid environments integrating Azure and on-premise infrastructure.
- Azure networking services (Virtual Networks, Azure DNS, VPN Gateway, ExpressRoute, Azure Load Balancer/Application Gateway).
- Azure Active Directory (AAD), encryption, security monitoring, compliance frameworks (FedRAMP, NIST, applicable security standards).
- Proficiency in Python, PowerShell, Bash, YAML/JSON for cloud automation and system management.
We could list these as bullet items under Skills.
Now Requirements could focus on years of experience, clearance, certification preference.
Let's define:
Requirements:
- Active Secret security clearance.
- 10+ years of experience in cloud engineering, DevOps, or systems administration, with a strong focus on Microsoft Azure environments.
- 5+ years of experience with Azure Cloud Engineering, IaC (Terraform), GitLab, and CI/CD pipelines.
- 4+ years of experience with PowerShell scripting.
Skills:
- Azure Solutions Architect certification (preferred) or equivalent Azure certification.
- Hands-on experience with Ansible, Jenkins, GitHub, and Azure DevOps services.
- Experience working in multi-cloud and hybrid environments integrating Azure and on-premise infrastructure.
- Strong proficiency in Azure networking services (e.g., Virtual Networks, Azure DNS, VPN Gateway, ExpressRoute, or Azure Load Balancer/Application Gateway).
- Strong knowledge of Azure Active Directory (AAD), encryption, security monitoring, and compliance frameworks (e.g., FedRAMP, NIST, and applicable security standards).
- Proficiency in Python, PowerShell, Bash, and YAML/JSON for cloud automation and system management.
That seems non-duplicative.
Now Benefits as list.
Pay: include salary range and explanation about determination plus additional compensation details.
We need to avoid filler like "commensurate with experience". The explanation includes factors; we keep it.
Now we need to ensure we don't include any boilerplate like "Like we said, we are big fans of our people..." That's maybe okay as part of About the role but it's somewhat fluff but still substantive? It's about benefits and culture. Could be included but we might keep it brief. However we must preserve ALL substantive information; we cannot omit details that are substantive. The paragraph about benefits and culture is somewhat generic but still part of posting. It's not boilerplate like EEO. It's about benefits package, professional growth, time to recharge. That's substantive. We could include it in About the role or maybe a separate section like "About MetroStar". But we only have allowed headings; we could put it under About the role as additional paragraph.
We also have "Learn more about our company culture code and benefits. Plus, check out our accolades." That's maybe fluff but still part of posting. Might be considered boilerplate? It's a call to action but not application instruction. Might be okay to keep.
But we need to remove duplicated lines. There's no duplication.
Now we need to output only HTML fragment.
Let's craft.
First, About the role paragraph(s):
We can combine the intro and MetroStar people paragraph and the "If you think you can see yourself..." sentence.
Paragraph: "As Sr. Azure Cloud Architect III, you’ll design secure, scalable, and resilient cloud solutions for complex enterprise environments. You will lead Azure architecture decisions, automate infrastructure, strengthen cloud governance, and collaborate with engineering and security teams to modernize critical technology platforms. We know that you can’t have great technology services without amazing people. At MetroStar, we are obsessed with our people and have led a two-decade legacy of building the best and brightest teams. Because we know our future relies on our deep understanding and relentless focus on our people, we live by our mission: A passion for our people. Value for our customers.
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive info; do not invent or summarize away detail. So we need to include all bullet points from duties and requirements and benefits. We need to ensure we don't repeat the job title as heading. So we don't put "Sr. Azure Cloud Architect III" as heading. We need to include meta like Job ID? Not present. We need to drop duplicated lines. Let's extract duties list: From "What you’ll do:" then bullet points (though not bullet formatted but sentences separated by periods). We need to convert each duty into list items. List: - Cloud Infrastructure Management: Design, implement, and maintain Azure cloud infrastructure using Azure Virtual Machines (VMs), Virtual Networks (VNets), Azure SQL Database, Blob Storage, Managed Disks, and Azure Active Directory (AAD). - Infrastructure as Code (IaC): Automate Azure resource provisioning and configuration using Terraform, Azure Resource Manager (ARM) templates, and Ansible. - Security & Compliance: Implement Azure cloud security best practices, including role-based access control (RBAC), Azure DDoS Protection, Microsoft Defender for Cloud, encryption at rest/in transit, and alignment with FedRAMP, NIST, and DoD compliance standards. - CI/CD Pipeline Management: Develop and manage CI/CD pipelines using GitLab, Jenkins, and Azure DevOps Pipelines to streamline deployments and improve delivery velocity. - Monitoring & Optimization: Utilize Azure Monitor, Azure Log Analytics, Azure Application Insights, and Azure Activity Logs to track system health, troubleshoot issues, and enhance performance. - Networking & Load Balancing: Configure and optimize Azure Virtual Networks (VNets), Azure DNS, Azure Load Balancer, Application Gateway, and ExpressRoute for secure and scalable connectivity. - Hybrid Cloud & Migration: Support Azure cloud migrations and hybrid environments, integrating with on-premises infrastructure using Azure Arc, Azure Migrate, and Azure Site Recovery. - Automation & Scripting: Develop automation scripts using Python, PowerShell, and Bash to improve operational efficiency and reduce manual workloads. - Disaster Recovery & Backup Solutions: Implement Azure backup strategies, including Azure Backup, blob lifecycle management, and snapshot automation. - Stakeholder Collaboration: Work closely with client organizations, DevOps teams, and security engineers to align Azure-based solutions with organizational objectives and compliance requirements. Now requirements list from "What you’ll need to succeed:": - Active Secret security clearance. - Azure Solutions Architect certification (preferred) or equivalent Azure certification. - 10+ years of experience in cloud engineering, DevOps, or systems administration, with a strong focus on Microsoft Azure environments. - 5+ years of experience with Azure Cloud Engineering, IaC (Terraform), GiLab, and CI/CD pipelines. (Note: GiLab likely typo for GitLab) - 4+ years of experience with PowerShell scripting. - Hands-on experience with Ansible, Jenkins, GitHub, and Azure DevOps services. - Experience working in multi-cloud and hybrid environments integrating Azure and on-premise infrastructure. - Strong proficiency in Azure networking services (e.g., Virtual Networks, Azure DNS, VPN Gateway, ExpressRoute, or Azure Load Balancer/Application Gateway). - Strong knowledge of Azure Active Directory (AAD), encryption, security monitoring, and compliance frameworks (e.g., FedRAMP, NIST, and applicable security standards). - Proficiency in Python, PowerShell, Bash, and YAML/JSON for cloud automation and system management. Now Benefits list: - Health, dental, and vision insurance - 401(k) retirement plan with company match - Paid time off (PTO) and holidays - Parental Leave and dependent care - Flexible work arrangements - Professional development opportunities - Employee assistance and wellness programs Now Pay: Salary range $150,000.00 - $200,000.00 plus explanation about determination. We need to preserve all substantive info; we can include the explanation as prose. We also have "Additional Compensation: This role may also be eligible for bonuses and/or additional incentives based on individual and company performance." plus earlier mention of performance-based bonuses, company-paid training, referral bonuses. We could incorporate into Pay section or maybe a separate "Compensation" but we only have Pay heading allowed. We can include all compensation details under Pay section. We also have intro paragraph about role and MetroStar people. That could be "About the role" section. We also have paragraph about MetroStar people: "We know that you can’t have great technology services without amazing people. At MetroStar, we are obsessed with our people and have led a two-decade legacy of building the best and brightest teams. Because we know our future relies on our deep understanding and relentless focus on our people, we live by our mission: A passion for our people. Value for our customers." plus "If you think you can see yourself delivering our mission and pursuing our goals with us, then check out the job description below!" That's fluff but substantive? It's about company mission. Could be part of About the role. We should not include boilerplate like EEO, legal, etc. Now we need to output HTML fragment only. Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
maybe we can list specific technical skills extracted from requirements? But we already have Requirements covering experience and certifications. Skills could be separate list of technical proficiencies: Python, PowerShell, Bash, YAML/JSON, Terraform, ARM, Ansible, Jenkins, GitLab, GitHub, Azure DevOps, Azure services, etc. However we risk duplication. The instruction: Prefer a few substantive sections over many thin ones. So maybe we combine Requirements and Skills into one section? But we have headings allowed: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could use Requirements for experience and certifications, Skills for technical proficiencies. That seems reasonable. Let's extract technical skills from requirements: - Azure Solutions Architect certification (preferred) or equivalent Azure certification. - Experience with Azure Cloud Engineering, IaC (Terraform), GitLab, CI/CD pipelines. - PowerShell scripting. - Experience with Ansible, Jenkins, GitHub, Azure DevOps services. - Multi-cloud and hybrid environments integrating Azure and on-premise infrastructure. - Azure networking services (Virtual Networks, Azure DNS, VPN Gateway, ExpressRoute, Azure Load Balancer/Application Gateway). - Azure Active Directory (AAD), encryption, security monitoring, compliance frameworks (FedRAMP, NIST, applicable security standards). - Proficiency in Python, PowerShell, Bash, YAML/JSON for cloud automation and system management. We could list these as bullet items under Skills. Now Requirements could focus on years of experience, clearance, certification preference. Let's define: Requirements: - Active Secret security clearance. - 10+ years of experience in cloud engineering, DevOps, or systems administration, with a strong focus on Microsoft Azure environments. - 5+ years of experience with Azure Cloud Engineering, IaC (Terraform), GitLab, and CI/CD pipelines. - 4+ years of experience with PowerShell scripting. Skills: - Azure Solutions Architect certification (preferred) or equivalent Azure certification. - Hands-on experience with Ansible, Jenkins, GitHub, and Azure DevOps services. - Experience working in multi-cloud and hybrid environments integrating Azure and on-premise infrastructure. - Strong proficiency in Azure networking services (e.g., Virtual Networks, Azure DNS, VPN Gateway, ExpressRoute, or Azure Load Balancer/Application Gateway). - Strong knowledge of Azure Active Directory (AAD), encryption, security monitoring, and compliance frameworks (e.g., FedRAMP, NIST, and applicable security standards). - Proficiency in Python, PowerShell, Bash, and YAML/JSON for cloud automation and system management. That seems non-duplicative. Now Benefits as list. Pay: include salary range and explanation about determination plus additional compensation details. We need to avoid filler like "commensurate with experience". The explanation includes factors; we keep it. Now we need to ensure we don't include any boilerplate like "Like we said, we are big fans of our people..." That's maybe okay as part of About the role but it's somewhat fluff but still substantive? It's about benefits and culture. Could be included but we might keep it brief. However we must preserve ALL substantive information; we cannot omit details that are substantive. The paragraph about benefits and culture is somewhat generic but still part of posting. It's not boilerplate like EEO. It's about benefits package, professional growth, time to recharge. That's substantive. We could include it in About the role or maybe a separate section like "About MetroStar". But we only have allowed headings; we could put it under About the role as additional paragraph. We also have "Learn more about our company culture code and benefits. Plus, check out our accolades." That's maybe fluff but still part of posting. Might be considered boilerplate? It's a call to action but not application instruction. Might be okay to keep. But we need to remove duplicated lines. There's no duplication. Now we need to output only HTML fragment. Let's craft. First, About the role paragraph(s): We can combine the intro and MetroStar people paragraph and the "If you think you can see yourself..." sentence. Paragraph: "As Sr. Azure Cloud Architect III, you’ll design secure, scalable, and resilient cloud solutions for complex enterprise environments. You will lead Azure architecture decisions, automate infrastructure, strengthen cloud governance, and collaborate with engineering and security teams to modernize critical technology platforms. We know that you can’t have great technology services without amazing people. At MetroStar, we are obsessed with our people and have led a two-decade legacy of building the best and brightest teams. Because we know our future relies on our deep understanding and relentless focus on our people, we live by our mission: A passion for our people. Value for our customers.