AI engineer & mobile developer
Enterprise mobile by day. Autonomous AI agents by night.
currently cooking
I'd rather build the thing than wait for permission to.
Eight-plus years shipping mobile apps for banks and telecoms. Nights, I build AI agents that browse, decide, and act. Farm kid from Andhra Pradesh — permanently mid-build.
Scroll sideways →
An autonomous job-application pipeline — job-board connectors, browser automation, a semantic answer bank, and Telegram notifications. It sources, matches, and applies on its own so I can focus on building.
A voice-activated personal assistant wiring together faster-whisper speech recognition, Browser Use for real web control, and the Claude API — an agent that actually does things, not just talks back.
Building with the modern agent stack — Claude API, Browser Use, MCP connectors, and retrieval pipelines. Wiring LLMs into systems that take real actions: browse, decide, execute, report.
Experimenting with the generative video frontier — Seedance and Kling with a character-consistency framework: face-locked descriptors, structured prompts, and director-style references for repeatable results.
A Gatling performance-testing framework I built for Mastercard token mapping — dynamic timestamp generation and compliance-grade load coverage for payment flows that can't fail.
A product concept aimed at the impound-lot industry, with a municipal go-to-market in Florida. Unglamorous problem, real money, nobody's solved it well yet.
Directed with prompts. Rendered by machines.
Seedance · Higgsfield · classroom & more — drag / tap anywhere ✦
The late-night build soundtrack — hit play.
Fintech & telecom — apps where mistakes aren't an option.
I ship clean code, drink too much chai, and have never once broken production on a Friday.*
*Okay, once. But I fixed it before anyone noticed. Let's build something.