Strategic software engineer building scalable architectures, performance-critical systems, and AI-driven automation.
I build the parts of software that have to hold up — the architecture under load, the latency budget nobody else wants to fight for, the migration that can't take the site down.
Three teams, one constant: I ship systems that stay fast when they get popular.
Real-time DDoS mitigation powered by ML malicious-IP detection.
Configurable voice-to-voice agent for natural speech dialogue.
Query any PDF in natural language with vector search.
B.E. Computer Science and Business Systems
Vellore Institute of Technology (VIT), Vellore
GPA 8.71 / 10.00
Off the screen, I'm chasing the same thing — controlled output under load.
Wrestling × Muay Thai
Wrestling for control, Muay Thai for timing. Both reward what good engineering does — composure when the pressure spikes and the plan meets reality.
Powerlifting × Bodybuilding
Progressive overload is a deploy pipeline for the body: small, measured increments, logged and repeated until the numbers move. Powerlifting builds the base; bodybuilding shapes it.
Same operating principle everywhere — show up, measure, overload, recover, repeat.
Let's
build.
Hard systems problem, a product to ship, or a team to scale? I'm founding engineer at codity.ai and open to a sharp conversation.