When I first joined the Grand Challenges Scholars Program, I saw it as something that would complement my computer science degree. I thought it would broaden my coursework and give me additional perspective. I did not realize that it would slowly reshape how I understand engineering itself.
Over time, GCSP became less about completing competencies and more about asking better questions. It pushed me to think beyond functionality and performance. It made me pause and consider who depends on the systems I build, what happens when they fail, and whether they truly serve the people they are meant to support.
At first, the five competencies felt independent from one another. As I moved through each experience, I began to see how deeply connected they were. Each one approached responsibility from a different angle, but they were all guiding me toward the same mindset.
GCSP reshaped how I evaluate my own work. Earlier in my degree, I focused on whether my code worked correctly. Now I also consider whether it will remain reliable over time, whether it protects users, and whether it respects the realities of those who interact with it.
This perspective prepares me directly for my professional career in software engineering. I will be working on large scale systems where trust and long term stability are essential. GCSP helped me see engineering as a responsibility that extends beyond technical execution.
The Grand Challenges Scholars Program has been one of the most formative parts of my education at ASU. It encouraged reflection at every stage instead of allowing experiences to pass without deeper meaning. It connected research, service, culture, policy, and entrepreneurship into a coherent whole.
Most importantly, it helped me grow into an engineer who thinks about impact before implementation. That shift in mindset is something I will carry with me long after graduation.
Looking back, GCSP did more than broaden my education. It shaped how I think, how I build, and how I hope to contribute in the future.
Talent
Through my senior capstone with Qualaces Inc, I worked on real product features such as secure test plan ingestion and structured team onboarding. The poster and final presentation included in this portfolio reflect that work. What stayed with me most was not only the technical growth, but the realization that backend decisions affect user trust in very visible ways. Privacy, structure, and reliability are not abstract concepts. They are felt by real teams who depend on the system.
Social Consciousness
In EPICS, working on the Offline Digital Library for the Jirani Project in Kenya changed how I view service oriented engineering. The design documents and deliverables included here show the technical side of the project, but the deeper lesson was about responsibility. Building something for a community means thinking about durability, ownership, and long term sustainability. It requires humility and careful listening.
Multicultural
Courses such as STS 332 and COM 263 encouraged me to step outside my technical comfort zone. Through analytical briefs and my presentation on food insecurity among international students, I began to understand how culture, policy, and identity shape lived experience. I learned that systems that appear neutral can affect groups very differently. This awareness now stays with me whenever I think about design decisions.
Multidisciplinary
FSE 150 and SOC 334 shaped how I approach complex problems. The Future Solutions Project and my research essay on algorithmic management pushed me to consider stakeholders, long term consequences, and ethical tradeoffs before proposing solutions. These experiences trained me to think in systems rather than isolated features.
Entrepreneurship
Through FSE 301, I learned to treat entrepreneurship as an evidence based process. The pitch deck, customer conversations, and presentation videos in this portfolio show how I tested assumptions, revised my message, and connected the idea to real user value
My chosen theme, Joy of Living, centers on improving everyday life through systems that increase stability, access, and trust. Each competency contributed to that focus in a meaningful way.
Capstone strengthened stability and privacy in digital workflows.
EPICS increased access to learning in a resource limited setting.
Multicultural and multidisciplinary courses deepened my understanding of fairness, context, and unintended consequences.
Entrepreneurship reminded me that systems must fit real human needs to truly improve daily life.
When I step back, I see that all of these experiences point toward the same goal. A well designed system should make life feel more secure, not more fragile. It should quietly support people in the background. That understanding has become central to how I define impact.