What the team does

Before a merchant can send a single message, someone has to subscribe. That's the Subscriptions team's domain. They own the full opt-in tooling at Recart: the popup editor, the rendering engine that shows popups on merchant storefronts, the targeting and trigger logic, A/B testing, and the session and user tracking infrastructure underneath it all.

Their work is highly visible. It runs directly on merchant websites, in front of real users, at scale. A bug here doesn't just affect a dashboard; it affects live storefronts. That reality shapes how they build.

Beyond the core popup engine, the team is actively investing in the next generation of the editor: a modular, component-based design system that makes popups more flexible, more powerful, and easier to build. They're also building one of Recart's most strategically significant features: the Recart Audience Network. A cross-store identification layer that recognizes returning shoppers across all Recart merchants. When a visitor has previously opted in through any Recart popup, they can be identified and served a OneClick popup on their next visit, no re-entry needed. Early results show nearly 3x conversion rate uplift. The network already has 500K+ members and grows with every opt-in across the merchant base. The Subscriptions team owns the infrastructure behind it.

What they work on

• Popup editor - create visually stunning popups that collects user data and consent for marketing messaging
• A/B testing - popup variant testing, holdout groups, and the stats/export infrastructure behind them
• Targeting & trigger logic - welcome, exit, welcome, these are just a few of the many options we need to support to show the popup to the right users at the right time
• User tracking - track various user behaviour to identify shopping intent and nudge them to become a customer
• Audience network - building our own user network to enable features that can work across our customers

Tech they work with

• Frontend: TypeScript, React, Preact
• Backend: Node.js, TypeScript
• Database: MongoDB, DynamoDB
• Design: Figma
• Tooling: Shortcut, LaunchDarkly, GitHub, DataDog

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, and on-call rotations mean someone's always got the weekend covered.

What kind of problems they solve

"A merchant wants to add animations to their popup to boost conversion rate. Is it worth it?"

(Spoiler: probably not, and you'll need the data to back that up.)

"How do we prove to merchants that popups are actually driving revenue, not just opt-ins? Design the metrics framework that makes the case. Revenue attribution above all."

"A merchant is complaining about slow popup load times on their storefront. Walk through the possible causes, isolate the root, and fix it without touching their theme."

"Goose Creek needs an accessibility-compliant popup. Keyboard navigation, screen reader support, ADA requirements. Figure out what that means for our editor."

Who thrives here

You'll do well here if you enjoy working at the intersection of product and infrastructure. The Subscriptions team isn't just building features, they're maintaining a rendering engine that runs on thousands of live storefronts simultaneously. You'll need to care about correctness, performance, and the end-user experience in equal measure.

The team moves between deep technical work (user tracking, performant popups with detailed metrics) and very product-facing challenges (satisfying our merchant’s wildest dreams). If that range sounds appealing, this is your team.

Size & structure

6 engineers, a Team Lead + 1 Designer, working closely with the Head of Product.