•Pod delivery — Own end-to-end delivery for the orchestration pod: planning, execution, quality, and shipping on time.
•Workflow orchestration — Design and build durable, long-running workflows on Temporal in Node.js/TypeScript that model the member action lifecycle, state transitions, scheduling, activation, and delivery outcomes.
•Action delivery architecture — Own the end-to-end action delivery pipeline from decision publication through activation, delivery acknowledgment, and state reconciliation. Design and implement Transactional Outbox patterns, atomic persist-and-publish workflows, idempotency controls, retry/backoff mechanisms, dead-letter queue handling, and delivery receipt processing.
•Activation integrations — Own the components that activate decisions to Adobe Experience Platform (AEP) and publish through Kafka output patterns to downstream channels. Define delivery contracts, activation guarantees, and receipt ingestion patterns that ensure reliable action execution.
•Hands-on development — Contribute code alongside the team, including Temporal workflows and activities, Node.js services, Kafka producers and consumers, outbox processors, and integration services.
•Technical decisions — Make the day-to-day architecture decisions for the pod, including workflow design, state machine modeling, retry and compensation strategies, idempotency, topic strategy, schema evolution, delivery guarantees, and API contracts.
•Distributed systems reliability — Engineer for correctness in a highly asynchronous environment. Ensure exactly-once business intent through idempotent consumers, deduplication strategies, durable state management, safe retries, and graceful failure handling.
•Observability and operations — Establish monitoring, tracing, alerting, and operational visibility across workflow execution, event publication, activation processing, and delivery acknowledgment pipelines.
•Team leadership — Manage and mentor engineers and contractors; run code reviews, uphold engineering standards, and keep the team unblocked and moving.
•Cross-team coordination — Coordinate interfaces with decisioning, the Action Library, activation systems, and the platform team; surface dependencies, integration risks, and operational concerns early.