About
A coastal town,
an electronics degree,
and a detour.
I grew up in Machilipatnam, a port town on the Andhra coast that has been shipping things out to the world for about four hundred years. It is not where people expect software to come from, which has never seemed like much of an argument.
I went to university to study electronics. Circuits, signals, tolerances. Somewhere between a lab bench and a laptop I started writing software instead, and found the same job underneath it: build the thing so it does not fall over, and know exactly where it would if it did.
What I do now is full-stack engineering with a lot of AI work in it. Schemas, services, retries, workflow automation, and models doing something genuinely useful rather than something impressive in a demo.
The part I care about is the part nobody sees. That is not modesty. It is where the whole thing either holds or does not.
Where I am now
2026
AI product work
Intants
Building the parts of a product that have to survive real usage: data models that stay correct as the product changes, services that fail in predictable ways, and AI features that earn their place rather than decorate the roadmap.
Client engagements
Freelance · Ongoing
Currently building an ordering platform for Vending & Delivery LLC in the United States, alongside a small number of other engagements and n8n automations that take the repetitive work off someone's desk. Usually somewhere between a real product and a business that needs to be understood before a line of code is worth writing.
The road here
2022 · 2026
- 2022
Electronics, not software
Started a B.Tech in Electronics & Communication at Vishnu Institute of Technology. The plan was circuits. Circuits teach you something software courses rarely do: every component has a tolerance, and the system is only as good as the weakest one in the chain.
- 2024
The detour that stuck
A product assurance internship at Bharat Electronics, and somewhere in that year the detour became the direction. Writing code turned out to be the same discipline as testing hardware: find where it fails before someone else does.
- 2025
Building without a brief
VishnuDentaCare and PaperPilot. Neither was commissioned. Both were built because the problems were interesting. One keeps several clinics' records sealed from each other; the other reads handwritten answer sheets. Work nobody asks for is where you find out what you actually care about.
- 2026
First people who paid me
Shri Arudra Exports and International Ocean Foods put in front of international buyers, an ordering platform for Vending & Delivery LLC in the US, and AI product work at Intants. The systems got larger, which mostly means the cost of a careless decision got larger with them.
B.Tech, Electronics & Communication · Vishnu Institute of Technology, Bhimavaram
What I believe
Three of them
Structure before surface
A beautiful interface on a bad schema is a debt with interest. The order matters: decide what is true, then decide how it looks.
Restraint over decoration
Most features are someone's idea of what might be useful. The discipline is asking which ones survive contact with an actual user, and leaving the rest out.
Built to be inherited
Code has a second audience: whoever maintains it after you. Writing for that person is the most generous thing you can do, and it usually makes the first version better too.
Off the clock
I still solve problems for fun, which is either a red flag or the whole point depending on who you ask. A few hundred of them on LeetCode, mostly the medium ones, because those are where the thinking is. The rest of the time I am reading about system design, taking apart products I admire, or building something deliberately strange to see what happens.
Curiosity is the only part of this job that cannot be taught.