Senior Engineer Integration and API Architecture

We are seeking a senior staff-level engineer to lead integration architecture and API enablement across multiple workstreams. This role is best suited for someone comfortable operating with high autonomy, navigating ambiguity, and independently figuring things out in a fast-evolving environment.

Key Responsibilities

1. Own the API and integration intake pipeline, ensuring consistent intake, triage, and execution across workstreams
2. Define and enforce API contract standards (REST and event-driven) and govern integration patterns enterprise-wide
3. Design and implement secure boundary controls, including tokenization of NPI/PII to prevent sensitive data exposure in lower environments
4. Establish and operationalize scalable integration patterns, including synchronous and event-driven architectures
5. Configure and manage our API gateway (Gravitee) and iPaaS/orchestration platform (Workato); experience with comparable platforms (Apigee, MuleSoft) is relevant
6. Design and support event streaming pipelines on AWS MSK/Kafka, and contribute to workflow orchestration patterns using Temporal or comparable durable-execution frameworks
7. Ensure API and integration contracts align to the enterprise canonical data model, working in partnership with data architecture
8. Act as a hands-on technical leader, bringing implementation experience and pragmatic decision-making to unblock teams

Profile

1. Proven experience designing and implementing API ecosystems and integration architectures at scale
2. Deep understanding of API contract design (REST, AsyncAPI) and governance models
3. Strong experience with API gateways (policies, rate limiting, access control) and orchestration/iPaaS platforms (workflow/recipe-based integration); Gravitee and Workato experience a strong plus
4. Expertise in modern authentication/authorization (OAuth2, OpenID Connect)
5. Experience implementing data protection controls such as tokenization (Protegrity, TokenEx, or equivalent)
6. Strong grounding in event-driven architecture, including hands-on experience with Kafka or AWS MSK
7. Experience with durable workflow orchestration (Temporal or similar) is a plus
8. Experience defining or consuming canonical/logical data models for contract design (e.g., enterprise data modeling, master data management) is a plus
9. Familiarity with AI agent orchestration patterns (e.g., LangGraph, agentic workflows) is a plus, though not a core requirement
10. Comfortable operating in ambiguity with minimal oversight; able to establish structure where none exists
11. Brings real-world implementation experience and practical lessons learned from prior deployments