Skip to content
Esc
Internships in Canada
New-grad roles in Canada
Remote roles
Roles that show pay
Postings at high ghost risk
PayWhat student tech roles in Canada pay
Check a linkPaste a posting to see its real age and ghost risk
JobsEvery open tech role
CompaniesWho fills fastest, who leaves postings up
Hiring calendarWhen employers open intern and new-grad roles
Skills gapWhat postings ask for that you don't have
Your resumeScore and fixes
Your matchesOpen roles ranked by your resume
ApplicationsSaved, applied, interviewing, offers
SettingsTheme, text size, motion
How it works

↑ ↓ to move, Enter to open? every shortcut

Keyboard shortcuts

CtrlKor/
Search employers, postings and pages
JorK
Next or previous posting in a list
O
Open the posting's page
Enter
Open it in the preview, on wide screens
S
Save or unsave it
?
This list
Esc
Close
Trener Robotics

Senior Cloud Infrastructure Engineer - Product

  • Seen live on Trener Robotics' site 3 days ago
  • Senior
Pay
Not stated
Location
San Jose (US-HQ)
Open for
11+ days
First seen
Oct 24, 2026
Apply on Trener Robotics' site (opens in a new tab)

Posting record

No flags

Open 11+ days

The posting's record, oldest first
  1. Trener Robotics' site dates the posting
  2. Ghostless first sees this listing
  3. Last checked: still up
How we know

It hasn't been reposted, listed twice, or left up unusually long, and the posting doesn't say it's a talent pool.

Ghostless records the day it first sees a posting, so a repost can't reset its age. This one was already up when Ghostless started tracking Trener Robotics, so its true age is longer.

Last checked Nov 1, 2026.

How well do you match?

See how much of this posting your resume shows, and what it's missing.

Upload your resume

What the posting discloses

Not stated: Pay, real vacancy, AI screening.

Why these three

Ontario requires postings from employers with 25 or more staff to state the pay, whether the vacancy exists, and whether AI screens applicants.

Some employers add pay only on their own site. Check the original posting before you rule it out.

Skills mentioned

About the role

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.

Something wrong with this posting?