Payments & billing
Subscriptions, retries, reconciliation and the ledgers behind them — built to be audited.
Hi there
Senior Backend Engineer
I make flaky systems boring — billing, queues and the parts nobody notices until they break.
Work with meBackend engineer with six years on high-traffic Laravel products. I own billing correctness and queue reliability, and I like the unglamorous work of making a flaky system boring again.
Lately that has meant payments infrastructure — retries, reconciliation and the reporting that finance actually reads.
Subscriptions, retries, reconciliation and the ledgers behind them — built to be audited.
Idempotent workers, dead-letter handling and dashboards that say what actually failed.
Partner-facing APIs with contract tests, versioning and documentation people can follow.
Finding the one query that costs four seconds, and the report that never needed it.
Acme Payments · Remote
Corepoint Systems · Pune
Nimbus Labs · Pune
Savitribai Phule Pune University
Open source
Product
API
“Aarti rebuilt our settlement pipeline in a quarter and it has not paged anyone since. That is the whole review.”
“The rare engineer who writes the runbook before the incident. Our integrators noticed the difference within a month.”
“Clear, calm and honest about trade-offs. I would hire her again tomorrow.”
Have a payments problem, a queue that misbehaves, or a team that needs a steady pair of hands? I would love to hear about it.
Available from November