# Senior AI Infrastructure Engineer at Hellyeah

> Onsite · United States · Senior · DevOps / SRE / Infra · open. Source: https://alderhq.app/jobs/ashby%3Ahellyeah%3A56897c0b-302f-45cf-9dd5-07556b7a54dc (read 2026-11-08).

## Facts (observed)

- Company: [Hellyeah](https://alderhq.app/companies/hellyeah)
- Location text: San Francisco HQ; Shanghai
- Where it can be done from (inferred): Onsite · United States (evidence: "Location: San Francisco HQ; Shanghai")
- Posted: 2026-11-02 (6 days ago)
- First seen by alder: 2026-11-04 · last verified: 2026-11-04
- Reposted: 0 times · edited: 0 times
- Apply on the employer's site: https://jobs.ashbyhq.com/hellyeah/56897c0b-302f-45cf-9dd5-07556b7a54dc
- Skills listed (inferred): PostgreSQL, MySQL, Redis, AWS, GCP, Azure, Kubernetes, Terraform, Airflow

## Pay and sponsorship

- Posted pay: not posted
- Market band for similar posted roles (SF Bay Area, n 114): p25 $189k, median $210k, p75 $230k

## Description (the employer's text)

### About Hellyeah AI

Hellyeah is the agentic operating system for distribution. AI agents plan, execute and optimize growth work, and humans approve it. A small engineering team runs several live products, with coding agents as part of how we ship.

### The role

You will own the platform our products and agents run on: the gateway every model call passes through, the runtime for our production agents, and the clusters, data stores, pipelines, secrets and release paths underneath.

We're hiring two engineers, one in San Francisco and one in Shanghai. One will lean toward the AI platform and the other toward the core platform. You'll share ownership and on-call, and work closely with our CTO.

This role is onsite five days a week. On-call includes nights and weekends, and days often run past 10 hours.

Why this role: You'll own the whole platform, work directly with our CTO, and build the agents that run it.

We run production AI across text, speech and video, mostly through third-party model APIs, with some self-hosted serving. The gateway supports internal teams, our products and customers. We do not train models. If you only want to work on model training, look elsewhere. If you want to make a multi-provider AI stack reliable, secure and affordable, keep reading.

Product teams own product features. IT support, marketing sites and SEO sit outside this role.

### What you'll do

The AI platform

Run the model gateway. Own routing, fallbacks, provider failover, rate limits and rollouts for 90+ model deployments across OpenAI, Anthropic, Azure, Google and AWS Bedrock. Benchmark new providers on latency, quality, cost and failure behavior before they take traffic, and escalate to vendors when they fall short.

Make the gateway multi-tenant. Give each team and customer the right keys, routes, limits and usage metering, and reconcile usage against provider invoices.

Run the AI developer platform. Own shared coding-agent access, including seats, quotas and per-user limits, plus the remote workspaces our engineers use. One heavy user should never slow down everyone else.

Run production agents safely. Own sandboxing, credential scoping and pinned releases for long-running agents on Kubernetes.

Automate your own job. Expect to build a lot of autonomous infra workflows and infra agents that take on routine requests and alerts, with a person approving risky actions.

Own infrastructure and AI spend. Reconcile provider bills against usage, tie spend to a team and product, and catch anomalies early. Right-size clusters, spend vendor credits before they expire, and handle quota and billing escalations with cloud and model vendors.

The core platform

Keep clusters and cloud healthy. Debug and upgrade EKS, AKS and bare-metal k3s through Argo CD and Kustomize. Manage AWS, Azure and GCP through reviewed Terraform.

Run the edge. Own Cloudflare across a dozen domains: DNS, WAF, TLS, CDN and object storage, plus GeoDNS, load balancers, egress IPs and email authentication.

Ship new services fast. Point a coding agent at an open-source repo and have it in production the same day: manifests or Helm, pinned images, Postgres and Redis, SSO, DNS, TLS, secrets and backups, all through GitOps. Make it highly available when it needs to be, and give each service a named owner. Build production infrastructure for new product launches the same way.

Hack your way to a solution. When something blocks you, read the source, patch it, work around it or build what's missing. You always have one more way to solve the problem.

Lead migrations. Move workloads between regions, clouds and platforms with a tested rollback, retire what's left behind, and bring stray services under GitOps.

Operate the data layer. Upgrade and migrate production PostgreSQL, MySQL, ClickHouse and Redis, run schema changes safely, and prove backups by restoring them.

Keep data pipelines flowing. Run Airbyte, Airflow, Dataform and CDC into BigQuery so product and finance data stay fresh, and catch a stalled sync before it fills a production disk.

---
Data: alder (https://alderhq.app). Cite https://alderhq.app/jobs/ashby%3Ahellyeah%3A56897c0b-302f-45cf-9dd5-07556b7a54dc and the date you read it. Observed facts come from the employer's own listing; location reach, level, family and skills are inferences.
