Senior Cloud Operations Engineer

Nimble | Career PageJob Openings Senior Cloud Operations Engineer About the job Senior Cloud Operations Engineer Senior Cloud Operations Engineer Location: Remote (Global) Team: Cloud Infrastructure / DevOps Summary You'll design, build, and operate the CI/CD and cloud infrastructure backbone that powers this client's software products across AWS, Azure, and GCP. You'll work directly with engineering teams to migrate on-prem workloads to the cloud, harden security, and automate everything that shouldn't be touched by hand. This is a hands-on engineering role — expect to write as much code as you do architecture. Requirements (Must-Haves) Excellent English communication skills — you'll interact directly with client-side engineering leads, present architecture decisions, and own cross-team coordination without hand-holding 7+ years of hands-on experience deploying and operating software on cloud infrastructure (AWS, Azure, or GCP) — real production environments, not sandbox tinkering 7+ years building and maintaining automated CI/CD pipelines — Jenkins, Bamboo, or equivalent; you should be able to debug a broken pipeline at 2am Strong Azure expertise — this is the primary cloud; Azure networking, IAM, monitoring, and PaaS services are day-to-day territory Proficiency in Infrastructure as Code — CloudFormation, Terraform, or Ansible; you've used it to build environments from scratch, not just tweak existing templates Expert-level scripting and programming — Python, Bash, and at least one compiled language (C#/.NET, Java); you write clean, reviewable code Solid grasp of security, access control, and compliance — you can configure least-privilege IAM, set up monitoring/alerting, and explain the security posture of an environment clearly Experience migrating on-prem applications to the cloud — you've done it at least once end-to-end, not just helped Hands-on with containerization — Docker and/or Kubernetes in production Requirements (Nice-to-Haves) Experience with multi-cloud environments — able to navigate differences between AWS, Azure, and GCP without starting from scratch each time Familiarity with compliance frameworks — SOX, HIPAA, or similar; you've worked in regulated environments and know what "audit-ready infrastructure" means Integration experience with on-prem enterprise tech — Microsoft, IBM, or HP stacks alongside cloud-hosted services Working knowledge of multiple OS environments — Windows and Linux are standard; macOS or mobile build environments are a plus Experience with APM and cloud monitoring tooling — Datadog, New Relic, CloudWatch, Azure Monitor — you set it up, you tune the alerts, you own the dashboards Bonus Points Hands-on Jenkins plugin ecosystem knowledge — build job configuration, front-end build pipelines, plugin management Experience with mobile build and test automation — iOS/Android CI pipelines are rare and valuable Cloud certifications — AWS Solutions Architect, Azure Administrator (AZ-104), or GCP Professional Cloud Architect Open source contributions or published tooling in DevOps/infrastructure space Experience with GitOps workflows (ArgoCD, Flux) — increasingly relevant for teams moving toward Kubernetes-native delivery Apply for Position Share Facebook Line LinkedIn X (Formerly Twitter) Whatsapp EmailRemoteSenior
Active

Job description

Senior Cloud Operations Engineer Location: Remote (Global) Team: Cloud Infrastructure / DevOps Summary You'll design, build, and operate the CI/CD and cloud infrastructure backbone that powers this client's software products across AWS, Azure, and GCP. You'll work directly with engineering teams to migrate on-prem workloads to the cloud, harden security, and automate everything that shouldn't be touched by hand. This is a hands-on engineering role — expect to write as much code as you do architecture. Requirements (Must-Haves) Excellent English communication skills — you'll interact directly with client-side engineering leads, present architecture decisions, and own cross-team coordination without hand-holding 7+ years of hands-on experience deploying and operating software on cloud infrastructure (AWS, Azure, or GCP) — real production environments, not sandbox tinkering 7+ years building and maintaining automated CI/CD pipelines — Jenkins, Bamboo, or equivalent; you should be able to debug a broken pipeline at 2am Strong Azure expertise — this is the primary cloud; Azure networking, IAM, monitoring, and PaaS services are day-to-day territory Proficiency in Infrastructure as Code — CloudFormation, Terraform, or Ansible; you've used it to build environments from scratch, not just tweak existing templates Expert-level scripting and programming — Python, Bash, and at least one compiled language (C#/.NET, Java); you write clean, reviewable code Solid grasp of security, access control, and compliance — you can configure least-privilege IAM, set up monitoring/alerting, and explain the security posture of an environment clearly Experience migrating on-prem applications to the cloud — you've done it at least once end-to-end, not just helped Hands-on with containerization — Docker and/or Kubernetes in production Requirements (Nice-to-Haves) Experience with multi-cloud environments — able to navigate differences between AWS, Azure, and GCP without starting from scratch each time Familiarity with compliance frameworks — SOX, HIPAA, or similar; you've worked in regulated environments and know what "audit-ready infrastructure" means Integration experience with on-prem enterprise tech — Microsoft, IBM, or HP stacks alongside cloud-hosted services Working knowledge of multiple OS environments — Windows and Linux are standard; macOS or mobile build environments are a plus Experience with APM and cloud monitoring tooling — Datadog, New Relic, CloudWatch, Azure Monitor — you set it up, you tune the alerts, you own the dashboards Bonus Points Hands-on Jenkins plugin ecosystem knowledge — build job configuration, front-end build pipelines, plugin management Experience with mobile build and test automation — iOS/Android CI pipelines are rare and valuable Cloud certifications — AWS Solutions Architect, Azure Administrator (AZ-104), or GCP Professional Cloud Architect Open source contributions or published tooling in DevOps/infrastructure space Experience with GitOps workflows (ArgoCD, Flux) — increasingly relevant for teams moving toward Kubernetes-native delivery

Senior Cloud Operations Engineer

Senior Cloud Operations Engineer

Location: Remote (Global)

Location:

Team: Cloud Infrastructure / DevOps

Team:

Summary

Summary

You'll design, build, and operate the CI/CD and cloud infrastructure backbone that powers this client's software products across AWS, Azure, and GCP. You'll work directly with engineering teams to migrate on-prem workloads to the cloud, harden security, and automate everything that shouldn't be touched by hand. This is a hands-on engineering role — expect to write as much code as you do architecture.

Requirements (Must-Haves)

Requirements (Must-Haves)
  • Excellent English communication skills — you'll interact directly with client-side engineering leads, present architecture decisions, and own cross-team coordination without hand-holding
Excellent English communication skills
  • 7+ years of hands-on experience deploying and operating software on cloud infrastructure (AWS, Azure, or GCP) — real production environments, not sandbox tinkering
7+ years
  • 7+ years building and maintaining automated CI/CD pipelines — Jenkins, Bamboo, or equivalent; you should be able to debug a broken pipeline at 2am
7+ years
  • Strong Azure expertise — this is the primary cloud; Azure networking, IAM, monitoring, and PaaS services are day-to-day territory
Strong Azure expertise
  • Proficiency in Infrastructure as Code — CloudFormation, Terraform, or Ansible; you've used it to build environments from scratch, not just tweak existing templates
Infrastructure as Code
  • Expert-level scripting and programming — Python, Bash, and at least one compiled language (C#/.NET, Java); you write clean, reviewable code
Expert-level scripting and programming
  • Solid grasp of security, access control, and compliance — you can configure least-privilege IAM, set up monitoring/alerting, and explain the security posture of an environment clearly
security, access control, and compliance
  • Experience migrating on-prem applications to the cloud — you've done it at least once end-to-end, not just helped
migrating on-prem applications to the cloud
  • Hands-on with containerization — Docker and/or Kubernetes in production
containerization

Requirements (Nice-to-Haves)

Requirements (Nice-to-Haves)
  • Experience with multi-cloud environments — able to navigate differences between AWS, Azure, and GCP without starting from scratch each time
multi-cloud environments
  • Familiarity with compliance frameworks — SOX, HIPAA, or similar; you've worked in regulated environments and know what "audit-ready infrastructure" means
compliance frameworks
  • Integration experience with on-prem enterprise tech — Microsoft, IBM, or HP stacks alongside cloud-hosted services
on-prem enterprise tech
  • Working knowledge of multiple OS environments — Windows and Linux are standard; macOS or mobile build environments are a plus
multiple OS environments
  • Experience with APM and cloud monitoring tooling — Datadog, New Relic, CloudWatch, Azure Monitor — you set it up, you tune the alerts, you own the dashboards
APM and cloud monitoring tooling

Bonus Points

Bonus Points
  • Hands-on Jenkins plugin ecosystem knowledge — build job configuration, front-end build pipelines, plugin management
Jenkins plugin ecosystem
  • Experience with mobile build and test automation — iOS/Android CI pipelines are rare and valuable
mobile build and test automation
  • Cloud certifications — AWS Solutions Architect, Azure Administrator (AZ-104), or GCP Professional Cloud Architect
AWS Solutions Architect, Azure Administrator (AZ-104), or GCP Professional Cloud Architect
  • Open source contributions or published tooling in DevOps/infrastructure space
  • Experience with GitOps workflows (ArgoCD, Flux) — increasingly relevant for teams moving toward Kubernetes-native delivery
GitOps workflows