Senior Full Stack Software Engineer at Customer.io

Role overview

Build and ship product experiences for Customer.io’s messaging platform, combining backend and frontend work for customer workflows. This posting is for remote work in EMEA.

Responsibilities

• Build fullstack features in Go, React and Ember for customer workflows.
• Collaborate with teammates to turn product ideas into shipped value.
• Help scale systems for more customers, messages and use cases.
• Participate in on-call and improve reliability of the software you build.
• Share knowledge, mentor colleagues and use AI agents with careful review.

Qualifications

• Seven or more years building and scaling backend services and product-facing features.
• Fluency in TypeScript, React or similar frontend technology and a statically typed backend language such as Go.
• API, relational-database and testable, performant-code experience.
• Care for frontend polish, backend performance and customer experience.
• Action-oriented ownership and comfort working in ambiguity.

Technology in this role

• TypeScript: Fluency in TypeScript, React or similar frontend technology and a statically typed backend language such as .
• React: Build fullstack features in Go, React and Ember for customer .
• Go: Build fullstack features in Go, React and Ember for customer .
• CAN: You’ll design, build, and ship the core product experiences our customers rely on - while helping the team push boundaries on what great communication tools can .

Role-specific candidate guide

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

Understanding the scope. This Senior Software Engineer, Full Stack 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: “Hi, I’m Paul, VP of Engineering at Customer.io . We’re looking for curious, driven Fullstack (Product) Engineers who want to own big things and delight our customers. You’ll design, build, and ship the core product…” 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 “Build fullstack features in Go, React and Ember for customer workflows.”; “Collaborate with teammates to turn product ideas into shipped value.”; “Help scale systems for more customers, messages and use cases.”. 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 and scaling backend services and product-facing features.”; “Fluency in TypeScript, React or similar frontend technology and a statically typed backend language such as Go.”; “API, relational-database and testable, performant-code experience.”. 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 TypeScript, React, 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 named tool, explain the closest related system you have.

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

• Senior Software Engineer at Voltus — Voltus
• Software Engineer II — Clearer.io
• Full-Stack Software Engineer at Runpod — Runpod
• Senior Software Engineer, Client Lifecycle at Virta Health — Virta Health
• Senior Software Engineer, Session Replay, Canada at Grafana Labs — Grafana Labs
• Senior Software Engineer, Session Replay, US at Grafana Labs — Grafana Labs