What I work on

I'm Shailesh Chaudhari, a software engineer who likes building backends that hold up under load. These are the kinds of problems I spend my time on, at work and on my own projects. TypeScript everywhere, correctness first, shipped in small iterations.

Backend systems in TypeScript/Node

Multi-tenant services, queues and workers, idempotent APIs. Node.js with Express or NestJS, Prisma, PostgreSQL, Redis — typed end to end and tested where it matters.

Real-time systems

Socket.io with the Redis adapter across multiple instances, distributed locks for the operations that must happen once, presence and live updates.

Applied AI inside products

Gemini function/tool calling, multi-model fallback, per-key isolation, bring-your-own-key encryption, evals, MCP tools, and pgvector retrieval that says “I don’t know”.

Webhooks and idempotency

At-least-once delivery turned into exactly-once effects: a unique constraint and an atomic claim in the database rather than a cache that can drift from the truth.

Verification that asserts outcomes

Deterministic simulation, property tests, mutation testing, and a preference for tests that check the row changed over tests that check the page rendered.

Frontend that passes an audit

React and Next.js with Tailwind and shadcn/ui, checked against WCAG 2.1 AA with axe on every route in CI, in both themes.

How I work

Async-first and written-first. I share working code early, flag blockers as soon as I see them, and write tests for anything that needs to keep working. When something is subtly wrong with code that already passes its tests, I would rather find it than ship it — the engineering page is a list of the times that mattered.

Questions about any of this? Get in touch.