> Markdown version of [/jobs/ext/3124757-multi-cloud-engineer](https://www.wearedevelopers.com/jobs/ext/3124757-multi-cloud-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Multi-Cloud Engineer

- **Company:** Mindsource Inc
- **Location:** Cupertino, CA, United States
- **Experience:** Expert
- **Contract:** Temporary contract
- **Skills:** Amazon Web Services, Amazon Elastic Compute Cloud, Proxy Servers, Bash Shell, Cloud Computing, Computer Networks, Domain Name System (DNS), Github, Identity and Access Management, Subnetting, Python (Programming Language), Routing, Node.Js, Reliability Engineering, Ansible, Spinnaker, Software Vulnerability Management, Datadog, Data Logging, Scripting, Transport Layer Security, Google Cloud, Load Balancing, Grafana, Firewalls (Computer Science), Amazon Virtual Private Cloud (VPC), Git, Cloudformation, Kubernetes, Route53, Cloudwatch, Terraform, Splunk, Pagerduty
- **Published:** September 28, 2026
- **Apply:** https://www.dice.com/job-detail/c93a1e2f-7ade-488d-b50f-81e439c0491d

## About the Role

* AWS: EC2, VPC, NLB and ALB, Route 53, subnet and address-space reconciliation, IAM roles anywhere
 * Google Cloud Platform: GCE, service accounts, vulnerability remediation workflows, project and folder structure
 * AliCloud: region-specific service availability and version constraints, STS and RAM
 * Cross-provider differences in quota, IAM, and network models. Knowing where the three diverge is the point of the role

Platform tooling - must have

 * Infrastructure as code: Terraform or Ansible, including drift detection and blast-radius management
 * Deployment and release tooling such as Spinnaker
 * Compass compliance onboarding, backup services, image and golden-AMI lifecycle
 * Internal cloud inventory and query tooling for account, resource, and spend reporting

Observability - must have

 * Prometheus and Grafana: dashboard authorship and alert definition that is actionable, not noise
 * Splunk: forwarding, query authorship, and use in live incident diagnosis
 * Defining SLIs for provisioning success, gateway availability, and request latency

Networking - must have

 * Cross-environment DNS resolution and connectivity to managed database services
 * Load balancer reconcile loops and subnet annotation behavior
 * Gateway and proxy endpoint troubleshooting, including destination allow-listing and egress paths
 * Outage triage and formal RCA authorship

Automation and code - must have

 * Python or Go sufficient to ship tooling that goes through peer review, not throwaway scripts
 * Converting repeat manual remediation into runbook automation or self-service paths
 * Git-based operational workflow, GitHub Actions, PagerDuty

Incident discipline - must have

 * Run an incident end to end: triage, mitigate, verify recovery against the customer-facing signal, resolve
 * Journal every investigation in writing as you work, so the next shift continues instead of restarting
 * Blameless RCA authorship and promotion of findings into the shared runbook library
 * Clear written English. Most hand-offs happen in writing across time zones, * 5+ years in cloud infrastructure support, site reliability, or cloud operations engineering. The multi-provider scope sets this bar above a single-cloud equivalent role.
 * Deep production expertise in at least one major cloud provider, with demonstrated working competence in a second. Depth in AWS or Google Cloud Platform is the most common qualifying profile.
 * Strong identity and access management fundamentals that transfer across providers: role assumption and delegation, service and machine identities, policy evaluation and troubleshooting, and federated or directory-sourced group mapping.
 * Practical Kubernetes operations experience (EKS, GKE, or ACK) - inspecting pod and node state, diagnosing volume and networking failures, and interpreting cluster events.
 * Working knowledge of enterprise network fundamentals: routing, DNS, TLS, proxies, CIDR planning, and firewall/ACL models.
 * Scripting proficiency in Python or Bash, plus fluency with provider CLIs.
 * Excellent written English - the majority of support happens asynchronously in text, and clarity directly determines resolution speed., * Certification in one or more of: AWS Solutions Architect (Associate/Professional), Google Professional Cloud Architect, Alibaba Cloud ACP.
 * Prior AliCloud experience or demonstrated rapid ramp on an unfamiliar cloud provider. Evidence of learning a new provider quickly is an acceptable and expected substitute.
 * Experience supporting internal developer platforms in a large enterprise.
 * Familiarity with hybrid connectivity between corporate networks and public cloud.
 * Infrastructure-as-code exposure (Terraform, CloudFormation).
 * Observability tooling experience (Splunk, Datadog, CloudWatch, Cloud Logging).
 * Prior follow-the-sun or multi-region support rotation experience

## Description

* Account lifecycle across providers: onboarding, org hierarchy placement, service enablement, decommission
 * Provisioning failure diagnosis and stuck-state recovery, from request intake to delivered resource
 * Quota management: request, validation, pre-requisite checks, and capacity escalation to the provider
 * IAM and access: roles, trust policies, federated and short-lived credentials, SSO role mapping
 * Cost visibility and remediation: identifying waste, right-sizing, and tracking realized savings