Senior Software Engineer, Strategic Integrations

Attentive

5h•$180,000 - $205,000

About The Position

Attentive® is the AI marketing platform for 1:1 personalization redefining the way brands and people connect. We’re the only marketing platform that combines powerful technology with human expertise to build authentic customer relationships. By unifying SMS, RCS, email, and push notifications, our AI-powered personalization engine delivers bespoke experiences that drive performance, revenue, and loyalty through real-time behavioral insights. Recognized as the #1 provider in SMS Marketing by G2, Attentive partners with more than 8,000 customers across 70+ industries. Leading global brands like Crate and Barrel, Urban Outfitters, and Carter’s work with us to enable billions of interactions that power tens of billions in revenue for our customers. With a distributed global workforce and employee hubs in New York City, San Francisco, London, and Sydney, Attentive’s team has been consistently recognized for its performance and culture. We’re proud to be included in Deloitte’s Fast 500 (four years running!), LinkedIn’s Top Startups, Forbes’ Cloud 100 (five years running!), Inc.’s Best Workplaces, and the Human Rights Campaign Foundation's Corporate Equality Index! About the Role The Strategic Integrations team builds and operates ecosystem-critical partner integrations that enable enterprise-grade omni-channel marketing use cases. Integrations are foundational to Attentive’s evolution from an SMS-first product toward a modern omni-channel platform: they power personalization, retention, and expansion, and they are table-stakes in enterprise evaluations. In 2026, we’re pivoting from “building integrations” to building an integrations platform model that is standardized, observable, extensible, and competitive. We’re looking for a Senior Software Engineer who has deep experience improving system quality and thoughtfully migrating legacy systems to better platforms—without breaking customers, support workflows, or downstream dependencies.

Requirements

Significant professional experience building and operating backend/distributed systems, with a track record of improving reliability, observability, and operational quality (not just shipping features).
Demonstrated experience migrating legacy systems to new platforms through safe, incremental approaches (e.g., compatibility layers, measured cutovers, staged rollouts), not only “rewrite” projects.
Strong debugging ability across service boundaries, including designing systems so issues are diagnosable (metrics/logs/traces, correlation IDs, clear error surfaces).
Experience integrating with third-party APIs at scale (auth, pagination, vendor limitations, rate limits) and building resilient ingestion/export patterns.
Strong engineering fundamentals (system design, data modeling, APIs, testing strategy), and the judgment to balance pragmatism with long-term maintainability.
Proficiency in a modern backend language; our ecosystem includes typed backend services (commonly Java/Kotlin).
Comfort collaborating cross-functionally (product, design, partnerships/support, platform teams), and willingness to lead through influence: writing proposals, running design reviews, leveling up patterns and templates.

Responsibilities

Lead platform quality improvements that unlock faster, safer integration delivery. Build durable, reusable engineering systems (frameworks, libraries, templates) rather than one-off solutions, aligned with our principle to “build with quality before speed.”
Migrate existing integrations onto a more standardized model. Drive incremental, observable migration plans that reduce risk, preserve backwards compatibility where needed, and avoid “silent breakage,” consistent with our focus on versioned contracts and explicit migrations.
Make end-to-end data traceability real. Address today’s gaps where tracing a datapoint can take days of cross-team coordination; evolve the system so engineers can trace acquisition → ingestion quickly and confidently.
Deliver data visibility as a first-class experience. Build/run capabilities like real-time logs, historical ingestion progress, and payload-level debugging tools—so customers and internal teams can understand data flow and integration health without guesswork.
Improve contract safety and testability. Reduce manual E2E testing by investing in reusable vendor payload fixtures/scripts and contract tests that reflect canonical downstream expectations.
Harden vendor API resilience and upgradeability. Reduce weeks-long cleanups from vendor API changes by improving API contract management, test coverage, and (where appropriate) generated models/boilerplate reduction.
Design for failure and recovery. Vendor APIs will rate-limit, error, and change; you’ll build resilient patterns for retries, idempotency, backoff, and partial failure.
Partner across engineering and product. Collaborate with Integrations Core and downstream domain teams to evolve paved paths, canonical models, and platform capabilities—so integration engineers stop reinventing the same infrastructure problems.