As a DevOps Principal Engineer, you will be part of a team that is responsible for the research and development of advanced vision care cloud solutions, saving vision for diabetic patients in primary healthcare settings.
The ideal candidate will have 5+ years of validated experience in Azure DevOps, infrastructure management, and solution architecture, with hands-on experience building scalable, reliable deployment pipelines and managing cloud-based environments.
What you'll be doing:
Design, build, and maintain CI/CD pipelines in Azure DevOps using YAML.
Manage and automate infrastructure deployments using Azure CLI and related tools.
Ensure stable and secure connectivity to databases across environments.
Manage and configure Azure VNets, subnets, and related networking components to support application and infrastructure needs.
Collaborate with cross-functional teams to support solution delivery and ensure alignment with overall architecture patterns.
Administer and troubleshoot Windows Server environments in cloud setups.
Analyze and enhance system reliability, performance, and scalability through automation and best practices.
Job Requirements
Details:
B.S. in an engineering, software development, or related subject area with 5+ years of validated experience in a DevOps and network administration role supporting cloud-based solutions.
Strong proficiency with Azure DevOps, including repository management, pipeline creation (YAML), and release management.
Experience with scripting languages such as PowerShell and Azure CLI for resource provisioning and management.
Solid understanding of Windows Server configuration, management, and troubleshooting.
Knowledge of database connectivity (SQL Server, Azure SQL, etc.) across different network environments.
Deep understanding of Azure networking concepts including VNets, subnets, NSGs, and VPN connectivity.
Familiarity with solution architecture principles and how infrastructure design impacts system performance, security, and scalability.
Ability to work collaboratively in cross-functional teams and communicate technical concepts to non-technical stakeholders