Senior Backend Software Engineer at Customer.io

Role overview

Build and operate distributed Go backend systems for Customer.io messaging across email, push, in-app and SMS. This individual posting lists remote work in EMEA.

Responsibilities

• Design and build distributed Go systems for timely, relevant customer communications.
• Own work end to end from architecture and schema design through testing, deployment and monitoring.
• Collaborate across teams to debug issues and deliver reliable, scalable solutions.
• Participate in on-call rotations and improve production reliability.
• Share knowledge through writing, short videos and mentorship, including responsible use of AI agents.

Qualifications

• Seven or more years building scalable distributed systems in Go or a similar statically typed language.
• Comfort with AWS or GCP cloud-native environments.
• Relational database experience, including performance tradeoffs and MySQL-like systems.
• Production observability and operational experience.
• Ownership, product judgement and a bias for action.

Technology in this role

• React: Under the hood: Go, React, Ember and AI help us ship fast and scale with .
• AWS: Comfort with AWS or GCP cloud-native .
• GCP: Comfort with AWS or GCP cloud-native .
• Go: Customer.io is hiring experienced backend engineers to design and operate distributed Go systems that deliver email, push, in-app and SMS communications at .
• MySQL: Relational database experience, including performance tradeoffs and MySQL-like .
• CAN: You’ll design, build, and evolve the systems that power communication at massive scale - while helping us push the boundaries of what great engineering can look .

Role-specific candidate guide

Preparation notes based on the employer’s stated responsibilities and qualifications.

Understanding the scope. This Senior Software Engineer, Backend position at Customer.io is best assessed through the work described in the employer’s posting, rather than the title alone. The available role overview says: “Customer.io is hiring experienced backend engineers to design and operate distributed Go systems that deliver email, push, in-app and SMS communications at scale. The postings are remote in the Americas or EMEA.” Read that statement together with the responsibilities below to understand the likely balance between delivery, coordination and technical decision-making. The role belongs to the software engineering area, but that label is only a guide to the work; the employer’s own requirements remain decisive. Before applying, check the original listing for reporting lines, product or team assignment, employment terms and any details that may have changed since this copy was checked. Where this page says a fact is not specified, treat it as an open question rather than an implied promise.

What the responsibilities signal. The posting specifically names “Design and build distributed Go systems for timely, relevant customer communications.”; “Own work end to end from architecture and schema design through testing, deployment and monitoring.”; “Collaborate across teams to debug issues and deliver reliable, scalable solutions.”. For each duty, identify a project where you performed comparable work and be ready to describe the context, your own contribution, constraints, decisions, and measurable result. Explain how you moved from the initial need to implementation, review, release or operational follow-through, where those stages apply. If the work involved other teams or users, distinguish your decisions from the group’s contribution. Avoid presenting a technology keyword as proof by itself: connect it to the problem you solved, the scale or complexity involved, and what changed after your work. The source may contain additional duties; review it directly before preparing your application.

How to read the requirements. The listed qualifications include “Seven or more years building scalable distributed systems in Go or a similar statically typed language.”; “Comfort with AWS or GCP cloud-native environments.”; “Relational database experience, including performance tradeoffs and MySQL-like systems.”. Mark each requirement as demonstrated, adjacent experience or a genuine gap, then use a concise example for the first two categories. A strong example explains what you personally owned, how you made trade-offs, how you validated the result and what you learned. If the posting specifies years of experience, language ability, certifications, location or eligibility, address those facts plainly in your CV or application rather than relying on the employer to infer them. Do not claim a qualification from exposure alone. For a requirement you do not meet, describe relevant transferable experience accurately and ask the recruiter whether it is mandatory.

Technology and working evidence. The technology terms associated with this listing are React, AWS, GCP, Go. Treat this as a set of posting-derived signals, not a guarantee that every tool is used daily or that the list is complete. For each term relevant to your experience, prepare one concrete example: the system or workflow, the part you owned, the alternatives considered, and how you tested reliability, security, performance or usability as appropriate. If you have not used a.

Benefits

• Customer.io lists starting salary of USD 150,000–200,000 for this role, subject to market adjustment, plus full insurance premium coverage, 16 weeks paid parental leave, unlimited PTO, remote and wellness stipends and a professional development budget.

About Customer.io

Customer.io provides automated email, push, in-app and SMS communication using behavioural data. The employer describes Go, React, Ember and AI in its technology stack.

Browse job categories

Related jobs

• Software Engineer II — Clearer.io
• Senior Golang Engineer at Kake — Kake
• Senior Software Engineer, Client Lifecycle at Virta Health — Virta Health
• Staff Software Engineer, Backend at Customer.io — Customer.io
• Staff Technical Support Engineer, Web App at Horizon3 — Horizon3
• Senior Software Engineer - Backend Platform at Customer.io — Customer.io