1

Assistant Principal Cloud Engineer Jobs (NOW HIRING)

... Principal Cloud Architect. This role is responsible for designing, implementing, and optimizing ... with engineering, security, and business stakeholders to define cloud strategy and deliver high ...

... DevOps teams, and solution architects. • Evaluate new cloud technologies and drive innovation. • Proficient in configuring and managing Azure networking components, including virtual networks ...

$129K - $193K/yr

These teams span all different areas of cloud engineering including information security ... Principal Engineer (level 3): A high school diploma with 9 years of relevant experience OR a ...

Principal Cloud Architect

Milpitas, CA · Hybrid

$162K - $284K/yr

Our expert teams of physicists, engineers, data scientists and problem-solvers work together with ... Qualifications The Principal Cloud Architect is responsible for designing, implementing, and ...

next page

Showing results 1-20

Assistant Principal Cloud Engineer information

See salary details

$20K

$84.6K

$129.5K

How much do assistant principal cloud engineer jobs pay per year?

As of Jul 15, 2026, the average yearly pay for assistant principal cloud engineer in the United States is $84,586.00, according to ZipRecruiter salary data. Most workers in this role earn between $69,000.00 and $98,500.00 per year, depending on experience, location, and employer.

What engineers make $300,000 a year?

Senior cloud engineers, including roles like Assistant Principal Cloud Engineer, can earn $300,000 or more annually, especially with extensive experience, advanced certifications, and expertise in cloud platforms such as AWS, Azure, or Google Cloud. High-level positions often require strong skills in architecture, security, and automation, and may include bonuses or stock options that contribute to total compensation.

Will AI replace cloud engineer?

AI is unlikely to fully replace cloud engineers, as their role involves designing, managing, and troubleshooting complex cloud infrastructure that requires human expertise. Instead, AI tools are expected to augment their work by automating routine tasks, allowing cloud engineers to focus on strategic planning, security, and optimization. Staying current with cloud platforms and certifications remains important for job security in this evolving field.

How much does a principal cloud engineer make?

A principal cloud engineer typically earns between $120,000 and $180,000 annually, depending on experience, location, and the size of the organization. They often possess advanced skills in cloud platforms like AWS, Azure, or Google Cloud, and may hold certifications such as AWS Certified Solutions Architect or Google Cloud Professional Cloud Architect.

What engineer makes $500,000 a year?

Senior cloud engineers, including roles like Assistant Principal Cloud Engineer, can earn $500,000 or more annually, especially with extensive experience, specialized skills in cloud architecture, and certifications such as AWS or Azure. High-level positions in large organizations or consulting firms tend to offer such compensation packages.
What cities are hiring for Assistant Principal Cloud Engineer jobs? Cities with the most Assistant Principal Cloud Engineer job openings:
What are the most commonly searched types of Principal Cloud Engineer jobs? The most popular types of Principal Cloud Engineer jobs are:
What states have the most Assistant Principal Cloud Engineer jobs? States with the most job openings for Assistant Principal Cloud Engineer jobs include:
Infographic showing various Assistant Principal Cloud Engineer job openings in the United States as of July 2026, with employment types broken down into 1% As Needed, 75% Full Time, 21% Part Time, 1% Temporary, and 2% Contract. Highlights an 99% Physical, and 1% Remote job distribution, with an average salary of $84,586 per year, or $40.7 per hour.
Principal Cloud Engineer - DevOps/Infrastructure

Principal Cloud Engineer - DevOps/Infrastructure

Resultant

Chicago, IL

$57.50 - $76.75/hr

Full-time

Posted 18 days ago


Job description

Company Description

Resultant is a modern consulting firm with a radically different approach to solving problems.  

We don’t solve problems for our clients. We solve problems with them. 

Through outcomes driven by data analytics, technology solutions, digital transformation, and beyond, our team works with clients in both the public and private sectors to solve their most complex challenges. We start by learning as much as we can about who they are, how they work, and what they’re striving for so we can feel their problems as our own. Partnering with our clients means their desired outcomes are always top of mind, their challenges and strengths guiding our efforts. We build client-focused relationships before we build unique solutions that blaze past expectations. 

Originally founded in Indianapolis in 2008, Resultant now employs more than 400 team members who operate from offices around the United States including Indianapolis and Fort Wayne, Indiana; Columbus, Ohio; Lansing, Michigan; Denver, Colorado; Dallas, Texas and Atlanta, Georgia. 

We’re Resultant. Clients partner with us to see a difference. People join us to make one. 

Job Description

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.
Qualifications

Qualifications

Must Have

  • 12+ years in cloud infrastructure, DevOps, or platform engineering, with deep production ownership and a record of setting technical direction.
  • Deep, hands-on expertise across all three of AWS, Google Cloud, and Azure, or mastery of two with strong production experience in the third.
  • Expert-level Infrastructure as Code, especially Terraform, with patterns and module libraries you have personally established as the standard across multiple teams.
  • Production Kubernetes experience (EKS, GKE, or AKS), including day-2 operations and troubleshooting.
  • Strong CI/CD design experience (GitHub Actions, GitLab CI, Azure DevOps, Jenkins, or similar).
  • Advanced scripting and automation in Python, Bash, and/or PowerShell.
  • Deep networking fundamentals across clouds: VPC and VNet design, DNS, load balancing, hybrid connectivity, and private-by-default access patterns (PrivateLink, Private Service Connect, Shared VPC, and multi-account or multi-project connectivity).
  • Strong grounding in cloud security and identity (IAM, RBAC, secrets management, encryption).
  • A track record as a design authority and top escalation point, and of mentoring senior engineers and setting standards others adopt.
  • Experience leading technical solutioning or pre-sales in a client-facing or consulting environment.
  • Strong written and spoken English communication skills, including with executive audiences.

Nice to Have

  • Multi-account or multi-project landing zone design (AWS Control Tower, GCP organization policy, Azure Landing Zones).
  • GitOps and progressive delivery (ArgoCD, Flux), and service mesh experience.
  • Policy as code (OPA, Sentinel) and compliance frameworks (SOC 2, FedRAMP, HIPAA).
  • FinOps and large-scale cost optimization.
  • VMware and hybrid or private cloud experience.

Additional Information

What It's Like to Work Here

At Resultant, we are driven by purpose—partnering with clients to take on their toughest challenges and creating outcomes that make a real difference. Success here means lasting impact, not just delivered projects. We work as collaborative experts, leaning into complexity with confidence and humility, asking smart questions, sharing ideas freely, and combining our diverse expertise to turn challenges into clear, transformative solutions. We make our outcomes visible by sharing results, stories, and lessons learned, because growth happens through shared experience.

Accountability & Ownership

Resultant offers a flexible, high-trust environment, paired with a shared commitment to accountability:

  • Take ownership of your work from start to finish and deliver on your commitments to clients and coworkers
  • Communicate proactively, especially when priorities shift
  • Focus on outcomes, follow-through, and measurable impact
  • Show up where it matters, in person or virtually, when it strengthens relationships or results
  • Do the small things brilliantly: respond timely, stay organized, and follow through to build trust

We trust each other to own our work and deliver exceptional results. Flexibility means autonomy paired with accountability: the freedom to work in ways that fit your life, balanced with the reliability our clients and coworkers count on.

Is Resultant the right spot for you?

You may thrive here if you bring curiosity and a consulting mindset to every challenge, take ownership of your growth, and give and receive feedback with intention. If you're energized by bold ideas, continuous learning, and investing in the people around you, this is your place. At Resultant, we show up for each other, own our outcomes, and build leaders who create lasting impact for our clients, our communities, and each other.

Equal Opportunity Employer 

We embrace AI across everything we do, and that includes how you prepare for this interview. Feel free to use AI tools to research the role, practice your responses, and put your best foot forward. What matters to us is getting to know the real you — how you think, how you communicate, and what you genuinely bring to the table. Our interviews are designed to go deeper than any polished answer, so come curious and come as yourself without the support of an AI tool during our conversation.