Suggested rewrite: Led a cross-functional initiative that improved [business outcome] by [measurable result], demonstrating experience relevant to this role...
Senior Software Engineer – Backend Platform
- Salary
- USD 150k–200k / yr
- Department
- Software Engineering
- Employment
- Full Time
- Experience
- Senior
- Published
- Apply before
- 6 Dec 2026
- Listing views
- 31
- Application actions
- 3
Make your next move.
Prepare your resume, explore your fit, and draft a cover letter for this opportunity.
About this role.
Hi, I’m Manu, Engineering Manager at Customer.io. We’re looking for experienced backend engineers who want to build and own the infrastructure that powers one of the most data-intensive platforms in marketing automation — systems that process millions of events per second, orchestrate complex workflows at scale, and keep everything running reliably for thousands of customers worldwide.
You’ll work on the Platform team, tackling hard distributed systems problems: designing for fault tolerance, scaling services under real production pressure, and building the foundational layers that every other team at Customer.io depends on. This isn’t just maintenance work — you’ll shape the architecture of systems that need to be both highly available and constantly evolving.
If you’re someone who gets energized by the intersection of scale, reliability, and developer experience — and wants ownership over infrastructure that truly matters — we’d love to talk.
What you’ll bring:
- Deep experience with distributed systems and large-scale backend architecture
- Strong instincts around reliability, observability, and fault tolerance
- Comfort reasoning about performance, capacity, and trade-offs at scale
- Experience with event-driven systems, message queues, or data pipelines is a plus
- A collaborative mindset — you raise the team around you
About Customer.io
Over 9,000 companies – from scrappy startups to global brands – use our platform to send billions of emails, push notifications, in-app messages, and SMS every day. Customer.io powers automated communication that people actually want to receive.
We help teams send smarter, more relevant messages using real-time behavioral data. Under the hood: Go, React, Ember and AI help us ship fast and scale with confidence.
What We Value
Ownership
You drive technical direction across systems and teams. You move with urgency, build with empathy, and think long-term. You’ve led large-scale infrastructure initiatives and know what it takes to get them over the line.
Engineers with customer focus
You think about how infrastructure unlocks customer value. You care about developer experience, system design, and how your work shapes the customer experience.
A healthy disregard for “the way things are done”
You bring rigor and creativity. Best practices matter, but never more than forward motion.
What You’ll Do
- Design and evolve distributed systems in Go to handle billions of daily events and messages and store and index petabytes of data
- Lead architectural decisions around performance, reliability, and real-time event processing
- Improve service-to-service communication through better APIs, messaging systems, and event-driven patterns
- Work across teams to uncover bottlenecks and system issues, and lead initiatives to resolve them for a smoother customer experience
- Tackle high-throughput challenges across data pipelines, queues, and scheduling infrastructure
- Able to debug production systems at scale using effective instrumentation, and resolve issues quickly and confidently
- Participate in an on-call rotation as required, supporting the reliability of the systems you build
- Share knowledge and raise the bar through sharing your progress publicly with short videos, thoughtful writing, and mentorship
- Leverage AI tools to prototype, move faster, and make better decisions
What we’re looking for
- Significant experience (typically 10+ years) building scalable, distributed systems in Go (or similar statically typed languages)
- Deep experience with databases – relational (MySQL, Postgres) and non-relational (DynamoDB, BigTable) – and how to make them fast
- Comfort working in cloud-native environments (AWS, GCP)
- Familiarity with APIs, observability, and operating production systems
- A bias for action over perfection, and pride in owning technical decisions
Compensation & Benefits
We believe in transparency. Starting salary for this role is $150,000 – $200,000 USD (or equivalent in local currency) depending on experience and subject to market rate adjustment. In addition to base salary, this role includes an equity grant in the form of stock options, so you share in the success you help build.
We know our people are what make us great, and we’re committed to taking great care of them. Our inclusive benefits package supports your well-being and growth, including 100% coverage of medical, dental, vision, mental health, and supplemental insurance premiums for you and your family. We also offer 16 weeks paid parental leave, unlimited PTO, stipends for remote work and wellness, a professional development budget, and more.
Our Process
No gotchas, no trick questions – just a clear, human process designed to help both of us make an informed decision.
- Application – We review everyone with care. Tell us why you’re interested.
- Recruiter Call (30 mins) – Let’s chat about what you’re looking for and how we work.
- Hiring Manager Interview (60 mins) – Talk with one of our hiring managers about your working style and a project you’ve owned end-to-end, plus a short AI-assisted coding exercise.
- System Design Interview (60 mins) – A collaborative system design conversation focused on scaling challenges.
- Coding Interview (60 mins) – Pair with one of our engineers for an agentic live coding interview.
All final candidates will be asked to complete a background check and employment verifications as part of our pre-employment process.
Customer.io recognizes the stifling impact of systemic injustice on diverse communities. We commit to using our influence to increase inclusion and equity within the tech industry. We strive to build an inclusive team culture, implement bias-free hiring practices, and develop community partnerships to expand our global impact.
Zoom is the only video conference platform that we use, virtual interviews will be conducted using the video capability (i.e., not via the chat), and offers will be extended in writing on official Customer.io letterhead. Please be vigilant in all of your job search activity, and if you have any questions please contact jobs@customer.io.
Join us!
We believe in empathy, transparency, responsibility, and, yes, a little awkwardness. If you’re excited by what you read and want to build software that makes communication better for everyone—apply now.
This job listing has been manually reviewed by the Jobicy Trust & Safety Team for compliance with our posting guidelines, including verification of the company's legitimacy, accuracy of job details, clarity of remote work policy, and absence of misleading or fraudulent content.
Role DNA
A quick view of the complexity, pace, ownership and collaboration implied by the job description.
Pace & Pressure
5/5Autonomy Level
5/5Communication Load
4/5Salary analysis
Estimated compensation compared with the broader US market for similar roles.
Core skills
Skills and capabilities most closely associated with this opportunity.
Sample interview questions
I would start by defining throughput, latency, ordering, retention, and delivery guarantees. I would use partitioned durable queues, independently scalable consumers, idempotent processing, back-pressure controls, dead-letter handling, and strong observability around lag, failures, and saturation. The design would be validated with capacity models and failure testing.
I would explain the customer impact, the telemetry used to narrow the issue, the immediate mitigation, and the root-cause analysis. I would also describe durable follow-up actions such as improved alerts, capacity safeguards, runbooks, tests, or architecture changes, along with measurable reliability outcomes.
I would evaluate consistency requirements, access patterns, data relationships, query flexibility, scale characteristics, operational burden, and failure modes. Relational databases are often preferable for transactional integrity and complex queries, while NoSQL systems can be useful for predictable, high-scale access patterns and horizontal distribution.
I would establish actionable service-level objectives and instrument services with structured logs, metrics, distributed traces, and correlation IDs. I would focus dashboards and alerts on user-impacting signals such as error rate, latency, queue lag, saturation, and dependency health, then ensure teams can use the signals effectively during incidents.
I would align stakeholders on the customer and technical problem, document options and trade-offs, and propose an incremental migration plan with ownership boundaries and success metrics. I would communicate progress transparently, solicit feedback early, reduce migration risk through compatibility layers or pilots, and share lessons learned after delivery.
Apply now.
Follow the employer’s application method and review Jobicy’s safety guidance before sharing personal information.
Continue on the employer website
Protect your personal information and never pay to secure an interview or job offer. .
