Graduate students are always told that they need to network. The advice usually comes with a familiar template: attend conferences, introduce yourself to important people, connect on LinkedIn, and follow up afterward.

While this template can be useful, it should not be conflated with the purpose of networking, nor should it be treated as the only way to build professional connections.

This naturally begs the question, what is the purpose of networking?

I came to Purdue from India with an undergraduate degree in Computer Engineering, and I graduated from the Master of Engineering in Robotics program in 2026. Before starting graduate school, I knew I was interested in robotics, autonomy, and intelligent systems, but I also knew that robotics is not something you truly understand only by studying equations, watching lectures, or reading documentation. You have to build, test, break things, debug them, and then try again. That is where my project-based coursework made the biggest difference in my graduate experience.

At the core of every engineering solution is iteration. I see most of my projects as works in progress, and that bothered me for a while. Even when some of them were already deployed and used by other people, there was always more to improve.