Vibe Coding Engineer - Integration & API Architecture

• Own the API and integration intake pipeline, ensuring consistent intake, triage, and execution across workstreams • Define and enforce API contract standards (REST and event-driven) and govern integration patterns enterprise-wide • Design and implement secure boundary controls, including tokenization of NPI/PII to prevent sensitive data exposure in lower environments • Establish and operationalize scalable integration patterns, including synchronous and event-driven architectures • Configure and manage our API gateway (Gravitee) and iPaaS/orchestration platform (Workato); experience with comparable platforms (Apigee, MuleSoft) is relevant • Design and support event streaming pipelines on AWS MSK/Kafka, and contribute to workflow orchestration patterns using Temporal or comparable durable-execution frameworks • Ensure API and integration contracts align to the enterprise canonical data model, working in partnership with data architecture • Act as a hands-on technical leader, bringing implementation experience and pragmatic decision-making to unblock teams Profile :- • Proven experience designing and implementing API ecosystems and integration architectures at scale • Deep understanding of API contract design (REST, AsyncAPI) and governance models • 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 • Expertise in modern authentication/authorization (OAuth2, OpenID Connect) • Experience implementing data protection controls such as tokenization (Protegrity, TokenEx, or equivalent) • Strong grounding in event-driven architecture, including hands-on experience with Kafka or AWS MSK • Experience with durable workflow orchestration (Temporal or similar) is a plus • Experience defining or consuming canonical/logical data models for contract design (e.g., enterprise data modeling, master data management) is a plus • Familiarity with AI agent orchestration patterns (e.g., LangGraph, agentic workflows) is a plus, though not a core requirement • Comfortable operating in ambiguity with minimal oversight; able to establish structure where none exists • Brings real-world implementation experience and practical lessons learned from prior deployments.