Skip to content

I build backends where partial failure is the normal case.

Software engineer at Kazam EV Tech in Bengaluru, working on Unified Bharat Charging: cross-network EV charging interoperability at national scale, and the payment and reconciliation layer underneath it. I ship things that keep working once the traffic and the failure modes show up. Then I write down what broke.

Priyanshu Naskar

Focus

Distributed systems

Idempotency keys, webhook-driven lifecycles, state-machine reconciliation, and recovery from partial failure. The interesting part is always what happens on the retry.

Payments and ledgers

Order and payment lifecycles at 20,000+ daily transactions, automated ledger reconciliation, and refund and cancellation flows that remove manual settlement work.

Multi-tenant platforms

Custom multi-tenancy and RBAC with isolated data boundaries, serving 1,200+ vendors and technicians across 20+ OEM tenants.

Backend and APIs

Go and Django REST, gRPC, WebSockets, Celery for async work, Redis for caching. Postgres and MongoDB underneath, on AWS.



Experience

Kazam EV Tech

Software Development Engineer / 2024 — now / Bengaluru

Build and run a Go interoperability platform for Unified Bharat Charging, unifying 3,420+ EV chargers across HPCL and BPCL and processing 20,500 daily transactions. Built the webhook-driven, idempotent order and payment lifecycle, and the multi-tenant OEM-Tool now serving 1,200+ vendors across 20+ tenants.

Alemeno

Software Development Engineer / 2024 / Remote

Backend for an edtech platform serving 400,000+ students on Django REST, with Celery for async processing and rolling multi-node deploys. Cut API response times 65% on high-traffic endpoints with a Redis caching layer, without touching the schema.



Get in touch

Open to interesting problems and good conversation about systems.

pnaskardev@gmail.com