Reflections on My Year as GDG on Campus Lead
As I look at my Certificate of Appreciation from Google Developer Groups, I'm reminded that leadership isn't just about titles—it's about transformation. Both for the community you serve and for yourself.
The Challenge of Starting
When I first stepped into the role of GDG on Campus Lead at the University of Embu, I thought I knew what I was getting into. Organise some tech talks, maybe a few workshops, and connect students with Google technologies. Simple enough, right?
I couldn't have been more wrong.
The reality hit me during our first event planning meeting. Staring at a room of eager students with diverse skill levels, different interests, and varying degrees of confidence, I realised that my job wasn't just about Google technologies—it was about people. It was about creating an environment where a first-year computer science student felt comfortable asking questions alongside a final-year developer building their capstone project.
The Growth in Complexity
What started as "let's do some Flutter workshops" evolved into something much richer. We found ourselves navigating questions that went beyond code:
How do you make technical content accessible to students who are still finding their footing in programming?
How do you balance structured learning with the organic curiosity that drives real innovation?
How do you build confidence in students who see technology as intimidating rather than empowering?
Each event taught me that technical leadership is deeply human work. The best workshops weren't just about Firebase or Flutter—they were about creating moments where students realised they could build things that mattered.
The Unexpected Lessons
Leadership is listening. The most impactful changes we made came from really hearing what our community needed. Sometimes that meant pivoting from a planned AI workshop to a basic Git tutorial because that's where the real knowledge gap was.
Consistency beats intensity. The students who benefited most weren't necessarily those who attended our biggest events, but those who engaged regularly with our smaller, ongoing initiatives.
Your role is to make yourself unnecessary. By the end of the year, seeing other students step up to lead sessions and mentor their peers was more rewarding than any certificate.
The Technical and the Personal
This role taught me to bridge worlds—translating complex technical concepts into engaging learning experiences, connecting academic theory with practical application, and most importantly, helping students see themselves not just as consumers of technology, but as creators.
The Google Developer ecosystem provided incredible resources, but the real magic happened in the spaces between the official curriculum.
Looking Forward
As I transition from this role, I'm carrying forward a deeper understanding of what the developer community means. It's not just about the latest frameworks or trending technologies—it's about fostering environments where curiosity thrives, where failure is reframed as learning, and where everyone has the support they need to grow.
To future GDG on Campus Leads: embrace the complexity. Your role is part educator, part community builder, part mentor, and part student. The technical skills you'll develop are valuable, but the leadership skills you'll gain are transformative.
The developer community needs leaders who understand that our most important work happens not in the code we write, but in the opportunities we create for others to discover what they're capable of building.
Gratitude and Recognition
This journey wouldn't have been possible without an incredible support system:
My Core Team
Google Developer Experts (GDEs)
Regional Community Managers
University of Embu
Community Contributors
Leadership in tech communities is never a solo effort—it's the result of an ecosystem of support, mentorship, and collaboration.
Thank you to Google Developer Groups and the entire community that made this year of growth and impact possible.
