Platform Engineer, AI Agent Systems

Role Overview

Title:

Platform Engineer, AI Agent Systems

Hours:

Full-time;
Salaried

Location:

Salt Lake City, UT (hybrid in-office)

Benefits Eligible:
Yes

Manager:
Justin Hanselman

Geothermal energy is the most abundant renewable energy source in the world. There is 2,300 times more energy in geothermal heat in the ground than in oil, gas, coal, and methane combined. However, historically it’s been hard to find and expensive to develop. At Zanskar, we’re using better technology to find and develop new geothermal resources in order to make geothermal a cheap and vital contributor to a carbon-free electrical grid.

Zanskar uses proprietary geophysical models and subsurface data to find geothermal resources faster than anyone else. We’re building the infrastructure that lets our team put AI agents to work on that data — safely. We need a Platform Engineer to own that infrastructure: the systems that let agents operate on sensitive company data and models without creating pathways for that data to be deleted, altered, or exfiltrated.

The work isn’t theoretical — we have proprietary subsurface models and geophysical datasets that cannot leave our environment, and we need agents that can work with them in production today.

Success in this role centers on two tightly related work streams that share the same hard underlying problem: letting agents operate on sensitive company data and models safely. You'll design and operate the production systems that run agentic workflows inside our infrastructure as well as support a self-service layer for our internal teams to deploy agent-based tools and agent-built internal apps.

You'll own the access control architecture that governs what agents can read, write, and call in both production and sandboxed experiments — explicit trust boundaries, revocable credentials, and audit trails that hold up under scrutiny. Throughout, you'll partner directly with scientists, engineers, finance, legal, and comms to understand what they need, what they'll accidentally break, and how to make the on-ramp fast without compromising the guardrails.

Within six months, you'll have foundational agent-deployment infrastructure running in production, a sandbox environment that internal teams are actively using to build tools, and an access-control and observability model that lets Zanskar expand agent usage safely as the company grows.

• A Platform Engineer First: You have 3+ years building and operating internal APIs, platform services, or backend infrastructure. You reach for containerized environments naturally, think in terms of service-to-service auth and secrets management, and you know what observability actually requires — not just that it’s important.

• Fluent in How Agents Fail: You have worked with LLM tool-use or function-calling in a production or near-production context. You understand hallucinated tool calls, unbounded loops, and context bleed — not just as concepts, but as things you’ve had to diagnose and contain. You have hands-on experience with at least one agentic framework and its operational tradeoffs.

• Security-Minded by Default: You don’t treat access controls as a bolt-on. You design systems where the path of least resistance is also the safe path. You’ve thought about what happens when a component is compromised, not just when it works correctly.

• Comfortable With Unsolved Problems: There is no playbook for safely deploying proprietary AI agents at the speed a small technical team needs. You’re the kind of engineer who figures out the right approach rather than waiting for one to arrive. You do your best work when the problem is real and the constraints are hard.

• Experience with multi-tenant systems where isolation between environments is a hard requirement, not a best-effort.

• Familiarity with model serving infrastructure and the patterns that apply when the model itself is proprietary.

• Experience with data access patterns in scientific or geospatial contexts — raster/vector data, large file stores, or similar environments where data sensitivity and file size…