Requirements

Deep backend engineering experience (typically 5+ years) building and operating production services in a modern microservice environment (e.g. JVM stack, relational databases, event-driven architectures).
A track record of leading complex projects (3–6 months) as the primary backend engineer: you’ve owned design, implementation, rollout and long‑term maintenance for systems with real customer and business impact.
Strong system design skills. You can design and evolve fault-tolerant, horizontally scalable systems, make pragmatic trade‑offs between short and long‑term needs and keep solutions simple where possible.
Experience maintaining, implementing and improving service maturity (latency, test coverage, fault tolerance, reliability).
Comfort working in high‑impact, data‑sensitive systems, including schema changes, migrations and performance-sensitive paths touching key tables and services in Messaging and Content.
Excellent collaboration and communication skills across engineering, product and support. Especially when clarifying ownership, triaging issues and aligning on behavior across multiple teams.
A growth mindset and evidence of multiplicative impact through mentoring others, improving shared libraries or shaping patterns that other teams adopt.

Nice to Have

Experience in messaging or marketing technology (email/SMS/WhatsApp sending, campaign management, compliance, or analytics).
Familiarity with MySQL/Vitess and large‑scale data migrations in a sharded environment.
Background working with CRM objects, properties and usage data, ideally including mirroring content into CRM and managing usage/ownership boundaries.
Experience with service maturity programs, error budgets and SLO‑driven reliability work within a larger product line.
Comfort collaborating with frontend teams to design robust contracts and APIs and with infra/platform teams on migrations and tooling improvements.

Design and build backend services and APIs for marketing Email, SMS and WhatsApp creation, management and publishing.
Own and evolve shared infrastructure used across Messaging.
Lead complex, cross-team projects (typically 3–6 months) that span multiple services, data stores and product areas.
Take a data-driven approach to reliability and performance.
Contribute to and sometimes lead database and infrastructure initiatives, such as keyspace migrations in partnership with platform teams.
Debug and resolve production issues across the stack: work with tooling like Metrics, Logfetch, Error Reporting and Tracing and use incident learnings to improve architecture, alerting and runbooks.
Drive technical design for new features and refactors: write design docs, review peers’ designs and ensure solutions are scalable, maintainable and aligned with the broader Messaging architecture.
Mentor and level up other engineers on the team via code reviews, pairing and informal coaching, helping them deepen their skills in distributed systems, reliability and product thinking.
Collaborate closely with frontend, infra and product partners across Messaging and adjacent teams to deliver cohesive, end‑to‑end solutions.
Participate in on‑call rotations and incident response, contributing to a culture of shared ownership for reliability and sustainable on‑call practices.

We know the confidence gap and imposter syndrome can get in the way of meeting spectacular candidates, so please don’t hesitate to apply — we’d love to hear from you.
If you need accommodations or assistance due to a disability, please reach out to us using this form.