I grew up curious about how things keep talking to each other.

I was born in a Tier-3 town in Tamil Nadu and later grew up in Thanjavur, a Tier-2 city that shaped much of my early life.

From a young age, I was fortunate enough to have access to technology and, more importantly, the freedom to explore it. Most of my curiosity was fed by endless searching. If something caught my attention, I wanted to understand it. Why it worked. How it worked. What was happening underneath.

That curiosity never really left.

Even today, I'm the kind of person who wakes up in the middle of the night with an idea, opens a laptop, and starts building something in a completely unfamiliar language or framework simply because I want to understand it. There is a strange kind of excitement in learning how things work beneath the surface.

After 10th grade, I moved to Coimbatore. The move wasn't just about education. It exposed me to different people, different opportunities, and different ways of thinking. It expanded my understanding of society and gave me a broader perspective on the world around me.

During college, I found myself asking a question many students ask:

"What exactly should I become?"

I was studying Computer Science, but I had no idea where I belonged.

Cybersecurity?

Application development?

Networking?

Embedded systems?

Everyone seemed to have an answer. Some people insisted I should focus on Java. I tried. I didn't enjoy it.

Instead of choosing a single path immediately, I explored everything I could get my hands on.

I spent my time jumping between domains, reading documentation, watching videos, experimenting with tools, breaking things, fixing them, and learning whatever sparked my curiosity.

Then I discovered web development.

For the first time, I could write a few lines of code and immediately see something come alive on the screen. That feedback loop was addictive. Build something. Refresh the page. See the result. Repeat.

That feeling changed everything.

Around the same time, my friend Hari Haran and I spent countless hours learning new technologies together. We explored different stacks, built projects, and constantly challenged each other to learn more. Looking back, those experiences taught me that learning is much more enjoyable when shared with curious people.

What seemed like random exploration at the time eventually revealed something important.

I wasn't interested in just one domain.

I was interested in systems.

Applications, networks, devices, infrastructure, communication protocols, communities, and people. Everything connected to everything else.

That realization continues to shape the way I approach engineering today.

During the final year of college, I got exactly what I had been hoping for.

A startup.

Not a large company. Not a corporate office. A startup.

The role was Full-Stack Developer, but in reality, everyone did a bit of everything. Looking back, that was probably the best environment I could have asked for.

The founder, Bhagath Singh Karunakaran, had a huge impact on me.

He constantly pushed me beyond what I thought I was capable of. Whenever I became comfortable, he encouraged me to explore further, think bigger, and take ownership of challenges that felt slightly beyond my reach.

Many of the opportunities, experiences, and growth I gained during those years can be traced back to his willingness to trust me with responsibility before I thought I was ready for it.

Another person who deeply influenced my journey was Raja Renga Basiyam, the company's CTO at the time.

With more than three decades of experience building software systems, he became one of my earliest technical mentors.

Sitting beside him and observing how he approached problems was an education of its own.

He didn't teach frameworks.

He taught fundamentals.

How systems should be designed.

How to think before writing code.

Why simplicity matters.

Why understanding core concepts is more valuable than chasing the latest trend.

The startup itself became a crash course in engineering.

One day I would be writing backend code. The next day I would be debugging infrastructure issues, managing domains and DNS records, testing applications, improving SEO, or contributing to technical discussions about product direction.

There was no clear boundary between development and responsibility.

That environment taught me something I still believe today:

Real engineering is rarely limited to a job title.

It is about understanding the entire system and helping wherever the system needs you.

Today, I spend my time building across multiple layers of technology.

At i45G, I work on IoT systems, industrial communication, and technologies closer to the physical world.

At O2D3, I contribute to rebuilding healthcare technology into modern, scalable systems.

Alongside that, I continue building Kiospal — a community-driven initiative focused on supporting students, creators, and first-generation entrepreneurs from Tier-2 and Tier-3 ecosystems.

My interests span software engineering, networking, Linux, telecommunications, embedded systems, microprocessors, industrial communication protocols, cybersecurity, and open-source development.

I continue to be fascinated by how systems communicate, how ideas become products, and how technology can solve meaningful problems when built with care.

I don't chase every trend.

I prefer fundamentals, long-term thinking, and technologies that quietly keep the world running.

For me, technology has never been only about code.

It's about understanding systems — both technical and human.