Sr. Azure Cloud IaC Developer
- 1 Point Systems
32 Days Ago
NA
NA
Chicago-IL, Portland-ME, Boston-MA, Dallas-TX
10-40 Years
Required Skills: Azure, IaC, Terraform, Virtual Networks, github
Job Description
Role: Sr. Azure Cloud IaC Developer
Location: This is a remote position; however, the candidate must reside within 30 miles of one of the following locations: Portland, ME, Boston, MA, Chicago, IL, Dallas, TX.
Engineers (Level 4 and Level 5)
- Level 4 = 5+ YOE (that is a rough guide, will be based on actual knowledge and hands on work)
- #1 focus is on IaC; will also have standard cloud security, disaster recovery, automation responsibilities, but IaC and strong terraform experience is the biggest need
- Manage cloud Infrastructure as Code (Terrafrom)
- Create/manage pipelines for landing zones, subscriptions, and security infrastructure; modify existing configurations, some hands on terraform code with new subscriptions
- Working to migrate all version control from Azure DevOps to GitHub (leverage github actions and github runners)
- Extensive experience with Azure (5+ years), specifically with Azure Networking services (Vnet, DNS, Load Balancing, VPN Gateway)
- Additional responsibilities: Cloud automation, monitoring, disaster recovery, documentation
Must Have Skills:
- Terraform for Infrastructure as Code (IaC)
- Azure Networking Services (Vnet, Load balancing, CPN Gateway, DNS)
- Github/GitHub actions (version control)
- Azure DevOps
- General expertise in Azure
Nice to Have Skills:
- AWS
- Kubernetes (not currently using with Azure, but moving there)
- Splunk (logging/monitoring)
- Datadog (moving to Azure DevOps)
- Jenkins (CI/CD)
Team:
- 8 engineers currently
- 3 focused on Azure, 2 strong - 1 is stronger on AWS
- Sit in Brazil
- One helps additionally with the architecture and designing layouts
- Backlog of projects for this team to implement
- Moving to an agile set up (previously just worked off a Kanban board)
- On call rotation for whole team regardless of level (~5-6 week rotation)
- Nights/weekends
- Rare to get called in - operations team gets called first, this team would be 2nd
