Senior Integration Engineer – WooCommerce + Telehealth Platform + Customer.io Event Pipeline (HIPAA)

Less than 1 month, Less than 30 hrs/week We're U.S. telehealth company selling subscription treatments. We need a senior engineer to design and build the real-time data pipeline that powers every lifecycle email we send. We need someone who can start this week. THE PROBLEM Our customer journey spans two systems: 1. WooCommerce + WooCommerce Subscriptions (checkout, orders, renewals; we use custom billing intervals via our own plugin) 2. A backend telehealth partner platform that handles intake questionnaires, provider review, prescriptions, pharmacy routing, and shipping/tracking. It exposes a REST API and HMAC-signed webhooks (~55 event types across order, prescription, pharmacy, shipping, payment, subscription, messaging, lab, and support events). Today, Customer.io only sees a fraction of this. We need every meaningful change from both systems flowing into Customer.io in near real time, attached to the correct person, so we can send accurate emails: intake reminders, approval, shipped (with tracking), delivered, renewal upcoming, payment failed, win-back, and more. WHAT YOU'LL BUILD - A lightweight middleware "event hub" (serverless or small service, your recommendation) that receives webhooks, acknowledges fast, queues, dedupes, resolves identity, and sends clean events/attributes/objects to the Customer.io Pipelines API - A small WordPress/WooCommerce plugin that emits order, customer, and subscription changes asynchronously (Action Scheduler), plus reconciliation via the Woo REST API - Partner webhook ingestion with signature verification, idempotency, out-of-order handling, and API hydration (the partner's webhooks are notification-style and intentionally exclude PII, so identity must be joined via IDs) - A Customer.io data model: person attributes, subscription/order objects, and a documented event catalog (tracking plan) - Historical backfill of existing customers and subscriptions - Dead-letter queue, replay, nightly reconciliation, alerting, and a simple monitoring view - Config-driven mappings so we can add events, products, or a new partner later without a rebuild - Handoff: repo, architecture doc, runbook, tracking plan, and a recorded walkthrough REQUIREMENTS - Proven production experience with Customer.io (Pipelines/Track API, objects, relationships) or a comparable platform (Braze, Iterable, Klaviyo) plus Customer.io familiarity - Deep WooCommerce experience, including WooCommerce Subscriptions hooks and the REST API - You've built inbound webhook systems that handle retries, duplicates, and out-of-order delivery at scale - Strong Node.js/TypeScript or Python; comfortable with AWS or GCP (queues, serverless, Postgres/DynamoDB) - Healthcare/HIPAA experience: data minimization, BAA-covered infrastructure, keeping PHI out of marketing tools - Clear written communication; you'll document everything NICE TO HAVE - Prior work with telehealth/pharmacy platforms or e-prescribing workflows - Segment, RudderStack, or Customer.io Data Pipelines experience - Experience migrating cart recovery from Metorik or similar into an ESP TIMELINE & STRUCTURE - Paid, fixed-price milestones: (1) discovery + tracking plan + architecture, (2) foundation + WooCommerce, (3) partner integration, (4) backfill, reconciliation, launch - NDA and confidentiality/BAA terms required before sandbox access - Strong potential for an ongoing retainer as we expand HOW TO APPLY (proposals that skip these won't be reviewed) Start your proposal with the word "Pipeline." 1. Link or describe 2 comparable integrations you've shipped (ideally one WooCommerce → ESP and one inbound-webhook system). Redacted diagrams, repos, or runbooks are great. 2. In a few sentences: a shipping-tracking webhook arrives BEFORE the "sent to pharmacy" webhook for the same order, and some events arrive twice. What does your system do? 3. The partner's webhook payloads don't include the customer's email. How do you attach events to the right Customer.io profile? 4. What would you never send to Customer.io from a telehealth business, and how would you enforce that in code? 5. Your recommended hosting/stack for this, and why. 6. Your availability this week and your estimate for Milestone 1. 7. Estimated fixed cost and timeframe to acoomplish this 8. If you have other ideas, thoughts, or experiences that might lends to a better solution