Cloud Solutions Engineer – Azure
Bright Vision Technologies · Eden Prairie, MN · 3 wk ago
On-siteEngineering$100k–$150k/yrFull-time
We need to output only HTML fragment, no html/body tags. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include sections only if posting has real specific content. We have:
- About the role: there is a paragraph "We are seeking a skilled Azure Cloud Engineer..." That's a summary. Could be "About the role". We'll include.
- Responsibilities: list of key responsibilities bullet points. We'll put under
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include sections only if posting has real specific content. We have:
- About the role: there is a paragraph "We are seeking a skilled Azure Cloud Engineer..." That's a summary. Could be "About the role". We'll include.
- Responsibilities: list of key responsibilities bullet points. We'll put under Responsibilities
with - each.
- Requirements: The posting has "Required Qualifications" and also "Experience Required: 6+ years". Also "Sponsorship: ...". We'll combine into Requirements section? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications sections. We need to decide what goes where. Typically Requirements could be experience, sponsorship, location, etc. Qualifications could be education, certifications, etc. We'll split.
- Qualifications: "Required Qualifications" list bullet points. Also "Preferred Qualifications". We'll include both under Qualifications? Could separate but we have only one Qualifications heading allowed. We'll include both required and preferred under Qualifications, maybe separate subheadings? But we cannot add extra headings beyond those listed? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. We'll stick to those.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills?, Benefits?, Pay?, Schedule?.
We have Pay: Salary Range: $100,000–$150,000 Annually. So we can include Pay section.
Schedule: Not mentioned besides Full-time. Could infer schedule but not explicit. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Schedule not explicitly stated beyond Full-time (which is a type). Might be considered schedule? Probably not enough detail. We'll omit Schedule.
Benefits: Not mentioned. No benefits listed. So omit Benefits.
Skills: Could be derived from responsibilities but not explicit list. Might be better to omit Skills unless there is explicit skills list. There's no separate skills section. We'll omit Skills.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay.
Now we need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID/requisition numbers as headings (none). Must remove boilerplate: EEO statement, application instructions, powered by JazzHR, etc. Also remove navigation/cookie/legal etc. Also remove "How to Apply" and contact info. Also remove "Learn more about Bright Vision Technologies at www.bvteck.com." Also remove EEO statement. Also remove "Sponsorship: ..."? That is substantive? It's about eligibility; could be part of Requirements. We'll keep that info in Requirements.
We must preserve all substantive information: company description, location, position type, salary range, experience required, sponsorship, job summary, responsibilities list, required qualifications, preferred qualifications.
We need to format as HTML fragment.
Let's craft:
About the role
Cloud Solutions Engineer – Azure at Bright Vision Technologies, a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a 100% Remote (U.S.) full-time, direct W2 position.
But we must not repeat job title as heading; but we can mention it in paragraph. That's fine.
Now Responsibilities: list each bullet from "Key Responsibilities". We'll preserve each.
We need to ensure we don't lose any detail. Let's extract responsibilities:
- Design and implement enterprise-grade Azure cloud architectures spanning compute, networking, storage, identity, and data services, with explicit attention to scalability, security, and total cost of ownership.
- Develop, maintain, and continuously improve infrastructure-as-code using Terraform, Bicep, or ARM templates, treating infrastructure changes with the same rigor as application code through version control and peer review.
- Configure and manage Azure landing zones, virtual networks, subnets, route tables, and network security groups to enforce strong segmentation and least-privilege connectivity between workloads.
- Implement secure identity, access management, and governance controls using Azure Active Directory, conditional access, role-based access control, and Azure Policy to ensure compliance with internal and regulatory standards.
- Architect and operate Azure Kubernetes Service (AKS) clusters, including node pool design, auto-scaling, network policy, and integration with container registries and service meshes.
- Deploy, scale, and tune Azure data and analytics platforms such as Azure SQL, Cosmos DB, Synapse Analytics, Data Factory, and Event Hubs to meet specific workload patterns and SLAs.
- Build and operate comprehensive CI/CD pipelines using Azure DevOps or GitHub Actions, enabling fast, automated, and auditable releases of both infrastructure and application code.
- Design and implement robust observability practices using Azure Monitor, Log Analytics, Application Insights, and third-party tooling, with thoughtful dashboards, alerting, and SLO tracking.
- Drive Azure cost optimization initiatives, including right-sizing, reserved-instance planning, lifecycle policies, and architectural changes that meaningfully reduce monthly cloud spend.
- Implement disaster-recovery and business-continuity strategies, including backup, geo-replication, failover testing, and documented runbooks that have been validated through regular drills.
- Strengthen security posture by integrating Microsoft Defender for Cloud, Sentinel, key vault, and managed identities, and by routinely remediating findings from compliance scans.
- Collaborate closely with application teams to architect cloud-native solutions, advising on patterns, anti-patterns, and Azure-native services that best fit each problem domain.
- Develop automation scripts and tooling in PowerShell, Bash, and Python to streamline repetitive operational work and reduce time-to-resolution for common incidents.
- Mentor junior engineers, lead architecture reviews, and contribute actively to internal communities of practice around Azure and DevOps.
Now Requirements: include location, position type, experience required, sponsorship, maybe also "Job Title: Cloud Solutions Engineer – Azure" but we shouldn't repeat as heading but can mention in paragraph? Already in About the role. We'll include:
- Location: 100% Remote (U.S.)
- Position Type: Full-time, Direct W2
- Experience Required: 6+ years (or 6+ years of cloud engineering experience, with at least three years focused on Microsoft Azure in production environments) Actually the posting says Experience Required: 6+ years. Then later Required Qualifications says Five or more years of cloud engineering experience, with at least three years focused on Microsoft Azure in production environments. We'll preserve both? Might be redundant. We'll include the specifics from Required Qualifications as part of Qualifications section. For Requirements we can include location, position type, sponsorship eligibility.
Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position.
We'll put that in Requirements.
Now Qualifications: include Required Qualifications bullet list and Preferred Qualifications bullet list.
Required Qualifications:
- Bachelor’s degree in Computer Science, Engineering, or a related technical discipline.
- Five or more years of cloud engineering experience, with at least three years focused on Microsoft Azure in production environments.
- Strong hands-on experience with Azure core services, including compute, storage, networking, identity, and platform-as-a-service offerings.
- Production-level experience with infrastructure-as-code tools such as Terraform, Bicep, or ARM templates.
- Solid experience designing and operating Azure Kubernetes Service (AKS) clusters at scale.
- Hands-on experience with Azure DevOps or GitHub Actions for CI/CD across infrastructure and applications.
- Strong scripting skills in PowerShell, Bash, and Python, with the ability to write maintainable automation code.
- Deep understanding of cloud security principles, identity management, and compliance frameworks.
- Experience implementing monitoring, alerting, and observability strategies across distributed workloads.
- Strong troubleshooting, communication, and documentation skills.
Preferred Qualifications:
- Microsoft Certified: Azure Solutions Architect Expert or Azure DevOps Engineer Expert certification.
- Experience operating hybrid cloud or multi-cloud environments spanning Azure and on-premises infrastructure.
- Familiarity with service mesh technologies such as Istio or Linkerd on AKS.
- Exposure to FinOps practices and cloud cost-management tooling.
- Experience with regulated environments such as HIPAA, PCI-DSS, SOC 2, or FedRAMP.
Now Pay: Salary Range: $100,000–$150,000 Annually.
We'll put that in Pay section.
Now ensure we don't include any boilerplate: remove "How to Apply", contact info, EEO statement, "Powered by JazzHR", etc.
Now output HTML fragment.
We'll wrap each section in appropriate tags.
Let's craft:
About the role
Cloud Solutions Engineer – Azure at Bright Vision Technologies, a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a 100% Remote (U.S.) full-time, direct W2 position.
Responsibilities
- Design and implement enterprise-grade Azure cloud architectures spanning compute, networking, storage, identity, and data services, with explicit attention to scalability, security, and total cost of ownership.
- Develop, maintain, and continuously improve infrastructure-as-code using Terraform, Bicep, or ARM templates, treating infrastructure changes with the same rigor as application code through version control and peer review.
- Configure and manage Azure landing zones, virtual networks, subnets, route tables, and network security groups to enforce strong segmentation and least-privilege connectivity between workloads.
- Implement secure identity, access management, and governance controls using Azure Active Directory, conditional access, role-based access control, and Azure Policy to ensure compliance with internal and regulatory standards.
- Architect and operate Azure Kubernetes Service (AKS) clusters, including node pool design, auto-scaling, network policy, and integration with container registries and service meshes.
- Deploy, scale, and tune Azure data and analytics platforms such as Azure SQL, Cosmos DB, Synapse Analytics, Data Factory, and Event Hubs to meet specific workload patterns and SLAs.
- Build and operate comprehensive CI/CD pipelines using Azure DevOps or GitHub Actions, enabling fast, automated, and auditable releases of both infrastructure and application code.
- Design and implement robust observability practices using Azure Monitor, Log Analytics, Application Insights, and third-party tooling, with thoughtful dashboards, alerting, and SLO tracking.
- Drive Azure cost optimization initiatives, including right-sizing, reserved-instance planning, lifecycle policies, and architectural changes that meaningfully reduce monthly cloud spend.
- Implement disaster-recovery and business-continuity strategies, including backup, geo-replication, failover testing, and documented runbooks that have been validated through regular drills.
- Strengthen security posture by integrating Microsoft Defender for Cloud, Sentinel, key vault, and managed identities, and by routinely remediating findings from compliance scans.
- Collaborate closely with application teams to architect cloud-native solutions, advising on patterns, anti-patterns, and Azure-native services that best fit each problem domain.
- Develop automation scripts and tooling in PowerShell, Bash, and Python to streamline repetitive operational work and reduce time-to-resolution for common incidents.
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. We'll stick to those.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills?, Benefits?, Pay?, Schedule?.
We have Pay: Salary Range: $100,000–$150,000 Annually. So we can include Pay section.
Schedule: Not mentioned besides Full-time. Could infer schedule but not explicit. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Schedule not explicitly stated beyond Full-time (which is a type). Might be considered schedule? Probably not enough detail. We'll omit Schedule.
Benefits: Not mentioned. No benefits listed. So omit Benefits.
Skills: Could be derived from responsibilities but not explicit list. Might be better to omit Skills unless there is explicit skills list. There's no separate skills section. We'll omit Skills.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay.
Now we need to preserve all substantive information, not invent or summarize away detail. Must not repeat job title as heading. Must not put Job ID/requisition numbers as headings (none). Must remove boilerplate: EEO statement, application instructions, powered by JazzHR, etc. Also remove navigation/cookie/legal etc. Also remove "How to Apply" and contact info. Also remove "Learn more about Bright Vision Technologies at www.bvteck.com." Also remove EEO statement. Also remove "Sponsorship: ..."? That is substantive? It's about eligibility; could be part of Requirements. We'll keep that info in Requirements.
We must preserve all substantive information: company description, location, position type, salary range, experience required, sponsorship, job summary, responsibilities list, required qualifications, preferred qualifications.
We need to format as HTML fragment.
Let's craft:
About the role
About the role
Cloud Solutions Engineer – Azure at Bright Vision Technologies, a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a 100% Remote (U.S.) full-time, direct W2 position.
But we must not repeat job title as heading; but we can mention it in paragraph. That's fine. Now Responsibilities: list each bullet from "Key Responsibilities". We'll preserve each. We need to ensure we don't lose any detail. Let's extract responsibilities: - Design and implement enterprise-grade Azure cloud architectures spanning compute, networking, storage, identity, and data services, with explicit attention to scalability, security, and total cost of ownership. - Develop, maintain, and continuously improve infrastructure-as-code using Terraform, Bicep, or ARM templates, treating infrastructure changes with the same rigor as application code through version control and peer review. - Configure and manage Azure landing zones, virtual networks, subnets, route tables, and network security groups to enforce strong segmentation and least-privilege connectivity between workloads. - Implement secure identity, access management, and governance controls using Azure Active Directory, conditional access, role-based access control, and Azure Policy to ensure compliance with internal and regulatory standards. - Architect and operate Azure Kubernetes Service (AKS) clusters, including node pool design, auto-scaling, network policy, and integration with container registries and service meshes. - Deploy, scale, and tune Azure data and analytics platforms such as Azure SQL, Cosmos DB, Synapse Analytics, Data Factory, and Event Hubs to meet specific workload patterns and SLAs. - Build and operate comprehensive CI/CD pipelines using Azure DevOps or GitHub Actions, enabling fast, automated, and auditable releases of both infrastructure and application code. - Design and implement robust observability practices using Azure Monitor, Log Analytics, Application Insights, and third-party tooling, with thoughtful dashboards, alerting, and SLO tracking. - Drive Azure cost optimization initiatives, including right-sizing, reserved-instance planning, lifecycle policies, and architectural changes that meaningfully reduce monthly cloud spend. - Implement disaster-recovery and business-continuity strategies, including backup, geo-replication, failover testing, and documented runbooks that have been validated through regular drills. - Strengthen security posture by integrating Microsoft Defender for Cloud, Sentinel, key vault, and managed identities, and by routinely remediating findings from compliance scans. - Collaborate closely with application teams to architect cloud-native solutions, advising on patterns, anti-patterns, and Azure-native services that best fit each problem domain. - Develop automation scripts and tooling in PowerShell, Bash, and Python to streamline repetitive operational work and reduce time-to-resolution for common incidents. - Mentor junior engineers, lead architecture reviews, and contribute actively to internal communities of practice around Azure and DevOps. Now Requirements: include location, position type, experience required, sponsorship, maybe also "Job Title: Cloud Solutions Engineer – Azure" but we shouldn't repeat as heading but can mention in paragraph? Already in About the role. We'll include: - Location: 100% Remote (U.S.) - Position Type: Full-time, Direct W2 - Experience Required: 6+ years (or 6+ years of cloud engineering experience, with at least three years focused on Microsoft Azure in production environments) Actually the posting says Experience Required: 6+ years. Then later Required Qualifications says Five or more years of cloud engineering experience, with at least three years focused on Microsoft Azure in production environments. We'll preserve both? Might be redundant. We'll include the specifics from Required Qualifications as part of Qualifications section. For Requirements we can include location, position type, sponsorship eligibility. Sponsorship: U.S. Citizens, Green Card Holders, EAD Holders, and H-1B transfer candidates are encouraged to apply. We are unable to sponsor new H-1B visa petitions for this position. We'll put that in Requirements. Now Qualifications: include Required Qualifications bullet list and Preferred Qualifications bullet list. Required Qualifications: - Bachelor’s degree in Computer Science, Engineering, or a related technical discipline. - Five or more years of cloud engineering experience, with at least three years focused on Microsoft Azure in production environments. - Strong hands-on experience with Azure core services, including compute, storage, networking, identity, and platform-as-a-service offerings. - Production-level experience with infrastructure-as-code tools such as Terraform, Bicep, or ARM templates. - Solid experience designing and operating Azure Kubernetes Service (AKS) clusters at scale. - Hands-on experience with Azure DevOps or GitHub Actions for CI/CD across infrastructure and applications. - Strong scripting skills in PowerShell, Bash, and Python, with the ability to write maintainable automation code. - Deep understanding of cloud security principles, identity management, and compliance frameworks. - Experience implementing monitoring, alerting, and observability strategies across distributed workloads. - Strong troubleshooting, communication, and documentation skills. Preferred Qualifications: - Microsoft Certified: Azure Solutions Architect Expert or Azure DevOps Engineer Expert certification. - Experience operating hybrid cloud or multi-cloud environments spanning Azure and on-premises infrastructure. - Familiarity with service mesh technologies such as Istio or Linkerd on AKS. - Exposure to FinOps practices and cloud cost-management tooling. - Experience with regulated environments such as HIPAA, PCI-DSS, SOC 2, or FedRAMP. Now Pay: Salary Range: $100,000–$150,000 Annually. We'll put that in Pay section. Now ensure we don't include any boilerplate: remove "How to Apply", contact info, EEO statement, "Powered by JazzHR", etc. Now output HTML fragment. We'll wrap each section in appropriate tags. Let's craft:About the role
Cloud Solutions Engineer – Azure at Bright Vision Technologies, a technology consulting and software development company delivering cloud, AI, data, and enterprise solutions across the United States. This is a 100% Remote (U.S.) full-time, direct W2 position.
Responsibilities
- Design and implement enterprise-grade Azure cloud architectures spanning compute, networking, storage, identity, and data services, with explicit attention to scalability, security, and total cost of ownership.
- Develop, maintain, and continuously improve infrastructure-as-code using Terraform, Bicep, or ARM templates, treating infrastructure changes with the same rigor as application code through version control and peer review.
- Configure and manage Azure landing zones, virtual networks, subnets, route tables, and network security groups to enforce strong segmentation and least-privilege connectivity between workloads.
- Implement secure identity, access management, and governance controls using Azure Active Directory, conditional access, role-based access control, and Azure Policy to ensure compliance with internal and regulatory standards.
- Architect and operate Azure Kubernetes Service (AKS) clusters, including node pool design, auto-scaling, network policy, and integration with container registries and service meshes.
- Deploy, scale, and tune Azure data and analytics platforms such as Azure SQL, Cosmos DB, Synapse Analytics, Data Factory, and Event Hubs to meet specific workload patterns and SLAs.
- Build and operate comprehensive CI/CD pipelines using Azure DevOps or GitHub Actions, enabling fast, automated, and auditable releases of both infrastructure and application code.
- Design and implement robust observability practices using Azure Monitor, Log Analytics, Application Insights, and third-party tooling, with thoughtful dashboards, alerting, and SLO tracking.
- Drive Azure cost optimization initiatives, including right-sizing, reserved-instance planning, lifecycle policies, and architectural changes that meaningfully reduce monthly cloud spend.
- Implement disaster-recovery and business-continuity strategies, including backup, geo-replication, failover testing, and documented runbooks that have been validated through regular drills.
- Strengthen security posture by integrating Microsoft Defender for Cloud, Sentinel, key vault, and managed identities, and by routinely remediating findings from compliance scans.
- Collaborate closely with application teams to architect cloud-native solutions, advising on patterns, anti-patterns, and Azure-native services that best fit each problem domain.
- Develop automation scripts and tooling in PowerShell, Bash, and Python to streamline repetitive operational work and reduce time-to-resolution for common incidents.