About the role
You make Private Agent One work with other agents and tools while keeping the user's authority intact. Everything on the other side of these connections is controlled by somebody else, changes without warning, and fails partially, so the interesting engineering is in the failure handling rather than the happy path.
The work
Implement versioned MCP and A2A integrations alongside ordinary APIs. Build discovery, capability negotiation, authentication, task status and error handling. Maintain conformance tests and a support matrix; a protocol handshake must never be treated as blanket permission.
What good looks like
In your first 90 days, demonstrate a local tool, an external service and an independent remote agent working through explicit permissions and cancellation.
Evidence we look for
Bring protocol, API or distributed application engineering experience. Show how you handle version changes, partial failure and systems controlled by other organizations.
What we need to see
- Protocol, API, or distributed application engineering
- You handle version changes and partial failure deliberately, with examples
- You design against systems controlled by other organisations without trusting them
- You test interoperability rather than assuming it from a specification
Nice to have
- MCP, A2A, or comparable agent interoperability rails
- You have written or implemented a public specification
- Contract or conformance testing
The exercise
Design an adapter for a remote agent that supports task creation but cannot guarantee cancellation after execution begins.
Where and how we work
In the office together five days a week, in any of these cities. Remote-friendly around your family, arranged one person at a time.