What the team does

When a Recart merchant launches a Black Friday campaign to 300,000 subscribers, or when an abandoned cart triggers a personalized SMS with a unique discount code, that's the Messaging team's work. They own the full lifecycle of message delivery: how campaigns are built, scheduled, sent, and measured; how automated flows are triggered and personalized; and how merchants are billed for it all.

They also handle the unsexy-but-critical parts: compliance with quiet hours and TCPA regulations, toll-free number (TFN) verification, STOP/unsubscribe handling, and making sure no campaign gets stuck in a processing queue at 3am the night before a Super Bowl promotion.

‍

What they work on

• Campaign infrastructure - scheduling, concurrent sending, traffic shaping (MPS management across parallel campaigns), and campaign A/B testing (Multi-Arm Bandit)
• Automated flows - the engine that powers abandoned cart, welcome, post-purchase, and custom trigger flows, including unique expiring discount codes in automations
• Discount code system - unique expiring codes, general discount codes, Shopify sync, and lifecycle management
• Billing - SMS credit management, overage invoicing, credit adjustments, and Stripe webhook infrastructure
• Phone number & compliance - TFN verification, Twilio number management, timezone accuracy for quiet hours, STOP keyword handling, litigation support tooling
• URL shortener - hash generation, reuse policy, subaccount-level URL management
• Context AI - an emerging initiative exploring how AI can enhance messaging personalization

Tech they work with

• Backend: Node.js, TypeScript (microservices)
• Infrastructure: AWS (API Gateway, SQS), Cloudflare, Redis, Kubernetes
• Messaging provider: Twilio
• Payments: Stripe
• Observability: Datadog
• Design & product: Figma (including Figma Make for prototyping), Appcues, Shortcut, Notion

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

"Her Fantasy Box is running 4 parallel campaigns and saturating our message pipeline. Build a traffic shaper."

"A merchant wants to send unique discount codes in every automated flow. Design the whole system."

"Daylight saving time just broke campaign scheduling for US merchants. Fix it before Monday."

"We need to verify toll-free numbers through Twilio with business registration data. Redesign the form."

Who thrives here

You'll do well here if you care about correctness and reliability at scale. Messaging is one of those domains where bugs have real-world consequences (compliance risk, merchant churn, lawsuits). You'll need to be comfortable owning a feature from Notion scope to production, and communicating clearly with non-engineers who depend on your work.

The work spans from high-level system design to very precise implementation details. Both matter.

Size & structure

5 engineers, the Team Lead + 1 Designer, working closely with the Head of Product and CTO.