What?

In the summer following my freshman year at the University of Cincinnati, I served as a Student Orientation Leader (SOL)—a role that turned out to be one of the most transformative experiences in my college journey thus far. Initially, I was hesitant to apply. As someone who had just begun adjusting to a new cultural environment and was still grappling with self-confidence and introversion, the idea of being a visible and vocal leader was intimidating. Nonetheless, I took a leap of faith, completed four rounds of interviews, and ultimately accepted the SOL position over a summer research opportunity.

The first half of the program involved rigorous training covering campus resources such as the Women's Center, LGBTQ+ Center, Accessibility Resources, and the Rec Center. Once orientation officially began, our team of 26 SOLs helped welcome and guide over 8,000 incoming students and their families. My responsibilities included facilitating discussions, conducting campus tours, supporting new students' transition into college life, and helping plan and execute daily orientation activities. The work was intense—early mornings, long days—but incredibly fulfilling.

So What?

This experience catalyzed profound personal and professional growth. The structured nature of our days—from waking up at 6 a.m. to clocking out in the evenings—instilled in me discipline and grit. More importantly, it pushed me to confront the social anxieties I carried into college. Before SOL, I was shy and unsure of myself in group settings, especially when surrounded by people from different backgrounds. But over the summer, I became someone who could confidently speak to large groups, connect with students from all walks of life, and offer guidance with clarity and compassion.

Professionally, this was my first experience where I recognized the power of effective communication—a skill that's often overlooked in the world of software engineering. As engineers, we rarely work in isolation. Whether it's collaborating on code, debugging with teammates, or presenting our solutions to stakeholders, communication is essential. This role made me a better communicator and team player—both of which are critical traits for any aspiring engineer.

On a more personal note, the SOL experience gave me some of my closest friendships. The bonds formed during those long training days and busy orientation sessions were strong and genuine. I'll even be living with a few of my fellow SOLs in the coming year—something I never would have imagined just a year earlier.

One of the most validating moments came when our efforts were acknowledged by UC President Neville Pinto during the Cincinnati vs. EKU football game. That recognition underscored the impact we had not only on incoming students but on the university community as a whole.

Now What?

Looking ahead, the lessons I learned as a Student Orientation Leader will serve as a foundation for how I approach leadership, collaboration, and communication in every area of my life. I now seek out opportunities that push me beyond my comfort zone—whether that's taking on leadership roles in student organizations, presenting my work to technical audiences, or stepping up to mentor peers.

This experience has also shaped my long-term goal: to become a well-rounded software engineer who is not only technically proficient but also a thoughtful, communicative team leader. In the coming months, I plan to pursue more leadership opportunities, research experiences, and internships that allow me to further develop the human side of engineering. I believe that bridging the gap between technical skill and interpersonal excellence is what will set me apart.

Most importantly, this experience reminds me that growth is nonlinear and often requires risk. Accepting the SOL position—despite initial doubts—ended up being a defining moment of my college journey. Though I'm writing this reflection later than expected, the impact of that summer still shapes who I am today. And I know it will continue to influence the trajectory of my academic and professional life as I work toward becoming the kind of leader UC helped me discover I could be.

What?

Beginning in January 2024, I joined the BioRaMP (Biomedical Research and Mentoring Program) at Cincinnati Children's Hospital as a research assistant in the Heart Institute Research Core (HIRC) under the guidance of Dr. Danny Wu. This was my first formal research experience, and it became a pivotal moment in my academic and professional development. Our project focused on building the HIRC Connect Web Portal, a web-based tool designed to help clinicians and researchers store and access their project data more efficiently.

As part of a small team that included another undergraduate research assistant, two project managers, and Dr. Wu, I contributed to the portal's development using Python Flask, JavaScript, HTML, and CSS. Despite being relatively new to some of these technologies, I embraced the steep learning curve with enthusiasm. We structured our work using Agile project management—specifically the SCRUM framework—which involved regular stand-up meetings, sprint planning, and iterative development. These practices helped us stay user-focused and adapt continuously based on feedback from Dr. Wu and other stakeholders.

We presented our final progress and findings to other BioRaMP researchers at the end of the spring semester, formally concluding the program. The presentation highlighted how incorporating Agile methodologies and User-Centered Design (UCD) significantly improved our development process and client satisfaction—a relatively novel approach in clinical research software projects.

So What?

This experience marked a major shift in my confidence, technical abilities, and understanding of real-world research workflows. As my first role in research, I initially faced challenges with technical execution and communication. However, through ongoing collaboration, mentorship, and persistence, I grew into a reliable and valued contributor to the team. Over time, I was trusted with more complex responsibilities and became comfortable navigating code reviews, delivering progress updates, and leading discussions on technical trade-offs.

Professionally, this experience introduced me to health informatics, a field I hadn't previously considered but now see as a potential career path. The interdisciplinary nature of the work—where software engineering meets healthcare impact—was both inspiring and intellectually fulfilling. The use of Agile and UCD also reinforced my belief that successful software isn't just about writing code—it's about understanding and designing for the user.

Equally important were the lasting connections I built during this time. I developed strong relationships with my fellow intern, our project managers, and Dr. Wu himself. These connections extended beyond the BioRaMP timeline—I offered to continue working with the team over the summer (at ~10 hours/week), which eventually led to a paid research assistantship in Dr. Wu's lab during Fall 2024 (5 hours/week). The mentorship and trust I gained from this group has had a meaningful and ongoing impact on my college experience.

On a broader scale, this early research exposure has positioned me strongly for my future goals. Having hands-on research experience during my undergraduate years not only enhances my skillset but also strengthens my candidacy for competitive graduate programs, especially in engineering fields that value applied research.

Now What?

This experience has sparked a deep interest in pursuing the intersection of healthcare and technology. Moving forward, I plan to build upon the foundation laid by BioRaMP by continuing my involvement with the HIRC Connect project and seeking out other research opportunities that blend software engineering with real-world impact. I aim to take on more leadership responsibilities in future projects and explore opportunities for publication or academic presentation.

In parallel, I will continue honing my full-stack development skills and deepening my understanding of project management practices. I am actively pursuing internships in health tech and informatics that will allow me to apply my skills in professional settings while also gaining insights into industry practices.

Ultimately, I want to become an engineer who is not just technically capable, but one who leads with empathy, communicates effectively, and delivers user-centered solutions—especially in high-impact fields like healthcare. The BioRaMP program has been a major stepping stone in that direction, and I am grateful for the mentorship, skills, and clarity it has provided as I shape the rest of my undergraduate journey and beyond.

What?

In Fall 2024, I participated in the Innovation Challenge hosted by the Center for Entrepreneurship at the University of Cincinnati. As part of a two-person team, I conceptualized, built, and pitched an advanced digital soil meter that integrated multiple sensors—including NPK (Nitrogen, Phosphorus, Potassium), soil moisture, and light intensity (via BH1750). Our goal was to empower gardeners and small-scale farmers to monitor the health of their plants more effectively through a real-time data-driven platform.

We used an ESP32 microcontroller to collect sensor data, which we then transmitted using Arduino code to a custom-built web application. The web app itself was developed using React.js, Python Flask, and styled with Tailwind CSS. Once the data reached our Next.js-based frontend, it was cross-referenced with ideal growing conditions from a dataset specific to various plant species. Based on this comparison, the application would generate actionable insights to help users optimize their plant care—whether adjusting light exposure, nutrient levels, or soil moisture.

To validate the feasibility and potential of our solution, I sought feedback from industry experts, including Professor William Haekins (Assistant Professor of CS) and Dr. Jason Heikenfeld, a faculty entrepreneur who also serves as one of the founders of the Innovation Challenge. Their insights were instrumental in refining both the technical approach and the business model.

In addition to the technical implementation, I led the business and strategic development side of the project. This involved conducting due diligence on the agTech industry, analyzing competitors and identifying our differentiators, developing a scalable revenue model, and crafting a compelling pitch deck. We ultimately presented this pitch to a panel of local Cincinnati entrepreneurs.

So What?

This experience was a turning point in my growth as an aspiring founder and well-rounded engineer. On the technical side, I deepened my understanding of the Software Development Life Cycle (SDLC). There were moments when our data pipeline or visualization logic failed to operate as expected—like when our sensor data displayed erratic spikes due to faulty calibration, forcing us to pause development and reallocate time to debugging and testing. These roadblocks taught me to build in flexibility and contingency planning, which are crucial aspects of real-world engineering.

Working closely with my teammate showed me firsthand the value of collaboration in software development. From pair programming Arduino scripts to ideating interface features late at night, I saw how two minds could bring more resilience and creativity to the table than working solo ever could. This reinforced a principle I now carry into every team project: code might be written by individuals, but software is built by teams.

Equally important was the entrepreneurial exposure I gained. While working on the challenge, I was also undergoing a semester-long analyst training for Bearcat Ventures, UC's student-led venture capital fund. The Innovation Challenge gave me a space to apply that knowledge practically—from conducting TAM/SAM/SOM market sizing to critically evaluating financial projections. It made abstract venture capital concepts tangible and relevant, sharpening my ability to assess feasibility and impact—skills I now bring into startup evaluations at Bearcat Ventures.

Our pitch to the judges was well-received, especially in terms of product-market fit and usability. However, we were caught off guard during the Q&A session. We hadn't prepared well enough to answer detailed questions around market entry and technical robustness. That moment, though disappointing, taught us a valuable lesson: every assumption needs to be questioned, and preparation must go beyond the pitch deck. This insight will stay with me for any future competitions or startup endeavors.

Now What?

Looking ahead, this experience has reaffirmed my passion for entrepreneurship in technology, especially in domains where real-world problems meet smart, accessible solutions. As someone who aspires to launch a startup in the future, this challenge gave me early exposure to what it takes—from ideation and prototyping to stakeholder communication and investor-facing storytelling.

In the near future, I plan to pursue more innovation-oriented programs and explore interdisciplinary projects that blend AI, hardware, and full-stack development. I also intend to compete in additional pitch competitions and accelerator programs that help young founders refine their ideas and prepare for real market validation.

Beyond just skill-building, this experience helped me discover that entrepreneurship is not only about launching companies—it's about solving problems, building trust, and embracing the unknown. The feedback from mentors, the adrenaline of demo day, and even the post-pitch introspection are all part of the journey I hope to continue for many years to come.

Ultimately, this Innovation Challenge was more than a competition—it was a stepping stone toward the kind of impact I want to create in the world, both as a software engineer and as a future founder.

At Cal Hacks 12.0 in San Francisco, my team built memARy: an AI wearable on Snap Spectacles that captures what you see and hear, stores it as searchable memory, and lets you recall it through natural language. The idea started from a real problem (memory loss for Alzheimer's patients) and got selected for the Snapchat AR track out of hundreds of applicants. I teamed up with a friend from UC and two strangers from Discord; when one dropped, I went around pitching the idea in a room of 3,000+ hackers to find our fourth teammate.

The weekend was less about smooth building and more about figuring out what to do when nothing works. Venue wifi crashed, we bounced between SF and Berkeley, debugged hardware we'd never used, swapped our whole database stack hours before the demo deadline, and recorded our submission video in an Uber on the way back. We still placed 3rd in the Snap AR track. Right after, I got into the YC Cal Hacks afterparty (meant for Berkeley students) and talked to partners and builders I'd only seen online. Source code.

For my visual representation, I chose our demo video. It's the clearest proof of what we actually shipped when almost nothing was working.

For me, being a Global Citizen Scholar isn't just doing well in class. It's building something that could actually help people, showing up in rooms you weren't expected to be in, and keeping the team moving when the plan falls apart. That's what this experience reinforced.