You will work on the settlement and ledger services behind Meridian Exchange's B2B marketplace: roughly 40 million ledger rows a month, Java 21 on Spring Boot, Postgres 16, Kafka for event fan-out. The interesting part is not new endpoints, it is correctness under load — idempotent writes, exactly-once effects on top of at-least-once delivery, and holding p99 write latency under 250 ms as the ledger grows.
Full time — hybrid, three days a week on site
6-9 years building server-side systems, at least two of them carrying the pager for code you wrote
Bengaluru, India
Apply for this role
The work
What you will do
Own two or three services outright: schema design, deployment, dashboards, and the runbook somebody else reads at 03:00.
Move the ledger write path from single-row inserts to batched idempotent upserts keyed on a client-supplied token, targeting 8,000 writes per second sustained on the existing three-node Postgres cluster.
Design partitioning and retention for tables now past 1.2 billion rows, then run the migration online with no read downtime.
Review 15-25 pull requests a week and hold the line on what gets merged.
Share an on-call rotation of one week in six, and write the incident review when it was your service.
You
What we look for
Deep Java: you can say what allocates in a hot loop, and when virtual threads help versus when they only relocate the contention.
Working Postgres knowledge — query plans, lock waits, index bloat, and the trade-off between a covering index and write amplification.
Production experience with a message broker, including what you did the first time consumers fell four hours behind.
You can argue for the boring option. Most of this codebase should stay legible to whoever joins next year.
Comfortable talking directly to a client's engineers rather than through an account manager.