Principal Cloud Engineer - DevOps/Infrastructure

About the Role

We are looking for a Principal Cloud Engineer to serve as the senior-most technical authority for how we design, build, and operate infrastructure across AWS, Google Cloud, and Azure. This is a hands-on, infrastructure-focused role for an engineer who has spent more than a decade in production environments and now sets the standards, patterns, and reference architectures that entire teams build on. You will own the hardest architecture decisions, act as the final technical escalation point, and multiply the impact of every engineer around you.

You will work across internal platforms and client-facing engagements, shaping solutions from pre-sales through production. This is a principal-level individual contributor role and design authority. Your leverage comes from the standards you set, the accelerators you build, and the technical direction you drive across the practice, not from managing people.

Key Responsibilities

• Technical authority. Act as the design authority for multi-cloud infrastructure across AWS, Google Cloud, and Azure. Own the hardest architecture decisions and serve as the final escalation point for production-critical problems across engagements.
• Standards and reference architectures. Define the firm-wide standards, patterns, and reference architectures for landing zones, networking, identity, and workload platforms that every team builds on. Set account, subscription, and project structure, environment separation, and identity boundaries as defaults.
• Infrastructure as Code. Own the IaC standard for the practice. Build the reusable, modular Terraform and the module library that other engineers adopt by default, and govern state, versioning, and drift at scale.
• Container platforms. Set the standard for running Kubernetes in production (EKS, GKE, AKS), including networking, autoscaling, workload isolation, and day-2 operations. Own container registries and artifact promotion (ECR, ACR, Artifact Registry) and golden image pipelines (cloud-init, image bake) for consistent, hardened builds.
• Solutioning and pre-sales. Shape proposals and estimates, lead technical discovery, and represent the firm as the senior cloud voice in client and executive conversations.
• Delivery automation. Build and harden CI/CD pipelines and deployment automation that move code to production safely and repeatably.
• Reliability. Establish observability, SLOs, and incident response practices. Lead root cause analysis and drive permanent fixes rather than repeated firefighting.
• Security and compliance. Define the cloud security and compliance posture: identity and least-privilege access, secrets management, network segmentation, encryption, and policy as code.
• Cost and efficiency. Drive cost visibility and optimization (FinOps) across accounts, projects, and clouds.
• Leadership and mentorship. Raise the technical bar across the practice. Mentor and grow senior engineers, shape the hiring bar, and lead design reviews.
• Accelerators. Build the accelerators and reference implementations that cut delivery time and raise quality across every engagement.