# AI Infrastructure Engineer at PlayerZero > Hybrid · United States · Unspecified · DevOps / SRE / Infra · open. Source: https://alderhq.app/jobs/ashby%3APlayerZero%3A388aec5c-6b3b-43d9-9bf0-0eb98d78f3da (read 2026-11-10). ## Facts (observed) - Company: [PlayerZero](https://alderhq.app/companies/playerzero) - Location text: San Francisco - Where it can be done from (inferred): Hybrid · United States (evidence: "Location: San Francisco") - Posted: 2026-10-22 (19 days ago) - First seen by alder: 2026-11-07 · last verified: 2026-11-08 - Reposted: 0 times · edited: 0 times - Apply on the employer's site: https://jobs.ashbyhq.com/playerzero/388aec5c-6b3b-43d9-9bf0-0eb98d78f3da ## Pay and sponsorship - Posted pay: $150k–$210k per year (from the listing's pay field) - Market band for similar posted roles (SF Bay Area, n 181): p25 $200k, median $238k, p75 $300k ## Description (the employer's text) ### What is PlayerZero? Building great software takes more than writing code. It takes teams working together, and too often, the information they need is scattered across tools, conversations, and systems. PlayerZero is an AI platform that connects work across enterprise Support, Engineering, Product, QA, and SRE teams, helping them resolve issues faster, improve software quality, and plan what to build next. At its core is our Engineering World Model: a living understanding of a company’s software, how it runs, and the people and decisions behind it. By connecting codebases, tickets, production telemetry, and the conversations that shape the work, our model links what software is intended to do with how it actually behaves in production—and learns from where the two diverge. Our agents (we call them Players :) use that context to take on work across the software lifecycle. They learn from each outcome, earning trust and taking on more responsibility over time. We’re building a future where AI plays an active role in how teams plan, build, and run software. We’re looking for people across disciplines to help shape it. ### About the AI Infra team Most AI tools help one person perform a task faster, a session at a time. But real software work doesn’t happen in one session or one tool. A bug moves from a customer to a ticket to a Slack thread to a PR to a deploy, across people and systems that never see the whole picture. The most interesting context lives between those systems of record, and so does the real work. For our agents to take on that work, something has to sit in between. The AI Infrastructure team builds it: where agents execute, what context they access, and how work moves between agents and people. Because the work runs through this infrastructure, it’s also what lets the Engineering World Model learn from every outcome and earn our agents the right to do more. It has to be fast, composable, and built to scale. We’re hiring infrastructure engineers who like hard distributed-systems problems and want to own them end to end. ### What you will do Build agentic infrastructure. Our agents don’t answer a question and disappear. They take on units of work that run for hours or days, change hands, and keep driving toward completion. You’ll build the runtime that creates continuity for that work: long-running sessions that survive failures, durable workflow state, lifecycle and cancellation, and workflows that track each piece of work across every stage and every party involved. Architect how context is represented and delivered. Because work flows through our platform, we’re present when the connections between code, tickets, units of work, and past decisions are made. The context between these systems of record is necessary for agents to do their work well, and the data models behind it shape everything an agent can know. You’ll design how that context is represented and delivered: what gets precomputed ahead of time versus resolved on demand, and how the right slice reaches each agent at the right moment. Build the communication layer. Real work doesn’t happen in isolation. Agents work alongside other agents (subagents, teammates, agents on customer machines, agents over MCP) and alongside people. You’ll build the layer that connects them: messaging between agents within and across sessions, escalations that pull in the right person at the right time, and agents that can be interrupted when new information arrives. Scale sandboxes and fleets. An organization’s work is spread across laptops, QA fleets, production hosts, and ephemeral scripts. You’ll build our own sandbox infrastructure, environments that spin up instantly and run by the hundreds, and the fleet layer that lets agents work on the machines where customer work already happens. You don’t need experience in all of these. We expect you to go deep on one or two and pick up the rest along the way. ### What you bring A builder mindset. You own projects end to end, think carefully about data models, performance, and maintainability, and have taken prototypes to production with a clear sense of the reliability and scale tradeoffs. --- Data: alder (https://alderhq.app). Cite https://alderhq.app/jobs/ashby%3APlayerZero%3A388aec5c-6b3b-43d9-9bf0-0eb98d78f3da and the date you read it. Observed facts come from the employer's own listing; location reach, level, family and skills are inferences.