becoming knight hacks vice president

starting in january 2026, the title changed from hackathon organizer to vice president at knight hacks. on paper that looks like a clean step up, but what it really meant was taking on a wider share of the responsibility for how the org feels, how the team moves, and how people experience the community when they first show up.

i had already spent a lot of time learning the rhythm of the club from the organizer side: logistics, event planning, execution, and the thousand small details that make a student organization feel real instead of improvised. stepping into vp meant zooming out and thinking less about a single workstream and more about how the whole thing holds together.

the promotion only made sense because the work had already been happening. organizing hackathons teaches you quickly that community leadership is not abstract. it is calendars, follow-through, communication, recruiting, momentum, and the ability to keep a room pointed in the same direction when everybody is busy.

that stretch as an organizer made the next step feel earned. it taught me how much trust matters in student leadership, especially in a club where the experience should feel open and exciting for new builders while still being rigorous enough for the team running it.

the part of the role that matters to me most is leverage. vice president should mean making it easier for the rest of the team to do their best work, not just being closer to big decisions. that means cleaner operations, clearer ownership, better support for directors and organizers, and more intention around culture.

knight hacks has always been at its best when it feels ambitious without becoming closed off. i want the leadership layer to protect that balance: high standards, low ego, and a community that still feels reachable to the first-time hacker who walks in not knowing anyone.

becoming vice president is not just another line on a resume. it means getting to help shape one of the communities that has had a real impact on how i grew as a builder and teammate. student organizations can change the trajectory of a college experience when they are run with care, and knight hacks has been that kind of place for a lot of people.

i care about the role because it sits at the intersection i like most: technical culture, event systems, and people. it is leadership work, but it is also product work in a different form. the product is the environment, and the goal is to make it easier for other people to find momentum.

the next chapter is about depth, not just scale. i want the org to keep getting better at onboarding new members, developing future leaders, and creating events that feel polished without losing the energy that made people care in the first place.

if the role goes well, the result should not just be bigger events. it should be a stronger team, a healthier culture, and more students leaving knight hacks with the feeling that they belong in rooms where ambitious technical work happens.