AI Agent Infrastructure Lead

The Role

Sphere is looking for an engineer to lead our internal AI agent enablement efforts. You’ll build the systems that let AI agents safely and effectively increase velocity across. Sphere, starting with engineering and expanding into ops, customer success, tax research, and implementation workflows.

What You'll Do

Within days

• Ship AI agent features that help Sphere’s engineering team use agents more effectively and responsibly.
• Iterate on versions of Sphere’s agent sandbox environments.
• Create workflows where agents can inspect the codebase, run local infrastructure, make changes, run tests, and prepare work for human review.
• Work directly with engineers to identify high-leverage internal workflows where agents can create immediate velocity.

Within months

• Lead Sphere’s internal efforts to enable AI agents to act more autonomously across engineering, ops, customer success, tax research, and implementation.
• Build “Goose” for Sphere: the internal AI agent layer that helps agents understand and operate across Sphere’s systems.
• Own the infrastructure, tooling, and workflows that let agents safely take on more complex internal work over time.
• Establish the patterns for how Sphere uses agents internally, including context, permissions, review, observability, and escalation.

Requirements

• Experience building production-quality software.
• Experience in AI agents, coding agents, internal developer tooling, or AI agent enablement.
• Comfort working across backend systems, infrastructure, local development environments, CI, and internal tools.
• Strong judgment around autonomy, safety, permissions, and human review.
• High agency. You can take a vague internal problem and turn it into a working system people actually use.
• Strong attention to detail. Agents are only useful here if they improve speed without reducing correctness.

Who You Are

You'll thrive here if

• You're a Dog. You've been underestimated, gone through struggle, and never stopped running. You have a chip on your shoulder and enormous drive. You look at Stripe, Deel, and Flexport all punting on compliance and think: good, that means the opportunity is ours. Hunger beats pedigree.
• Early stage is in your bones. You've built things where there's no playbook and nobody handing you the answer. You define the problem instead of waiting for instructions.
• You own it end to end. Give you a goal and you figure out your own path. Small team, global surface area - everyone owns a domain that would be a full team at a larger company. No one tells you how.
• You believe speed and accuracy are both possible. We're building a complex product that requires robustness and 100% uptime, and we have to build at our customers' pace. Move fast. Don't break things. Both.
• Being in the room is a feature, not a cost. Being in SF isn't a policy, it's how the work gets done. The speed and density of collaboration we need doesn't survive over video.

This won't be a fit if

• You need structure handed to you or ambiguity feels draining rather than motivating
• You want to manage people more than own hard problems (we're a flat, experienced team - everyone builds)
• You're used to "good enough" shipping (small errors have outsized impact here)