Software Engineer (Backend)

Location: Fully remote, based in the Americas or European time zones, with overlap during Americas working hours. Some travel is expected for team offsites, conferences, and meetups.

Salary: $140,000–$180,000 USD per year, depending on experience.

Company

A modern email-sending platform for developers, used by more than 4 million developers and supporting millions of emails every day.

What you will do

• Own features end-to-end, from idea and project scoping through APIs, dashboard experiences, and backend services.
• Build reliable distributed systems, including queues and background workers that handle traffic spikes, retries, duplicate events, concurrency, and partial failures.
• Scale APIs and relational databases while improving performance, data integrity, and efficiency.
• Operate production systems through monitoring, safe deployments, observability, debugging, and an on-call rotation.
• Work with support and customers to identify recurring problems and turn them into product improvements.
• Improve tests, tooling, infrastructure, and existing systems while delivering new capabilities.

Requirements

• 8+ years of software engineering experience, including substantial experience building and operating backend services in production.
• Deep experience with Node.js, TypeScript, Go, and Postgres.
• Experience with queues, asynchronous processing, distributed systems, APIs, relational data models, and safe database changes.
• Experience operating AWS services with serverless or container-based infrastructure, including deployments, capacity management, and production debugging.
• Experience with infrastructure as code using Terraform or AWS CDK.
• Clear written and spoken English and consistent overlap during Americas working hours are required.

Nice to have

• Experience with developer tools, public APIs, or email infrastructure.
• Comfort working across the stack to deliver complete product experiences.

Culture & Benefits

• Fully remote work with flexibility around shared working hours.
• Meaningful ownership over product direction and system operation.
• Autonomy to make decisions, propose improvements, and move work forward.
• High standards for API behavior, service reliability, and failure recovery.
• Collaborative, low-ego environment focused on knowledge sharing and developer growth.