Job Description
About the Role:
We’re looking for a Cloud Engineer who thrives in environments where systems scale fast, reliability isn’t negotiable, and automation replaces repetition. You’ll be key in building, optimizing, and securing the infrastructure that powers our platform across AWS and GCP. If you’ve ever designed a Terraform module that others begged to borrow—or written a Lambda function just to prove that cron jobs were lazy—keep reading.
You Will:
- Design and maintain infrastructure-as-code for multi-cloud environments (primarily AWS and GCP) using Terraform and Pulumi.
- Own the rollout of ephemeral environments for feature testing and blue/green deployments in Kubernetes.
- Build and maintain CI/CD pipelines (we use GitHub Actions, ArgoCD, and a sprinkle of custom runners).
- Implement observability tooling that gives engineers actionable insights without dashboards that resemble a cockpit.
- Work with Security to implement IAM policies, service mesh encryption (we use Istio), and audit pipelines.
- Automate incident response runbooks—yes, real automation, not just documentation.
- Participate in architecture discussions and be the loud advocate for operational simplicity.
You Have:
- 3+ years of cloud infrastructure experience, including at least one production-grade deployment in both AWS and GCP (we won’t count Azure unless it comes with a compelling redemption story).
- Strong hands-on experience with Terraform (not just using modules—writing them).
- Real-world Kubernetes experience—debugging cluster issues, tuning autoscalers, and managing Helm charts.
- Comfort with Golang or Python for scripting infrastructure tasks and writing tools.
- Familiarity with service meshes, secret management (we use HashiCorp Vault), and container security.
- The ability to trace a problem across logs, metrics, and traces—and fix it without escalating.
- Not afraid of YAML, but know when it’s gone too far.
Bonus Points If You:
- Built internal tooling that actually gets adopted by other teams.
- Have opinions on why “serverless” is or isn’t the right choice—and evidence to back it up.
- Can explain the difference between SLOs, SLIs, and SLAs without Googling.
- Contributed to open-source infra projects (share your GitHub or relevant PRs).
Are you interested in this position?
Apply by clicking on the “Apply Now” button below!
#GraphicDesignJobsOnline#WebDesignRemoteJobs #FreelanceGraphicDesigner #WorkFromHomeDesignJobs #OnlineWebDesignWork #RemoteDesignOpportunities #HireGraphicDesigners #DigitalDesignCareers#Dynamicbrandguru