Cloud / Platform Engineer (Kubernetes, GCP, AWS)

Supero • US-Remote • Sep 18, 2026 •

> ROLE OVERVIEW

We deploy other people's applications on demand: a generated app becomes a live URL, on our infrastructure or inside the customer's own AWS or GCP account. That is an infrastructure product hiding inside an application platform. It works, it is in production, and it has more shell script and less automation in it than a system this important should have. You would own it, and the mandate is to make it boring. On call, honestly.

> CORE RESPONSIBILITIES

The Kubernetes platform. A high-availability control plane, our own registry, deployment topology, and the rendered manifests behind it.
Multi-cloud deploy paths. GCP (Cloud Run, Cloud Build, GCS) and AWS (CodeBuild, ECR, App Runner/ECS).
Preview and live environments. Ephemeral previews and long-lived production apps, which we separated properly after learning the hard way that they must not share a lifecycle.
CI/CD and release. Build, image promotion, rollout, rollback — and making 'which version is actually running in that pod' a five-second question.
Observability and cost. Logs a human can find, alerts that mean something, and a cloud bill that scales with customers rather than with mistakes.
Security posture. Secrets, network policy, TLS, CSP and CORS on served applications, and the tenant boundary at the infrastructure layer.

> HARD REQUIREMENTS & SPECS

4+ years in cloud infrastructure, platform engineering or SRE, running production.
Kubernetes past the tutorial — you have debugged a cluster at 2am and can explain what you found.
AWS and/or GCP at depth, IAM included. Especially IAM.

Apply via Direct ATS

Is the AI extraction inaccurate? Report an issue