Why I started Cognitain

I got my first full-time job in my third year of college. The company was RepCard. I was still finishing my degree, and I was already shipping iOS work in production.

After college, I got placed at Zomato. The offer was 29 LPA. For a kid who had been grinding mobile engineering, that number meant something. Stability. Proof. A seat at a company most engineers in India grow up wanting.

I worked at Zomato for about a year.

The hours were real. Roughly 10 to 11 hours a day, including Saturdays and Sundays. I was learning at scale, and I was also watching a quieter pattern form in the background: every time I hit a problem in my own life, I wrote it down. Not as a complaint. As a product note.

Habit systems. Developer tooling. Things I kept wanting that did not exist in the shape I needed. The list got longer than my excuses.

At some point the question stopped being "Can I grow more inside this job?" and became "Do I have more potential if I take a bet on myself?"

I already knew how to ship. I had done it at RepCard. I had done it at Zomato. What I had not done was put my name on the bet.

So I started Cognitain.

Not because the Zomato job was small. Because I wanted to scale my own ideas in public, test them against real users, and find out what I am actually capable of when the product is mine. Habit AI came first. Flow-UI followed. I still call myself a Product Engineer on purpose. Titles like CEO can wait until the numbers earn them.

This is the short version of why I left a high-paying role at Zomato to build Cognitain: I wrote the problems down, I trusted the list, and I chose the harder path on purpose.