Dear Hiring Team,
I’ve been a Meridian user since your public beta — I’ve filed three bug reports and one feature request, so in a sense this isn’t my first contribution. The Senior Backend Engineer opening is a chance to make the contributions full-time.
At Streamline (a Series B logistics platform), I own the order-routing service: 40M requests/day, p99 under 120ms. Last year I led a migration from a monolithic scheduler to event-driven processing that cut infrastructure spend 30% and took our worst incident category to zero. I work in TypeScript and Go daily, but the throughline of my career is simpler: I take ambiguous, load-bearing systems and make them boring.
What draws me to Meridian specifically is the product surface: developer tools live or die on latency and error messages, and your public changelog shows a team that sweats both. I’d be glad to bring my routing and reliability experience to your sync engine as it scales.
I’d welcome a conversation about what reliability at Meridian’s next order of magnitude looks like. Thanks for reading — and for fixing that webhook retry bug I reported in March.
Best, Priya Raman