Senior Software Engineer, NewsBreak

• 5+ years of backend software engineering, including ownership of a messaging, notification, or lifecycle platform
• Operated that platform at meaningful scale, millions of messages per month, across at least two of email, SMS, and push
• Designed event-driven systems with explicit idempotency, retry, and deduplication guarantees, and carried on-call responsibility for them
• Shipped within a consent or privacy regime such as TCPA, CAN-SPAM, GDPR, or CCPA, where the system, not a policy document, enforced the rules
• Hands-on production experience with a major messaging provider or platform (for example Twilio, SendGrid, Braze, Iterable, Customer.io, or an in-house equivalent), and clear judgment about build versus buy
• Strong proficiency in at least one of Go, Java, Kotlin, Python, or TypeScript, plus SQL

Desirable

• In a two-sided marketplace, nearly every commitment made to a customer or a provider is delivered as a message: confirmations, time-sensitive notifications to professionals, outcome follow-ups that feed our quality measurement, shared summaries for family members, and longer-horizon engagement
• Because consumer messaging in our category is regulated, the platform that sends these messages is also the system that enforces consent, preferences, and suppression
• You will design, build, and own that platform across email, SMS, push, and in-app channels
• Design and build the messaging platform: triggering, routing, templating, retries, deduplication, rate limiting, scheduling, and delivery tracking, with reliability and observability as first-class requirements
• Build the consent and preference layer: per-channel consent records with provenance, opt-out and do-not-contact propagation to partners within contracted timelines, quiet hours, and suppression rules that no campaign can override
• Own deliverability end to end: sender registration and reputation, authentication standards, bounce and complaint handling
• Partner with data and machine-learning engineers on event-triggered engagement, including frequency management and holdout design
• Provide experimentation hooks so growth can test timing, content, and channel without changes to the core platform
• Establish engineering standards for a system that carries regulatory obligations, including audit trails and access controls