高级软件工程师, 后端 (AMER)
Staff Software Engineer, Backend (AMER)
你好，我是Paul，[Customer.io](http://Customer.io)的工程副总裁。我们正在寻找一位资深工程师，负责制定每天处理数十亿条消息的系统的技术方向。这个职位不是关于更快地交付，而是关于决定哪些功能需要开发，架构下一步该往哪里走，并提升你周围工程师的能力。
### 关于[Customer.io](http://Customer.io)
超过9000家公司——从初创公司到全球品牌——使用我们的平台每天发送数十亿封电子邮件、推送通知、应用内消息和短信。[Customer.io](http://Customer.io)支持人们真正想要接收的自动化沟通。
我们帮助团队利用实时行为数据发送更智能、更相关的信息。后台：Go、React、Ember和AI帮助我们快速交付并有信心地扩展。
### 我们看重什么
**在公司规模上的责任感**
你承担那些没人认领的问题——这些问题跨越多个小组，没有明确的负责人，如果被忽视，可能会让我们损失一年的时间。你要么解决它们，要么让领导层达成一致。
**有产品品味的工程师**
你像用户一样思考，而不仅仅是工程师。你能将架构决策与客户实际体验联系起来，并能向不写Go的人解释这种联系。
**对“传统做法”的健康怀疑**
你淘汰那些已经失去价值的做法，包括你自己曾参与建立的。最佳实践很重要——但永远不能阻碍前进。
**放大战斗力**
你最好的季度不是看你交付了什么，而是看部门现在能做什么，而之前是做不到的。
### 你会做什么
- 在Go中塑造我们分布式消息系统的整体技术方向——在关键服务上做出高层次的架构决策，这些服务在规模、成本和可靠性之间存在紧张关系
- 承担跨小组和职能边界的模糊且高风险的问题，并在没有人知道正确答案时推动问题得到解决
- 在多个团队之间就有争议的技术问题达成共识，并清晰地传达权衡，使高级管理层能够据此行动
- 提升部门标准——设定质量和设计标准，指导高级工程师，并将你的知识转化为其他团队无需你在场也能使用的框架和文档
- 推动跨多个小组的工程流程和工具改进，而不仅仅是单一团队
查看英文原文
Hi, I'm Paul, VP of Engineering at [Customer.io](http://Customer.io). We're looking for a staff engineer to set technical direction for the systems that move billions of messages a day. This isn't a role about shipping more, faster. It's about deciding what gets built, where the architecture needs to go next, and raising the ceiling for the engineers around you.
### About [Customer.io](http://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](http://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 at company scale**
You take on the problems nobody has claimed yet — the ones that span squads, have no obvious owner, and would quietly cost us a year if left alone. You either solve them or get leadership aligned to.
**Engineers with product taste**
You think like a user, not just an engineer. You connect architectural decisions to what customers actually experience, and you can explain that connection to people who don't write Go.
**A healthy skepticism for "the way things are done"**
You retire practices that have outlived their usefulness, including ones you helped build. Best practices matter — but never more than forward motion.
**Force multiplication**
Your best quarter isn't measured by what you shipped. It's measured by what the department can now do that it couldn't before.
### What You'll Do
- Shape the technical direction of our distributed messaging systems in Go — making the high-level architectural calls on mission-critical services where scale, cost, and reliability are all in tension
- Take on ambiguous, high-stakes problems that cross squad and function boundaries, and drive them to a decision when the right answer isn't obvious to anyone yet
- Build consensus on contested technical questions across teams, and communicate the tradeoffs clearly enough that senior leadership can act on them
- Raise the department's bar — set quality and design standards, mentor senior engineers, and turn what you know into frameworks and documentation other teams can use without you in the room
- Drive engineering process and tooling improvements that span multiple squads, not just your own
- Interview and calibrate against our career ladder, giving honest, evidence-based assessments of candidates
- Use AI agents to make multi-file changes by scoping the work, writing the prompt, and verifying the output
### What we're looking for
- 10+ years building scalable, distributed systems in Go (or similar statically typed languages), including several as the person others turned to on architecture
- Depth across multiple systems or domains, not just one — you've been the recognized expert in more than one place
- A track record of designing for production reality: you quantify tradeoffs in throughput, cost, and reliability rather than picking a reasonable path and defending it
- Experience designing observability and recovery as first-class concerns — metrics, alerting, rollback, backpressure, checkpointing — not logging added afterward
- Comfort working in cloud-native environments (AWS, GCP), with relational databases (we use MySQL) and a real understanding of performance tradeoffs
- Evidence of making other engineers better: mentorship, technical writing, design review, standards that outlasted your involvement
- A bias for action over perfection, and the judgment to know which decisions are worth slowing down for
### Compensation & Benefits
We believe in transparency. Starting salary for this role is $200,000 - $240,000 USD (or equivalent in local currency) depending on experience and subject to market rate adjustment. This role also carries a 10% annual bonus target.
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.
See full benefits here →
### Our Process
No gotchas, no trick questions - just a clear, human process designed to help both of us make an informed decision.
1. **Application** - We review everyone with care. Tell us why you're interested.
2. **Recruiter Call (30 mins)** - Let's chat about what you're looking for and how we work.
3. **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.
4. **Architecture Interview (60 mins)** - A collaborative system design conversation focused on scaling challenges, tradeoffs, and failure modes.
5. **Take-Home Assignment** - Complete a short, realistic task similar to what you'd work on here.
6. **Assignment Review Call (60 mins)** - Walk us through your work and discuss tradeoffs, priorities, and how you'd iterate.
All final candidates will be asked to complete a background check and employment verifications as part of our pre-employment process.
[Customer.io](http://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](http://Customer.io) letterhead. Please be vigilant in all of your job search activity, and if you have any questions please contact [jobs@customer.io](mailto: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.