US CITIZENS AND GREENCARD HOLDERS ONLY NO THIRD PARTIES Location- FULLY REMOTE Industry- Insurance Length- 6 months to start with extensions likely Interview process: 2 steps. Quick Client is looking for in depth knowledge in Azure and AWS Cloud Engineering. This is a high visibility role. The Cloud Engineer will be part of a architect/engineering team which is responsible for new mergers and acquisitions. The team is subject to executive oversight by business management at Hub International. It is a challenging, fast paced environment where environment with a strong focus on team. Job Requirements: Proficiency in Azure Core Services: • Resource groups, Virtual Networks (VNets), Azure Monitor, Bicep, Virtual Machines (VMs), IaaS, PaaS, DDI Experience with AWS Core Services: • VPCs, EC2, CloudWatch, IAM Policies, Route 53, DDI Knowledge of GCP Core Services: • Projects, VPCs, GKE, Stackdriver Strong understanding of Identity and Access Management: • RBAC, IAM policies, cross-account/cross-project access, Conditional Access Networking expertise across all CSPs: • VPC design, peering, hybrid connectivity Storage and Object Lifecycle Management: • Blob/S3/Cloud Storage classes, lifecycle rules, access tiers Compute (VMs, Containers): • Scaling, auto-healing, container orchestration (AKS, EKS, Kubernetes Native, Docker), registration Monitoring & Logging: • Cloud-native logging, alerts, distributed tracing Security & Compliance: • Encryption, Key Management, understanding of the Shared Responsibility Model Infrastructure as Code (IaC): • Terraform, Bicep, CloudFormation, Deployment Manager, ARM CI/CD Pipelines: • Experience with GitHub Actions, CodePipeline, Cloud Build, GitEnterprise Cost Optimization: • Budget management, usage reports, rightsizing, reserved instances Multi-Cloud Design: • Data egress strategies, hybrid workloads, multi-region architectures Troubleshooting Skills: • Identifying latency issues, network faults, permission problems, log tracing Communication Skills: • Ability to explain cloud designs effectively to both technical and non-technical stakeholders