About the role
You connect a person's agent to the services that already run their life and business: the bank, the calendar, the practice-management system, the thing the accountant insists on. Making an ordinary workflow dependable across interfaces that were never designed for this is the work, and it is mostly about failure handling rather than the first successful call. Depth matters far more here than familiarity with every format.
The work
Build integrations for communications, calendars, commerce and business systems using supported APIs, webhooks and event streams. Handle OAuth, quotas, schema changes and duplicate events. Use narrowly scoped browser automation only where authorized and appropriate.
What good looks like
In your first 90 days, deliver one complete workflow across two selected services with retries, reconciliation and an understandable audit trail.
Evidence we look for
Bring strong application integration experience. Relevant work may involve REST, GraphQL, gRPC, SOAP, SQL, messaging or enterprise integration tools; depth matters more than knowing every format.
What we need to see
- Strong application integration experience, with production systems behind it
- Depth in some of REST, GraphQL, gRPC, SOAP, SQL, messaging, or enterprise integration tooling
- You make an unreliable interface reliable through retries, idempotency, and reconciliation
- You leave integrations somebody else can operate
Nice to have
- Legacy enterprise systems specifically
- Event-driven architecture
- You have integrated something with no usable documentation
The exercise
Design a booking flow where one service succeeds and another fails, without misleading the user about the final state.
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.