Maya Rodriguez

June 7, 2026

Dear Mr. Okonkwo,

The hardest part of moving money isn't the happy path — it's the duplicate charge that slips through at 2 a.m. under load. I spent the last three years designing for exactly that edge: at Lumen Payments I built an idempotency framework that was adopted org-wide and eliminated duplicate-charge bugs across 12 teams. When I read that Meridian is scaling its payments platform, that's the kind of problem I want to be in the room for, which is why I'm writing about your Senior Platform Engineer opening.

My instinct is to make reliability measurable. I led the migration of Lumen's payments ledger from a monolith into six Go microservices, cutting p99 latency 42% while the system grew to handle 50M+ daily transactions. Earlier, at Northwind Analytics, I built a Kafka-based real-time event pipeline running 2B events/day at 99.99% uptime, then trimmed cloud spend 35% ($1.2M/yr) by rightsizing services and adding autoscaling. I treat performance and cost as first-class features, not cleanup work.

Just as important to me is how a team ships. I mentored five engineers at Lumen and introduced an RFC process that cut production incidents 30% year over year — the kind of leverage where one reviewed design saves a dozen pages. I work primarily in Go, Python, and TypeScript across Kubernetes, AWS, and PostgreSQL, and I hold the AWS Solutions Architect – Professional certification. A platform team building for scale and correctness is precisely where that toolkit pays off.

I'd welcome the chance to talk through how Meridian thinks about latency, idempotency, and on-call health, and where I could contribute first. Thank you for your time; my resume is enclosed, and I'm happy to share design docs or walk through any of the systems above.