Ramp Backend Software Engineer role at Ramp owning core parts of the communications platform. Build integrations and design reliable delivery workflows across multiple messaging channels.
Responsibilities
Every approval request, receipt reminder, payment alert, and card notification Ramp sends has to reach the right person, on the right channel, at the right time. When it does, finance teams close faster and employees spend less time chasing tasks. When it doesn't, a missed message can mean a stalled approval, a late payment, or a flood of notifications nobody asked for.
Ramp's Communications Platform team builds the shared system that every product team uses to reach customers. It handles transactional messages across email, SMS, push, Slack, Microsoft Teams, and WhatsApp, including templating, delivery, retries, digesting, user preferences, and delivery monitoring. The team also supports the conversational experiences that let customers work with Ramp directly from the channels they already use.
We're looking for a backend engineer to own a core part of that platform. You'll take responsibility for an area such as message delivery and channel integrations, communication preferences, or platform reliability and scale, set its technical direction within the team, and keep it correct and dependable as message volume and the number of teams building on it grow. You'll work closely with product, design, and engineering partners across Ramp to make communications faster, more reliable, and easier for every team to build on.
Own the design and evolution of a core part of Ramp's communications platform, from technical design through launch, monitoring, and iteration
Build and extend integrations with messaging channels and delivery providers, including email, SMS, push, and workplace chat tools such as Slack and Microsoft Teams
Design delivery workflows that are idempotent, retry safely, and confirm successful delivery, so customers reliably get the messages they need without duplicate sends
Build communication preferences and controls that let users and administrators decide what they receive and where
Make the platform simple and safe for other Ramp engineers to build on, with clear abstractions, strong defaults, and good developer tooling
Improve the reliability, performance, and observability of the platform as message volume grows
Drive technical direction for your area and raise the engineering bar through design reviews, code reviews, and mentorship
Qualification
Experience designingStrong system design judgmentProduct senseExperience building notificationExperience scaling high-volume
Required
Experience designing, building, and operating production backend systems, including APIs, data models, and asynchronous workflows
A track record of owning a system or product area end to end and shaping its technical direction over time
Strong system design judgment, especially around reliability, idempotency, and correctness in high-volume distributed systems
Product sense: you care about the experience of the people receiving each message, not just the ticket, and you balance speed with quality
Clear communication and a collaborative approach to technical decisions across product, design, and engineering
Preferred
Experience building notification, messaging, or communications platforms
Experience integrating with messaging providers or channel APIs, such as Twilio, SendGrid, Slack, Microsoft Teams, or WhatsApp
Experience building internal platforms or shared services used by many engineering teams
Experience scaling high-volume, event-driven, or queue-based systems
