Senior Cloud Infrastructure Engineer - Product
At a glance
Senior Platform & Infrastructure role at Trener. San Jose · full-time · no salary stated · we estimate $146,057–$210,000 across the United States.
Trener has not published a salary for this role. The figure below is our estimate, not theirs.
devopsroles summary, based on the employer's posting.
What you'll do
- Run the Google Cloud platform, covering projects, networking, GKE, access, cost visibility and shared services
- Build and maintain OpenTofu modules and Atmos configuration, with reviewed CI changes and drift checks
- Handle cluster upkeep, Helm charts and ArgoCD delivery for internal services
- Keep cloud monitoring, data collection and remote support working for robots in the field
- Document, secure and upgrade the platform while coordinating infrastructure changes with cloud and delivery peers
What you bring
- You have run production infrastructure and taken responsibility when it failed
- You have authored reusable Terraform or OpenTofu modules, managed state across environments and maintained infrastructure over time
- You bring production GCP experience with GKE, VPC networking and IAM, or deep AWS or Azure experience plus hands-on GCP exposure
- You can operate Kubernetes, write Helm charts and troubleshoot networking across routing, DNS, TLS and load balancing
- You use Python and Bash for automation, diagnostics and glue, work fluently in Linux, and communicate clearly in written English
Who this fits
This is a senior individual-contributor role reporting to the Chief Product Officer, with no direct reports at the start and possible technical leadership as the team grows. You’ll work onsite in San Jose and coordinate with peers, including across time zones.
From the employer
About Trener
Trener is building the software foundation for a new generation of industrial robotics. We combine advanced AI, intuitive programming, and pre-trained skill models to make robots easier to deploy, operate, and adapt to real-world industrial work. With teams in San Jose and Trondheim, we build software that connects cloud infrastructure, developer platforms, and deployed robotic systems.
About the Role
We run a production cloud platform on Google Cloud today: private GKE clusters managed with OpenTofu and Atmos, GitOps delivery, self-hosted CI, a container registry, secrets management, and the monitoring and remote-support services behind our deployed robot fleet. It is a working production platform, and we are now building a cloud team to own and grow it.
You will own our GCP platform. You will work as a peer to a cloud engineer in T-Labs, our research organization, who owns our AWS environment. The two of you agree on shared conventions and review each other's infrastructure changes. You will also work closely with our delivery infrastructure engineer, and the greater engineering team.
This is a senior individual contributor role reporting to the Chief Product Officer. You will not have direct reports at the start. As the team grows, this role may take on technical leadership of cloud infrastructure.
What You Will Own
Our GCP platform: project structure, networking, GKE clusters, access controls, cost visibility, and the shared services that run on them. You keep it running, secure, upgraded, and documented.
Infrastructure as code and delivery: the OpenTofu modules and Atmos configuration that describe the platform, and reviewed plan/apply in CI with drift detection.
Kubernetes and GitOps: cluster lifecycle, Helm charts for our internal services, and ArgoCD-based delivery.
Cloud services for our robot fleet: the cloud side of remote monitoring, data gathering, and remote support for deployed robots.
Requirements
Production operations: You have operated production infrastructure as a cloud, platform, infrastructure, or site reliability engineer, including being responsible when it broke.
Terraform or OpenTofu at module-authoring depth: You have written and versioned reusable modules, managed state across multiple environments, and handled the lifecycle of real infrastructure over time.
Production GCP experience: GKE, VPC networking, IAM, and service accounts in a production setting. Equivalent depth on AWS or Azure is acceptable if you have hands-on GCP exposure and can show how you learned a new provider before.
Kubernetes operations: Cluster upgrades, RBAC, networking, and troubleshooting workloads that will not start or cannot communicate.
Helm chart authoring: not just chart installation.
Networking depth: VPCs, routing, DNS, TLS, load balancing, firewall policy, and debugging connectivity across those layers.
Python and Bash: for automation, diagnostics, and glue, plus Linux fluency.
Clear written communication in English: Infrastructure decisions here are discussed, documented and reviewed in writing, often across time zones.
Experience That Will Help You Succeed
Cloud services that support physical devices in the field: robots, IoT, or industrial equipment.
Taking ownership of an existing production system and improving it.
Infrastructure composition tooling such as Atmos, Terragrunt, or Terraspace.
Building CI for infrastructure: automated plan/apply, policy checks, drift detection.
GitOps with ArgoCD across multiple environments.
Externalized secrets management and Kubernetes-native secret delivery.
Operating Prometheus, Grafana, and Loki, or comparable observability tooling.
Overlay or private networking such as Tailscale or WireGuard.
Production experience on a second major cloud provider.
What We Offer
The opportunity to work at the intersection of robotics, AI, and cloud infrastructure, as a founding member of a cloud team. A senior technical role with direct influence over the foundations the company builds on, reporting to the Chief Product Officer.
A growing international engineering organization with teams in the United States and Norway.
Platform & Infrastructure work from LinkedIn, X, Reddit and Upwork, in one list.
Each morning you get everything that fits, strongest first.
Platform & Infrastructure
Find me workBy the team behind devopsroles.