What the team does

E-commerce brands don't run on a single tool. They run on Klaviyo, Postscript, Attentive, Iterable, LoyaltyLion, Typeform, Loop... and Recart sits at the center of it all. The Integrations team makes that work.

They design, build, and maintain the integrations that connect subscriber data, opt-in events, discount codes, and customer profiles across platforms. When a shopper signs up via a Recart popup and instantly receives a Klaviyo welcome email with a unique discount code, that's the Integrations team's work.

Beyond integrations, they own segmentation. The infrastructure that determines which subscribers receive which messages, powered by SingleStore, a distributed SQL engine built for real-time workloads.

What they work on

• Integration ecosystem - Klaviyo, Postscript, Attentive, Iterable, LoyaltyLion, Loop, Typeform, Shopify-native APIs
• -—Shopify Data Integration - ensuring correctness and consistency across customers, orders, products, and all shared entities between Shopify and Recart
• Segmentation infrastructure - S2 (SingleStore)-based segment membership, real-time condition evaluation, and segment lifecycle management
• Subscriber data integrity - timezone accuracy, opt-in compliance (CTIA/TCPA), and data backfills
• Compliance tooling - known litigator filtering, checkout subscription compliance, and subscriber data audit trails

Tech they work with

• Frontend: React
• Backend: Node.js, TypeScript, Go (microservices architecture)
• Databases: MongoDB, DynamoDB, SingleStore (S2)
• Infrastructure: AWS, Kubernetes, Datadog, PagerDuty
• Tooling: Shortcut, LaunchDarkly, GitHub

How our engineering teams work

On any given day, our engineers are fielding questions from CS, syncing with Product, and reviewing each other's scopes on Notion before a single line of code is written. We do standups, run design reviews, and write internal docs when something new gets built, so knowledge doesn't live only in Slack threads.We move fast, but we're deliberate: new features go through feature flags, changes are scoped before they're picked up.

What kind of problems they solve

“MongoDB can't keep up with real-time segmentation at our current scale. Plan and execute the migration to a OLAP database.” "Klaviyo stopped counting new vs. returning profiles. Figure out why." "This merchant's quiz captures phone numbers via Typeform — can we wire that into our opt-in flow?" "Our Postscript integration uses deprecated auth that expires in 2027. Plan the migration now."

The problems are real, they come from real merchants, and the Integrations team is the last line of defense before they escalate.

Who thrives here

You'll do well on this team if you like owning a domain end-to-end. From scoping a technical solution on Notion to deploying it and monitoring it in Datadog. The work is varied: some days it's a deep architectural decision about SingleStore projections, other days it's debugging why a Klaviyo segment sync is off by one record.

You'll work closely with the broader engineering org, Product, and CS. Being a clear communicator matters as much as being a strong engineer.

Size & structure

~4-5 engineers, working closely with the Head of Product and CTO.