Senior AI Infrastructure Engineer

San Francisco, CA, US Senior AI/ML Engineer

Interested in this AI/ML Engineer role at Hellyeah AI?

Apply Now →

Skills & Technologies

AirbyteAnthropicAwsAzureBedrockGcpKubernetesOpenaiPython

About This Role

AI job market dashboard showing open roles by category

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.

Reliability and security

  • Own reliability. Set SLOs and alerts people trust, lead incidents across infrastructure and product services, including realtime speech, write the reviews, and automate the triage you keep repeating.
  • Own observability. Keep metrics, logs and traces flowing and usable across every cluster and the gateway. Maintain Grafana, Prometheus, Loki and Datadog, build on OpenTelemetry, add telemetry to new services, and manage retention and cost, so engineers and agents can see what's happening without asking you.
  • Own infrastructure security. Rotate credentials, replace static keys with workload identity, find exposed secrets and vulnerable dependencies, respond to exposures, and control access to customer data.
  • Make access self-serve. Replace manual grants with SSO, workload identity and scoped secrets, so engineers get what they need without asking you. Own the OAuth clients and API apps we run on ad and commerce platforms, including their reviews.

The team around you

  • Give product teams a paved road. Build the release pipelines, canaries, preview environments and guardrails that let them ship and operate their own services.
  • Review and teach. Review infrastructure changes from engineers, founders and their agents, and share the runbooks and agent skills that keep everyone fast.

Your first 90 days

  • Join on-call and run an incident review.
  • Take a new model from benchmark to production traffic.
  • Reconcile one month of gateway usage against provider invoices.
  • Cut manual access requests in half.
  • Put one recurring request or alert under agent handling, with a person approving risky actions.
  • Make sure a second person can run each critical system.

What you'll bring

  • 5+ years running production infrastructure, with real on-call experience
  • Deep Kubernetes debugging, including stateful workloads, and hands-on experience running Kubernetes on bare metal: storage, networking, upgrades and node failure
  • Hands-on work with LLM APIs in production: routing, rate limits, streaming, failure modes and cost
  • You've handed real operational work to agents or automation, with guardrails, approvals and recovery when a run dies
  • Enough Go or Python to read an unfamiliar codebase and ship a fix
  • Hands-on observability: you can maintain Grafana, Prometheus and OpenTelemetry collectors, write metric and log queries, and build a dashboard people use

You'll also need

  • GitOps and Terraform in production, ideally across more than one cloud
  • Networking fundamentals: DNS, TLS, load balancing, WAF and routing
  • You've taken a third-party service to production end to end, including SSO, backups and upgrades
  • You've led a region, cloud or database migration with a tested rollback
  • You've cut a real cloud or AI bill and can show the numbers
  • Security judgment: least privilege, secret handling, credential rotation, safe rollouts
  • Daily use of coding agents, plus clear views on what they should not touch unreviewed
  • You follow the current agent landscape, including Hermes Agent, OpenClaw, open-source Codex and Vercel's eve, and can explain agent harness best practices: durable runs, sandboxing, scoped credentials, human approval, memory, tracing and evals
  • The confidence to say no to a risky change and explain why, including to a founder
  • Written English for daily work with teammates in the US, China and India

Nice to have

  • LiteLLM or a similar LLM gateway
  • LLM serving, such as SGLang or vLLM
  • Multi-tenant API platforms, including metering and billing
  • Data pipelines, such as Airbyte, Airflow or CDC into BigQuery
  • Realtime audio or WebSocket services
  • Agent sandboxing, such as gVisor, Landlock or agent-sandbox
  • Langfuse or other LLM tracing
  • Remote dev environments, such as Coder
  • FinOps across several clouds
  • Mandarin

How we hire

A detailed application form, an online assessment, a technical interview, a 30-minute deep dive with our CTO on a project you've built, then a paid work trial before any offer. You'll see how we work and we'll see how you work.

Role Details

Company Hellyeah AI
Title Senior AI Infrastructure Engineer
Location San Francisco, CA, US
Category AI/ML Engineer
Experience Senior
Salary Not disclosed
Remote No

About This Role

AI/ML Engineers build and deploy machine learning models in production. They work across the full ML lifecycle: data pipelines, model training, evaluation, and serving infrastructure. The role has evolved significantly over the past two years. Where ML Engineers once spent most of their time on model architecture, the job now tilts heavily toward inference optimization, cost management, and integrating LLM capabilities into existing systems. Companies want engineers who can ship production systems, and the experimenter-only role is fading fast.

Day-to-day, you're writing training pipelines, debugging data quality issues, setting up evaluation frameworks, and figuring out why your model performs differently in staging than it did on your dev set. The best ML engineers are obsessive about reproducibility and measurement. They instrument everything. They know that a model is only as good as the data feeding it and the infrastructure serving it.

Across the 10,419 AI roles we're tracking, AI/ML Engineer positions make up 75% of the market. At Hellyeah AI, this role fits into their broader AI and engineering organization.

Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.

What the Work Looks Like

A typical week might include: debugging a data pipeline that's silently dropping 3% of training examples, running A/B tests on a new model version, writing documentation for a feature flag system that lets you roll back model deployments, and reviewing a junior engineer's PR for a new evaluation metric. Meetings tend to be cross-functional since ML touches product, engineering, and data teams.

Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.

Skills Required

Airbyte Anthropic (2% of roles) Aws (11% of roles) Azure (10% of roles) Bedrock (2% of roles) Gcp (7% of roles) Kubernetes (6% of roles) Openai (5% of roles) Python (23% of roles)

Python and PyTorch dominate the requirements. Most roles expect experience with cloud platforms (AWS, GCP, or Azure) and familiarity with ML frameworks like TensorFlow or JAX. RAG (Retrieval-Augmented Generation) has become a top-3 skill requirement as companies integrate LLMs into their products. Docker and Kubernetes show up in about a third of postings, reflecting the production focus of the role.

Beyond the core stack, employers increasingly want experience with experiment tracking tools (MLflow, Weights & Biases), feature stores, and vector databases. Fine-tuning experience is valuable but less common than you'd think from reading Twitter. Most production LLM work is RAG and prompt engineering, not fine-tuning. If you have both, you're in a strong position.

Companies that are serious about AI/ML hiring tend to post specific infrastructure details in the job description: the frameworks they use, their model serving stack, their data pipeline tools. Vague postings that just say 'ML experience required' without specifics are often companies that haven't figured out what they need yet.

Compensation Benchmarks

AI/ML Engineer roles pay a median of $213,800 based on 16,346 positions with disclosed compensation. Senior-level AI roles across all categories have a median of $230,000.

Across all AI roles, the market median is $214,834. Top-quartile compensation starts at $266,000. The 90th percentile reaches $321,730. For comparison, the highest-paying categories include AI Safety ($274,500) and Research Engineer ($252,000). By seniority level: Entry: $114,400; Mid: $193,200; Senior: $230,000; Director: $272,100; VP: $235,000.

Hellyeah AI AI Hiring

Hellyeah AI has 1 open AI role right now. They're hiring across AI/ML Engineer. Based in San Francisco, CA, US.

Location Context

AI roles in San Francisco pay a median of $261,300 across 3,262 tracked positions. That's 22% above the national median.

Career Path

Common paths into AI/ML Engineer roles include Data Scientist, Software Engineer, Research Engineer.

From here, career progression typically leads toward ML Architect, AI Engineering Manager, Principal ML Engineer.

The fastest path into ML engineering is through software engineering with a self-directed ML education. A CS degree helps, but production engineering skills matter more than academic credentials. Build something that works, deploy it, and measure it. That portfolio project is worth more than a Coursera certificate. For career growth, the fork comes around the senior level: go deep on technical complexity (staff/principal track) or move into managing ML teams.

What to Expect in Interviews

Expect system design questions around ML pipelines: how you'd build a training pipeline for a specific use case, handle data drift, or design A/B testing infrastructure for model deployments. Coding rounds typically involve Python, with emphasis on data manipulation (pandas, numpy) and algorithm implementation. Take-home assignments often ask you to build an end-to-end ML pipeline from raw data to deployed model.

When evaluating opportunities: Companies that are serious about AI/ML hiring tend to post specific infrastructure details in the job description: the frameworks they use, their model serving stack, their data pipeline tools. Vague postings that just say 'ML experience required' without specifics are often companies that haven't figured out what they need yet.

AI Hiring Overview

The AI job market has 10,419 open positions tracked in our dataset. By seniority: 117 entry-level, 4,975 mid-level, 3,840 senior, and 1,487 leadership roles (Director, VP, C-Level). Remote roles make up 6% of the market (580 positions). The remaining 9,776 roles require on-site or hybrid attendance.

The market median for AI roles is $214,834. Top-quartile compensation starts at $266,000. The 90th percentile reaches $321,730. Highest-paying categories: AI Safety ($274,500 median, 90 roles); Research Engineer ($252,000 median, 580 roles); AI Engineering Manager ($250,811 median, 72 roles).

Demand for AI/ML Engineers has been strong and consistent. Unlike some AI roles that spike with hype cycles, ML engineering is a foundational need. Every company deploying AI models needs people who can keep them running, and the gap between research prototypes and production systems keeps growing.

The AI Job Market Today

The AI job market spans 10,419 open positions across 16 role categories. The largest categories by volume: AI/ML Engineer (7,849), AI Product Manager (516), AI Software Engineer (513). These three account for the majority of open positions, though smaller categories often have higher per-role compensation because of specialized skill requirements.

The seniority mix tells a story about where AI teams are in their maturity. Entry-level roles (117) are outnumbered by mid-level (4,975) and senior (3,840) positions, reflecting that most companies are past the 'build a team from scratch' phase and need experienced engineers who can ship production systems. Leadership roles (Director, VP, C-Level) total 1,487 positions, representing the bottleneck between technical execution and organizational strategy.

Remote work availability sits at 6% of all AI roles (580 positions), with 9,776 requiring on-site or hybrid attendance. The remote share has stabilized after the post-pandemic correction. Senior and specialized roles (Research Scientist, ML Architect) are more likely to be remote-eligible than entry-level positions, partly because experienced hires have more negotiating power and partly because these roles require less hands-on mentorship.

AI compensation is structured in clear tiers. The market median sits at $214,834. Top-quartile roles start at $266,000, and the 90th percentile reaches $321,730. These figures include base salary with disclosed compensation. Total compensation (including equity, bonuses, and sign-on) runs 20-40% higher at companies that offer those components.

Category matters for compensation. AI Safety roles lead at $274,500 median, while Prompt Engineer roles sit at $140,000. The spread between highest and lowest-paying categories reflects the premium on specialized technical skills versus broader analytical roles.

The most in-demand skills across all AI postings: Python (2,350 postings), Aws (1,173 postings), Azure (1,030 postings), Rag (986 postings), Gcp (714 postings), Pytorch (649 postings), Kubernetes (583 postings), Claude (581 postings). Python dominates, appearing in the vast majority of role descriptions regardless of category. Cloud platform experience (AWS, GCP, Azure) is the second most common requirement. The newer entrants to the top skills list (RAG, vector databases, LLM APIs) reflect the shift from traditional ML toward generative AI applications.

Frequently Asked Questions

Based on 16,346 roles with disclosed compensation, the median salary for AI/ML Engineer positions is $213,800. Actual compensation varies by seniority, location, and company stage.
Python and PyTorch dominate the requirements. Most roles expect experience with cloud platforms (AWS, GCP, or Azure) and familiarity with ML frameworks like TensorFlow or JAX. RAG (Retrieval-Augmented Generation) has become a top-3 skill requirement as companies integrate LLMs into their products. Docker and Kubernetes show up in about a third of postings, reflecting the production focus of the role.
About 6% of the 10,419 AI roles we track offer remote work. Remote availability varies by company and seniority level, with senior and leadership roles more likely to offer location flexibility.
Hellyeah AI is among the companies actively hiring for AI and ML talent. Check our company profiles for detailed breakdowns of open roles, salary ranges, and hiring trends.
Common next steps from AI/ML Engineer positions include ML Architect, AI Engineering Manager, Principal ML Engineer. Progression depends on whether you lean toward technical depth, people management, or product strategy.

Get Weekly AI Career Intelligence

Salary data, skills demand, and market signals from 16,000+ AI job postings. Every Monday.