Midwest Research Computing and Data Consortium
This is a series where we delve into the experiences of participants in the Student Experience Program (SEP), which pairs students with mentors and introduces them to the field during the Annual Networking Meeting. This year, six students from four institutions participated. Below is a list of the students, followed by their responses:
ABRAR: I applied to the Student Experience Program because I wanted to connect my academic work in High-Performance Computing (HPC) with the real-world needs of the research computing and data (RCD) community. My research focuses on tools like power-aware schedulers and edge autotuners, but I wanted to see how this work fits into the bigger picture. MWRCD’s focus on building a regional network of professionals stood out to me. The in-person retreat seemed like a great chance to make meaningful connections. I liked the idea of student-led panels and co-presentations with senior professionals. These activities support both learning and career growth. I saw the program as a way to grow my network, get mentorship, and understand what it really takes to succeed in the RCD field.
DALÍ: I am currently a third-year student in the Systems Biology and Bioinformatics PhD program with a background in biochemistry. Since my computational experience has come entirely from my PhD training rather than my prior education, I wanted to explore what career paths might be available for someone with my trajectory. This program offered an accessible way to learn about different professional options and the skills needed to succeed in them.
DUNG: It was curiosity. I had used the HPC platform in a few of my classes at CWRU, but I didn’t really know what it was or how it worked behind the scenes. When I saw the SEP opportunity, it felt like a chance to finally understand all the engine going on under the hood. It seemed exciting and different from what I usually see in class.
MEHMED: As someone who has worked at the in high-performance computing (HPC) support, done research for several years, and attended the MWRCD last year, I was very keen on applying for the Student Experience Program again to attend the consortium and catch the latest trends and emerging advancements within the field. I’ve been supporting users at Advanced Research Computing at the University of Michigan since my freshman year, while also leveraging those same clusters for my own machine learning research. I also applied to the SEP because I wanted to step beyond the walls of my university and see how other institutions approach research computing, to hear the stories of people building and maintaining these systems, and better to understand the evolving landscape of HPC across the Midwest.
ABRAR: The retreat was full of great experiences, but two conversations really stood out. First, I spoke with Dr. Scott Hampton from the University of Notre Dame. His career path was not straight, and he shared how being open to new opportunities helped him grow. He reminded me that soft skills matter a lot, like writing a strong cover letter, and that persistence is key. Second, I talked with Corinne Adams from the University of Michigan. She was honest about how job descriptions can be different from the actual day-to-day work. She encouraged me to explore internships to better understand different roles. Her advice to “be true to yourself” stuck with me. These conversations helped me see that technical skills are important, but relationships, flexibility, and self-awareness are just as critical for success.
DALÍ: I was genuinely surprised by how diverse the computing field is, both in terms of career roles and the educational backgrounds represented. I spoke with professionals who transitioned from research to computational support roles for reasons ranging from career satisfaction to family responsibilities. Others came from fields like physics, chemical engineering, even philosophy, yet found meaningful work in computational research. Another thing I appreciated was that the organizers introduced the student participants to the broader group right away. It broke the ice and made it much easier to approach people and start conversations. One conversation that stuck with me was with Dr. Djohari, who explained how he pivoted from postdoc research to advanced research computing because he wanted more rewarding work with faster timelines and broader impact. This is certainly something I can relate to. Conversations like that showed me that career paths can be much more flexible than I had assumed.
DUNG: I was surprised by how wide-reaching the HPC community is. I always thought of it as something super technical and niche, but it actually connects people from research, data centers, and industry. The session that really stuck with me was “Quantum Computing at Cleveland Clinic.” I didn’t expect to hear about quantum tech being used in healthcare, and it made me realize how fast things are changing and how important it is to stay aware of those intersections.
MEHMED: This year’s consortium reminded me that the research computing ecosystem is as much about people as it is about machines. One moment that really stood out was the mentorship I received from Shawn Slavin, whose career arc from astronomy to RCD gave me a new perspective on how technical and human adaptability intertwine. He spoke about staying curious, embracing flexibility, and the importance of maintaining relationships, which I know will be ever so important as I start grad school next semester. Session-wise, the keynote on Quantum Computing at Cleveland Clinic was unforgettable. It highlighted how HPC is increasingly collaborative, interdisciplinary, and medically impactful. I also really enjoyed the breakout session on Security & Compliance for DoD Research, a very thoughtfully designed, discussion-based session that unveiled the secrets of how universities are proactively building infrastructure for secure science.
ABRAR: The program gave me the confidence to connect my HPC work with real-world problems. After the retreat, I took a more interdisciplinary approach to my research. For example, during my internship at NCAR, I worked on an environmental data system using LoRa networks. I combined my HPC background with atmospheric science. Dr. Hampton’s advice made me feel confident about exploring areas outside my main field. Corinne’s focus on hands-on experience also made me value my work with devices like the Raspberry Pi and Jetson Nano more. Now, my research goals include building software that is not only efficient but also practical and usable in real-world, low-resource settings.
DALÍ: It opened my eyes to career options I would have previously dismissed as “out of reach.” Before, I would have assumed certain computational or research computing positions required a background I did not have. After this experience, I see that the skills I’ve built in my PhD are in demand and can be marketed effectively for roles beyond traditional academia.
DUNG: Talking to people at the retreat and during SEP made a big impact. Everyone had such different paths and goals, and hearing their stories helped me think more about what I want to do long-term. As a data science major, most of what I’ve learned is on the application side. SEP gave me a glimpse of the infrastructure and deeper systems side which is something I hadn’t really seen before.
MEHMED: SEP helped reframe how I view my own work, not just as code or models, but as part of a larger, distributed system of people, platforms, and priorities. I left the consortium with an even deeper understanding and appreciation for the sometimes invisible labor that supports academic discovery. Conversations with mentors and professionals helped me think more critically about what it means to build sustainable, secure, and user-friendly research environments. As someone pursuing work at the intersection of AI and infrastructure, that shift in perspective is invaluable.
ABRAR: The biggest skills I gained were not technical; they were professional.
DALÍ: I did not realized how many high-performance computing centers exist around the country and globally. As someone who is not from Ohio, it was reassuring to see that opportunities in this field are not limited to one location. The program also gave me a clearer picture of how HPC resources are managed, who maintains them, and what skills are necessary to use or support them effectively.
DUNG: Two big things are collaboration and awareness. I didn’t realize just how collaborative HPC work is. No one builds these systems or runs big data projects alone. And I started thinking more about the ethics of data: how it’s used, who it affects, and the responsibilities that come with working in this space. It’s not just technical stuff but rather human too.
MEHMED: Beyond the technical, what I gained most from SEP was a framework for thinking about career development in research computing. Listening to professionals talk candidly about their paths, which varied from startup pivots to unexpected academic turns, it all helped me realize that curiosity and initiative matter just as much as credentials (also networking). I also walked away with a better understanding of compliance frameworks like CMMC, the organizational challenges of resource allocation, and the ways institutions are tackling cybersecurity and access in HPC environments. These insights are difficult to pick up in a classroom or lab, and they’ve already proven useful in how I approach both support and research tasks, or more so helped me understand the bigger picture of everything.
ABRAR:
DALÍ: Take full advantage of the networking opportunities. Everyone I met was open, approachable, and willing to share career advice. For students who are not naturally comfortable networking, this program offers a low-pressure environment to practice those skills while also learning about the diversity of career paths in research computing. As for improvements, I honestly think the structure works well as it is. The intentional introductions at the beginning made it easy to start conversations, and the mix of technical and career-focused discussions kept things engaging.
DUNG: Jump in fully. Everyone I met was super approachable and happy to share their time and stories. Don’t be afraid to ask questions or say you don’t know something as that’s kind of the point. Even if you’re unsure whether this is the right fit, you’ll learn something valuable just by showing up and being open.
MEHMED: Lean into the people. The presentations are valuable, but the real gold comes from the side conversations, the hallway chats, the coffee breaks, the post-panel questions. Literally everyone I talked to seemed happy to be approached and it was a beneficial experience every time. Everyone you meet has a story, and those stories are interesting and contain hard-earned lessons that you can truly appreciate and apply to your life. One suggestion I’d offer: introduce a bit more unstructured networking time, especially during the second day. Some of the best interactions I had came during casual moments, and it would be great to build more space into the schedule for those spontaneous connections to form. A casual roundtable or “mentor mingle” could go a long way.
ABRAR: The SEP has had a big impact on my future plans. Academically, I’m more focused on doing research that solves real problems and helps others. Professionally, I now see myself working at a national lab or university RCD center, where I can build tools that support science. I also feel like I’m now part of the RCD community, not just a student anymore. I want to give back by mentoring others and working on shared challenges. This experience was a turning point that helped me grow from a student into a future professional.
DALÍ: This experience gave me the confidence to consider roles in research computing that I would have overlooked before. I now see how to highlight the skills I’ve gained in my PhD and translate them into roles outside traditional research. It broadened my career perspective and made me aware of opportunities I would not have otherwise explored.
DUNG: It gave me a better sense of direction. Talking with people who’ve done really cool things with their careers helped me imagine what’s possible. I’m still figuring things out, but SEP definitely shifted how I think about data, tech, and my own path going forward.
MEHMED: As I have officially graduated and will be moving onto grad school, I will unfortunately have to leave my part-time job at Umich ARC. So I do not know how much my involvement will be on the support side, but I know I will continue to be a heavy user. One of the biggest takeaways for me is that contributing to research computing doesn’t always mean being a faculty member or developer; it can also mean being a connector, a mentor, or a systems thinker. As I start my Master’s program, I hope to carry forward not just technical goals, but how I can simultaneously contribute meaningfully to the research computing community in the long term.