The useful layer between a good idea and a product that can be trusted with real customers, real data, and real growth, whether you're scaling a startup or modernising a small business.
Reliable APIs and services that stay legible when the first 10,000 users arrive.
Useful agentic workflows, not demos: model orchestration, evaluation, and the guardrails around both.
Queues, caches, data flows, and observability designed around the failure modes that matter.
Clear interfaces that connect the customer experience to the systems behind it, without leaving the last mile unfinished.
The connective tissue between the tools a small business already relies on, turning scattered work into one reliable flow.
Internal tools and automation that turn a repeated two-day task into a reliable few-minute workflow.
A few examples of the systems work behind the résumé. The decisions, not just the logos.
Turning a complex privacy review into an always-on product surface for teams shipping fast.
A high-stakes reporting workflow rebuilt around speed, validation, and confidence.
Backend improvements for an audio platform serving 1,000+ audiobooks without wasting work.
The strongest engineering instincts are sharpened outside the day job too, by reading unfamiliar code, making careful changes, and giving them back. That breadth carries into the integrations and product work small businesses depend on.
LLM integrations, completions, chat, image generation, and guardrails.
Functional API contributions including trimzeros, fromstring, and frame.
Configurable TCP inactivity timeout replacing a fixed ten-minute limit.
A community assistance platform with listings, reusable UI components, and RESTful CRUD APIs.
Tools are selected for the constraint in front of us. The goal is a system that is easy to change, easy to operate, and hard to surprise, with a usable product surface on top.
Production software is a conversation with edge cases. I design the system so the next decision is clear.
A fast first release is valuable. A fast first release you can still understand six months later is better.
I stay close to the product question, not just the ticket. The implementation should move the business forward.
I'm Keshav, a backend and product engineer at Privado.ai, NIT Meghalaya graduate, ICPC Asia Regionalist, and open-source contributor. I build the systems behind the UI, the UI that customers use, the AI agents that remove manual work, and the integrations that connect it all.
That range is useful whether you're launching a startup or improving a small business: I can translate a fuzzy product risk into a clean system boundary, make the tradeoff explicit, and ship the part that unlocks the next milestone.
Whether you're launching a startup or improving a small business, tell me what's becoming a bottleneck. I'll tell you where I'd start.
A clear paragraph is enough to start a useful conversation. Click below, it opens Gmail with the questions already laid out, just fill in the blanks and send.
Open in Gmail, pre-filled →Not on Gmail? Use the plain email link on the left instead.