My Engineering Journey So Far
At Bennett, I leaned into that curiosity through student organizations. As General Secretary of the ACM student chapter and Chairperson of the Quantum Computing Club, I ended up doing a lot more than just attending events. I helped organize talks, mentored peers, and ran nerdy deep-dive sessions on topics like post-quantum cryptography and trusted execution environments. That turned into actual research projects: a comparative analysis of pre- and post-quantum encryption algorithms and a review of advances in TEEs for blockchain security. Those experiences made me realize how much I enjoy both research and explaining technical ideas in a way that other people can actually use.
Transferring to Iowa State University for my junior year was a turning point. I was the first student to do that partnership program from Bennett, which meant stepping into a new continent, a different academic system, and a place where I suddenly had to choose my own courses instead of following a fixed curriculum. My first semester at ISU was rough, I was completely used to the Indian system, where expectations and paths are more rigid. Instead of treating that as a vague “culture shock,” I ended up approaching it the way an engineer approaches a problem: I met with advisors, watched how my classmates managed their workloads, and iterated on my study habits until I found a rhythm that worked. That experience pushed me to take responsibility for my own learning in a much more deliberate way.
One of the biggest shifts at ISU was my growing interest in embedded systems. I bought an ESP32-S3 mostly out of curiosity and started teaching myself how to actually make it do something meaningful. That self-learning spilled into projects like an automotive CAN-bus telemetry system (“CANary”) and a motion-triggered bird feeder monitor (“PerchGuard”), where I had to combine low-level communication protocols, edge processing, and practical constraints like power usage and responsiveness. None of that was “required” in class; I learned machine learning basics, embedded C, and networking details because I wanted my ideas to work in the real world, not just on paper. Similarly, my earlier work on encryption and security came from realizing that non-technical people are extremely vulnerable online simply because they don’t understand what’s happening behind the scenes, so I tried to fill that gap with projects and explanations aimed at everyday users.
One of my favorite examples of designing and integrating a system was our Wi-Fi optimization and router placement robot. I was responsible for the entire user interface and the overall integration of the subsystems. The GUI had to do more than just “look nice”, it needed to stay perfectly in sync with the robot’s movement, show its real-time location, and generate a heatmap of Wi-Fi signal strengths as it scanned. For the demo, the driver wasn’t allowed to look at the robot directly, so the GUI effectively was their eyes. That meant any mismatch between what the robot was doing and what my interface showed would immediately break the illusion and the usefulness. I spent nights tuning the data pipeline between the robot and the UI, dealing with limited location information, smoothing out timing issues, and making sure that the user could intuitively understand what was happening. That project taught me a lot about system-level thinking: it’s not enough for each individual component to work; the entire experience has to make sense to the person using it.
Alongside the technical work, communication has been a constant theme in how I operate in teams. Whether it was coordinating tasks, mediating small conflicts, or helping teammates articulate their ideas during presentations, I naturally drifted toward roles that involved organizing and translating. I’ve seen how a lack of clear communication can sink a project, so I put real effort into making expectations explicit and making sure everyone knew what they were doing and why. That made meeting deadlines much less chaotic. On the written side, I’ve always liked creating technical content for non-technical audiences, from my “Quantum Computing for Everyone” and “Personal Cybersecurity” web essays to documentation I wrote back in ACM and the quantum club. Even in my operations and technical content internship at Horse’s Mouth, a lot of my impact came from writing and structuring content that actually reached and engaged people, not just existing as jargon on a page.
My ethics course at ISU pushed me to zoom out and think about the larger consequences of my future work as an engineer. For my final case study, I wrote “Algorithmic Ethics and Human Rights: An Examination of Meta’s Role in Global Conflicts,” where I analyzed how Facebook/Meta’s algorithms influenced real-world harm in Myanmar, Ethiopia, and the Israel-Palestine conflict. I used frameworks like consequentialism, stakeholder ethics, and a human rights lens to examine how seemingly “neutral” algorithmic decisions led to amplified hate speech, misinformation, and, ultimately, violence and displacement. That project was personal in a way I didn’t expect; consuming constant negative news, especially about war and injustice, had already affected my own mental space. Writing the paper helped me understand that as engineers, we don’t get to hide behind “unintended consequences.” If we design systems that operate at global scale, we have a responsibility to monitor their impact and build guardrails to reduce harm. That assignment is one of the clearest examples where my coursework directly deepened my sense of ethical and professional responsibility, especially in a global and societal context.
Being an international student has also expanded my understanding of what “global context” actually means in day-to-day engineering. Back home, people were more relaxed about coursework, and the intensity level felt very different. At ISU, I’ve seen classmates pour huge amounts of time and energy into projects, research, and internships. That contrast forced me to raise my own standards and broaden my perspective. It’s made me more aware of how different educational cultures shape expectations, how teams with mixed backgrounds think about problems differently, and how engineering decisions can’t be separated from the environments and societies they emerge from.
Across both universities, a big part of my growth has come from stepping into leadership and community roles. As General Secretary of the ACM student chapter, Chairperson of the Quantum Computing Club, and later a student leader in other spaces, I discovered that I genuinely enjoy mentoring and teaching. It’s one thing to understand something yourself; it’s another to break it down so that someone younger or less experienced can build on it. That’s where I really saw the connection between communication (ABET 3) and lifelong learning (ABET 7): every time I teach something, I’m forced to refine my own understanding and stay up to date. These roles also made me more intentional about seeking out external resources, research papers, technical documentation, expert talks, and even human rights reports in the case of my Meta ethics work, rather than waiting for everything to be handed to me in a classroom.
If I had to summarize what I’ve learned about myself through this whole journey, I’d say my main strengths are coordination, creative problem-solving under constraints, and a stubborn curiosity. I like being the person who pulls the pieces together when a project seems stuck, especially when resources are limited or the problem looks unsolvable at first glance. I also know now that I’m happiest when I’m learning something new and then turning that knowledge into something concrete, whether that’s a case study on algorithmic ethics, an encrypted system, or a quirky embedded device that quietly does its job at the edge.
Looking forward, I plan to go to graduate school in computer engineering, likely focusing on edge computing in the near term and eventually moving toward quantum computing hardware. The big, maybe slightly dramatic, goal is to work on something that outlives me, whether that’s a new algorithm, a hardware design, or an application of quantum computing that genuinely benefits humanity. The more I’ve learned, the more obvious it’s become that engineering is not static. Technologies, threats, and societal needs are constantly evolving, and if I want to contribute meaningfully, I’ll have to keep evolving too. My undergraduate journey, from quantum clubs in India to embedded systems and ethics case studies in the U.S. has convinced me that I’m ready to take on that responsibility: to communicate clearly, to think ethically about the systems I build, and to keep learning long after the degree itself is over.