About the role
Requirements:
- 10+ years of engineering experience with deep, hands-on ownership of large-scale distributed systems, comparable scale strongly preferred: hundreds of services or thousands of instances, billions of daily events.
- You've carried sole accountability for a production system through real failures, not adjacent to it, not advising on it. Owned it.
- Deep command of queueing and async architectures, delivery semantics, ordering, backpressure, idempotency, exactly-once myths, and at-least-once realities.
- Strong with multiple storage engines (SQL and NoSQL); you reason about consistency models, indexing at scale, and when each engine is the wrong choice.
- Expert-level depth in Redis or comparable in-memory systems, including their failure modes under memory pressure and network partition.
- Production experience on Kubernetes at scale, resource limits, autoscaling behavior, and what actually happens when a node pool dies.
- Exceptional design communication, docs, diagrams, and RCAs that drive decisions across multiple teams.
- Fluent in Node.js and/or Go, enough to prototype your own proposals and ship fixes on the critical path.