Why I Chose This Path

I did not always have everything planned.

I never mapped out my entire career or knew exactly where life would take me. But looking back, I realize that every decision I made had a reason behind it. Those reasons evolved over time, yet each one quietly led me to the next chapter.

In 2017, I decided that I wanted to become an engineer. Surprisingly, choosing the discipline did not take much thought. Civil Engineering felt natural, not because it was the easiest or the most popular option, but because it builds the foundation of everyday life.

Roads, bridges, buildings, water systems, airports, and public infrastructure rarely attract attention when they function well. Yet they influence how people live, travel, work, learn, and even survive. We notice infrastructure only when it fails. That simple realization stayed with me long before I fully understood what Civil Engineering truly involved.

In 2020, I began my bachelor's degree in Civil Engineering. At that point, pursuing a master's degree was never part of the plan. My goals were straightforward: understand the fundamentals, gain practical experience, secure a stable career, and contribute meaningfully through my work.

To me, that seemed enough.

As my undergraduate studies progressed, however, one area of Civil Engineering continually drew my attention, transportation infrastructure, particularly roads and pavements.

At first glance, a road appears to be nothing more than asphalt stretched across the ground. In reality, it is an intricate engineering system. Much like a carefully layered cake, every layer beneath the surface serves a specific purpose. If one layer fails, the entire structure is compromised.

But what fascinated me most was not the engineering itself.

It was what roads represent.

A road connects a child to school.

It connects an ambulance to a hospital.

It connects people to jobs, businesses to markets, and families to opportunities they might never have reached otherwise.

Infrastructure is more than concrete and asphalt, it is access.

Yet many communities remain disconnected, not because they lack potential, but because they lack infrastructure. Roads do not simply appear where they are needed. They must be planned, funded, constructed, managed, and maintained throughout their lifespan.

That realization gradually shifted my interest beyond structural design. I became increasingly curious about how infrastructure projects are executed, managed, maintained, and ultimately experienced by the people they serve.

Several experiences during my undergraduate years strengthened that curiosity.

Even before formally beginning my degree, my uncle asked me a question that seemed simple at the time:

"Why don't Civil Engineering students take initiative within their own colleges?"

Every educational institution constantly renovates buildings, expands facilities, and upgrades infrastructure. Yet the very students studying Civil Engineering are rarely involved in those projects.

That question stayed with me.

Later, I collaborated with students from the Electronics Engineering department to develop a smart parking system for our college using IoT technologies. We designed a reservation-based parking solution that improved parking management on campus. It was not a large-scale infrastructure project, but it demonstrated something important to me, that classroom knowledge could solve real problems when applied creatively.

During my final year, another opportunity expanded my perspective even further.

Working alongside my professor, the State Police, and the Department of Roadways, I participated in collecting Pavement Condition Index (PCI) data and helped develop a Python-based AI model that predicted pavement deterioration and prioritized maintenance activities.

For the first time, I witnessed how infrastructure decisions extend far beyond engineering calculations. Every maintenance decision involved balancing data, field conditions, budgets, public safety, traffic demands, and limited resources.

Civil Engineering was no longer just about designing structures.

It was about making decisions that affect thousands of people every day.

These experiences also revealed something else.

My undergraduate education had given me a strong technical foundation, but it naturally had its boundaries. Design calculations, laboratory experiments, and theoretical models are essential, yet they cannot fully capture the uncertainties of construction sites or the complexity of managing large infrastructure projects.

Real projects involve changing weather, unexpected site conditions, stakeholder expectations, financial limitations, government regulations, and countless human decisions.

I realized I wanted to understand Civil Engineering from a broader perspective, not only how infrastructure is designed, but how it is planned, executed, managed, maintained, and continuously improved throughout its life cycle.

That realization led me toward Construction Management.

During my junior year, another question quietly emerged:

Is this enough?

For the first time, I seriously considered pursuing graduate studies.

Many engineering students in India naturally prepare for GATE. I considered that path too, but I was honest with myself. It did not align with the way I wanted to learn or the type of career I envisioned. I was looking for an education that emphasized application, research, interdisciplinary collaboration, and exposure to different ways of solving problems.

Conversations with my uncle, the same person who first challenged my thinking years earlier, reinforced that perspective.

Gradually, my attention shifted toward the United States.

Initially, the reasons were academic. Advanced research facilities, emerging technologies, flexible curricula, and opportunities to collaborate with people from diverse backgrounds made graduate education in the U.S. particularly attractive.

But once I arrived, I realized that education was only one part of the experience.

Living in the United States taught me independence in ways no classroom could. Managing academics while balancing responsibilities, adapting to unfamiliar environments, working with people from different cultures, and making decisions on my own fundamentally changed how I think.

It taught me flexibility.

It taught me accountability.

Most importantly, it taught me that learning extends far beyond earning a degree.

Today, when I reflect on this journey, I see that none of these experiences happened exactly as I had planned.

Yet each one prepared me for the next.

If I return to this piece years from now, I hope I remember one thing above everything else:

I did not choose Civil Engineering for titles, prestige, or recognition.

I chose it because I wanted to understand how the built environment quietly shapes people's lives.

I wanted to contribute to something larger than myself, something that improves communities not through headlines, but through everyday reliability.

The future remains uncertain, and I know my career will continue to evolve. But one principle has remained constant throughout every stage of this journey:

Keep learning.

Respect people.

Stay curious.

Remain involved.

Contribute wherever possible.

I have come to believe that careers are not built by perfectly following a plan. They are built by remaining open to opportunities, asking better questions, and allowing experiences to shape your perspective.

Looking back, every decision I made had a reason.

Looking forward, I trust that the next one will too.