Apply for this role
Fill in the quick form below — it takes a minute. Go to the application form →
Careers · Engineering · Taipei
Senior Backend Engineer, Messaging
The SMS platform is the busiest thing we run. A single customer launch can push millions of messages through it in an hour, and every one of them is someone's passcode, alert, or order update. We're looking for a senior engineer to own the systems that decide whether those messages arrive — fast, in order, and accounted for.
About the role
The traffic that can't fail.
You'll work on the core messaging pipeline — the path a message takes from an API call, through routing and carrier selection, to a delivery receipt that a customer reconciles against their bill.
This is high-throughput, latency-sensitive backend work in Go, close to carrier interconnects across Asia-Pacific. It's also work with real operational weight: the code you write is on call, and the decisions you make about queuing, retries, and failover show up directly in delivery rates. You'll join a small Taipei engineering team that owns messaging end to end and cares about the unglamorous details that make the difference between 95% and 99% delivered.
What you'll do
- Own services in the messaging path — submission, routing, carrier adapters, and the delivery-receipt (DLR) pipeline — from design through production.
- Improve throughput and tail latency under peak load, and keep behavior correct when a carrier degrades or a queue backs up.
- Build and tune multi-carrier routing logic that weighs delivery quality and latency, not just cost, and fails over automatically.
- Make the system observable: metrics, tracing, and alerts that tell you a route is slipping before a customer does.
- Carry the pager for your services on a shared rotation, and lead the fixes that keep incidents from repeating.
- Review designs and code with the team, and mentor engineers earlier in their path.
What we're looking for
- 5+ years building backend services in production, with real ownership of systems that handle serious volume.
- Strong with a systems language — Go preferred; Rust, Java, or C++ experience translates well.
- Comfortable with distributed-systems fundamentals: queuing, back-pressure, idempotency, retries, and eventual consistency.
- You reason about latency and throughput with data, and you've debugged the hard production problem at 3 a.m. and written the postmortem after.
- You care about correctness and observability as much as features.
- Working proficiency in English; our engineering teams collaborate across Taipei, San Francisco, and Phoenix.
Nice to have
- Experience with telecom or messaging protocols (SMPP, SS7) or carrier/aggregator integrations.
- Familiarity with high-volume streaming or message-queue systems (Kafka, NATS, or similar).
- Exposure to multi-region infrastructure and failover.
Ready to apply?
Tell us about the hardest thing you've kept running.
Send your résumé and a short note. A real person on the engineering team reads every application — no keyword filter.
How we hire
Four steps, usually two to three weeks. See the process →
Apply
Submit your application
Fill in the form and add a link to your résumé or portfolio. A real person on our team reviews every application — usually within a few days.
✓ We reply to every applicant✓ No account or login required✓ Your details go straight to our hiring team