Job description

The role You will own the paved road: the scaffolding, tooling, isolation model, and release machinery that lets engineers ship compliant agent workflows in a day instead of weeks — and, before long, let a customer's own engineers do it without us in the room. You will lead a small, high caliber and capable team. A meaningful part of this job is establishing the engineering standards. What you'll own The golden path. Scaffolding, templates, and defaults so a new solution stands up with backend, ingest, RBAC, and audit packaging already handled — and the engineers write only agent logic. The shared tool catalog. Today every agent intent re-authors its own tool definitions. Make tools first-class, versioned, referenced objects rather than copy-paste. Versioning and promotion lanes. Agents and playbooks move local → shared → production through auditable, gated CI/CD. No silent edits to anything shared. The compliance harness. Provable auditability and governance for every agent run: who changed what, which version executed, which sources grounded which claim. Testing infrastructure. A skill and tool testing suite, regression gates, and shadow A/B in production environments. Multi-tenancy done properly. Logical isolation across the control, data, execution, and playbook planes — strong enough that a customer's security review passes without us resorting to dedicated per-tenant infrastructure. The customer-facing developer experience. SDK, API gateway, sandboxed evaluation, trace-level debugging, and egress webhooks that a bank's own quant engineers can safely build against. A repeatable vendoring cycle. We ship sanitized codebases into customer environments today. Make that a supported, IP-defensible process. Engineering standards that stick. Written specs, clear approval rights, real separation of concerns, and a team that knows the difference between deliberate technical debt and accidental technical debt. What we're looking for You have built and operated a multi-tenant platform that external developers built on — SDK or API surface, tenant isolation, gated deploys, the whole path. You have shipped in a regulated environment and can hold your own on SOC 2, audit trails, access control, and model risk without treating them as someone else's problem. You have converted services delivery into product before. You know which bespoke work becomes a platform primitive and which is a one-off you should refuse to generalize. You have led engineers directly, including engineers earlier in their careers, and you set standards by writing things down rather than by being in every conversation. You are opinionated about developer experience and can defend those opinions with what happened last time. Signals we weight heavily Internal developer platform, paved road, or platform-as-a-service ownership at a company that sold to enterprises. You have said no to a customer request in order to protect a platform abstraction — and can explain how you made that call. You have introduced written decision-making to a team that ran on hallway conversation, and it survived contact. Comfort with AI agent systems is welcome but not required.

Requirements

Must-haves

You will lead a small, high caliber and capable team.
A meaningful part of this job is establishing the engineering standards.
What you'll own
The golden path. Scaffolding, templates, and defaults so a new solution stands up with backend, ingest, RBAC, and audit packaging already handled — and the engineers write only agent logic.
The shared tool catalog. Today every agent intent re-authors its own tool definitions. Make tools first-class, versioned, referenced objects rather than copy-paste.
Versioning and promotion lanes. Agents and playbooks move local → shared → production through auditable, gated CI/CD. No silent edits to anything shared.
The compliance harness. Provable auditability and governance for every agent run: who changed what, which version executed, which sources grounded which claim.
Testing infrastructure. A skill and tool testing suite, regression gates, and shadow A/B in production environments.
The customer-facing developer experience. SDK, API gateway, sandboxed evaluation, trace-level debugging, and egress webhooks that a bank's own quant engineers can safely build against.
A repeatable vendoring cycle. We ship sanitized codebases into customer environments today. Make that a supported, IP-defensible process.
Engineering standards that stick. Written specs, clear approval rights, real separation of concerns, and a team that knows the difference between deliberate technical debt and accidental technical debt.
You have built and operated a multi-tenant platform that external developers built on — SDK or API surface, tenant isolation, gated deploys, the whole path.
You have shipped in a regulated environment and can hold your own on SOC 2, audit trails, access control, and model risk without treating them as someone else's problem.
You have converted services delivery into product before. You know which bespoke work becomes a platform primitive and which is a one-off you should refuse to generalize.
You have led engineers directly, including engineers earlier in their careers, and you set standards by writing things down rather than by being in every conversation.
You are opinionated about developer experience and can defend those opinions with what happened last time.
Signals we weight heavily
Internal developer platform, paved road, or platform-as-a-service ownership at a company that sold to enterprises.
You have said no to a customer request in order to protect a platform abstraction — and can explain how you made that call.
You have introduced written decision-making to a team that ran on hallway conversation, and it survived contact.
Comfort with AI agent systems is welcome but not required.

Nice-to-haves

None flagged.

Application prep

Use the role’s language and application details while tailoring your materials.

Keywords to mirror

ci/cdapiai

Platform: gem
Effort: medium

Benefits

Benefits detected in the listing.

Dental