Kulshresth Jangid — Jaipur, India
Backend Engineer.
I build systems
that scale.
Four years building distributed systems at scale. Founded Kaizex — a multi-tenant Marketing OS — from schema to Kubernetes, currently running in production. Senior Engineer at Equinix.
Featured Case Study — Kaizex
CASE STUDYKaizex — Marketing Operating System
LIVEFounded · 2025 · Production
Problem
Content teams are operationally bottlenecked: posting manually, context-switching across platforms, and getting generic AI output with no strategic grounding. Existing schedulers (Buffer, Hootsuite) are dumb pipes — no content intelligence, no insight layer, no ownership of the output.
Solution
A Marketing Operating System with a four-stage pipeline: Source → Insight → Content → Distribution. Raw knowledge enters as articles and notes; the AI layer extracts strategic signals; a configurable persona engine generates platform-native content; async workers publish it. Three automation modes: Manual, Review, Autopilot. BYO-AI: connect any LLM. Scheduling engine validated at 1M+ tasks/instance.
Key signals
Selected Backend Engineering Work
// production systems and architecture
Monolith to Microservices Migration
INTERNALLed domain decomposition and phased service extraction at Rampwin. Reduced MTTR by 28%, eliminated cross-domain cascading failures, and enabled independent team deployments.
API Performance Overhaul
INTERNALSystematic data-access and caching redesign at CarDekho: p99 DB latency -40%, API latency -35%, user conversion +12%.
CI/CD Automation and Deployment Reliability
LIVEDesigned canary pipelines, automated rollback on Prometheus burn-rate triggers, and contract testing gates at Equinix. Deployment failure rate -30%.
What People Say
// colleagues, managers, clients
Kulshresth was the engineer you'd hand the ugly latency problem to and not have to think about again. The caching redesign on our search APIs cut p99 by 40% — but what stuck with me was that he came with a diagnosis, not just a fix, and the rollout didn't touch our on-call at all.
I've watched Kulshresth go from shipping features to owning entire systems — Kaizex is not a side project, it's a real multi-tenant platform he built pipeline by pipeline. Give him a vague problem and he'll come back with the schema, the failure modes, and the rollback plan.
We didn't need a contractor who just takes tickets — we needed someone who'd push back when a request didn't make sense for the business. Kulshresth did that, shipped fast, and was easy to reach when something broke. That combination is rarer than it should be.
Live Infrastructure
// tic-tac-toe gateway — all systems nominal