
Turned 23 Today : My Journey From AWS Cloud Club Captain to AWS Student Builder Groups Leader
I turned 23 today. Looking back at the last year, AWS gave me much more than cloud knowledge. It gave me people, experiences, opportunities to speak and build, and eventually helped me understand why I enjoy Developer Relations so much.
Today, I turned 23.
Birthdays have this strange way of making you look backward before you start thinking about what comes next. When I looked back at the last twelve months, I realized how much had changed in a very short time.
Exactly one year ago, on this same day, I became a GDGC Lead. At that point, I knew I loved technology and communities, but I didn’t really know where any of it was going. I liked building things, organizing events, meeting developers, and explaining technology, but these still felt like separate interests.
Over the next year, those pieces slowly started connecting.
AWS became one of the biggest reasons why.
Not only because I learned more about cloud, but because the AWS community gave me opportunities to organize, volunteer, travel, speak, teach, meet builders, work with other communities, and understand what it actually means to build something for developers.
Looking back now, becoming an AWS community leader was never really about getting a title.
It was about everything that happened because I decided to keep showing up.

It Started With Wanting to Do Something More
When I first started becoming serious about communities, I wasn’t thinking about speaking at Community Days or bringing multiple AWS communities together.
I simply wanted students around me to experience technology beyond classrooms, assignments, courses, and certificates.
There is a very different kind of learning that happens when you meet someone who has actually built something, listen to the problems they faced, ask questions directly, and then go home wanting to try it yourself.
I wanted more students at my college to experience that.
That eventually led me toward AWS communities, and I got the opportunity to become an AWS Cloud Club Captain at my college.
Of course, getting selected felt amazing. But with time, I understood that getting the role was actually the easiest part. The real journey started after that.
A title gives you access to an opportunity. What you build with that opportunity is completely up to you.

My First AWS Student Community Day
One of my first major AWS community experiences after becoming a captain was AWS Student Community Day at Parul University.
I attended as a new captain, and I remember spending a lot of time simply observing how everything worked.
There were sessions, of course, but what interested me equally was what happened outside the sessions. I met other Cloud Club Captains, community builders, speakers, volunteers, and developers who were already deeply involved in the ecosystem.
I started noticing how easily conversations happened. Someone would be talking about AWS in one corner, another person would be discussing a project, and somewhere else two community leaders would already be thinking about collaborating.
That event helped me understand something important.
AWS wasn't only a platform where I could learn cloud services. There was an entire community around it where people genuinely wanted other builders to grow.
That made me want to become more involved.



Then I Saw the Other Side of a Community Event
The next important experience came with AWS Community Day Ahmedabad.
This time, instead of only attending, I volunteered.
That completely changed the way I looked at community events.
When you're attending, you mostly see the polished side. You see the stage, speakers, sessions, networking, food, booths, and everything happening on schedule.
When you're volunteering, you start seeing everything behind that.
There are people coordinating speakers, handling registrations, solving unexpected problems, directing attendees, checking rooms, supporting organizers, and fixing things that most attendees will never even realize went wrong.
I really enjoyed that side of community building.
It made me realize that a lot of meaningful community work happens without anyone posting about it.
Sometimes you're not on stage. Sometimes nobody even knows you solved a problem. But the event works because a group of people decided to take responsibility for it.
That became one of my earliest lessons in community leadership.



Community Connect — Collaboration Over Competition
I also had the opportunity to attend a Community Connect hosted by AWS User Group Vadodara, organized by Adit N Modi, Nirmal Pathak, and the team, with an inspiring opening keynote from MarĂa Encinar and Ridhima Kapoor.
The session brought together 22 community leaders and their members to openly discuss the real challenges of building and managing communities.
What stayed with me most was the idea of collaboration over competition. Instead of working in silos, we discussed how communities can support each other through shared events, resources, speakers, and opportunities.
I was representing AWS Student Builder Groups at BVM, GDG On Campus BVM, our Open Source Club, and MLSA, and it made me realize how powerful it can be when different ecosystems come together.
That experience strengthened one belief I still carry:
Communities grow stronger when they grow together.



Representing My Community at AWS Community Day Pune
Later, I attended AWS Community Day Pune while representing my Cloud Club.
It was my second AWS Community Day, but this one felt different because I was no longer attending only as a student trying to understand the ecosystem. I was starting to feel responsible for representing the community I was building back at college.
I even got the opportunity to step onto the stage and represent my community.
It may look like a small moment when I write about it now, but I remember how significant it felt at that time.
Only a few months earlier, I was watching community leaders and speakers and wondering how people reached that point. Slowly, I was becoming part of the same ecosystem myself.
The change didn’t happen overnight. It happened one conversation, one event, one volunteer opportunity, and one small responsibility at a time.



AWS Student Community Day CHARUSAT — Learning What Leadership Really Means
AWS Student Community Day CHARUSAT was particularly important for me because I got the opportunity to be part of a Cloud Captain Panel Discussion.
This time, the conversation wasn't only about AWS services or technical learning.
We discussed what it actually means to lead a student community.
I shared how we manage activities as leaders, how we plan sessions, coordinate with team members, keep students involved, work with speakers, and handle the situations where things don't go exactly according to plan.
I also spoke about something that had become a very real part of my own journey: handling multiple communities at the same time.
By then, I was already becoming involved in different developer ecosystems. Managing multiple communities sounds exciting from the outside, but it also teaches you quickly that leadership is mostly about prioritization.
Every community has different members, different goals, different expectations, and a different culture. You can't simply copy the same event or approach everywhere.
Sometimes leadership means being the person with the idea. Other times, it means stepping aside and helping somebody else's idea happen.
Sometimes it means speaking.
Sometimes it means listening.
And sometimes it means realizing that you cannot personally do everything.
Sharing those experiences at CHARUSAT was meaningful because I wasn't talking about theory. I was talking about things I was learning while actively trying to manage them myself.
That panel was another moment where I realized how much community leadership was changing the way I think.



AWS Student Community Day Amravati — When Speaking Became Personal
Another very important milestone was AWS Student Community Day Amravati.
I was invited as a speaker, and I also helped around the event as a volunteer.
My session was:
“Beyond the Cloud: How AWS Communities Shape Builders and Leaders.”
What made that session special to me was that it wasn't really focused on one AWS service.
It was about people.
I spoke about how communities create opportunities for students, why networking matters, why you should take initiative even when you don't feel completely ready, and how joining one community can sometimes completely change your journey.
Those were not things I had read in a textbook.
I was experiencing them myself.
Standing there and talking about community made me notice something else too: I genuinely enjoyed explaining things.
Not only technical concepts. I enjoyed explaining opportunities, sharing lessons, talking about mistakes, and helping someone understand what their next step could be.
That realization became very important later.



From Attending Sessions to Taking Them
Once I became more comfortable speaking, I started saying yes to more opportunities where I felt I could contribute.
I represented my community at GitHub Copilot Dev Days Vadodara, where I spoke about Copilot CLI and AI-powered developer workflows. I also spoke at GitHub Copilot Dev Days BVM, focusing on Copilot and developer productivity.
I delivered a session on Serverless Architecture with Cloud Club ANITS x Prismatica, where the goal was to take something that can initially feel complicated and make it understandable through practical examples.
Beyond the bigger events, I also started conducting sessions with different AWS Student Builder Groups.
Those sessions became very important to me because every audience was different. Sometimes I was speaking to students who already knew AWS. Sometimes I was talking to someone who had never opened the AWS Management Console before.
That forces you to change how you teach.
Sometimes the most rewarding outcome is one student staying back after the session and saying, “I finally understood this,” or asking you what they should build next.
Teaching also exposed my own gaps.
It's easy to finish a course and think you understand something. Try explaining that same concept to a beginner without hiding behind complicated terminology, and you'll very quickly discover what you actually understand.
AWS speaking opportunities made me a better learner because they forced me to understand things deeply enough to explain them simply.



From AWS Cloud Club Captain to AWS Student Builder Groups Leader
Then another chapter started.
AWS Cloud Clubs evolved into AWS Student Builder Groups, and I moved from being an AWS Cloud Club Captain to becoming an AWS Student Builder Groups Leader.
The name changed, but I think I had changed more than the program had.
When I first became a captain, the title itself felt like a big achievement.
By the time I became an AWS Student Builder Groups Leader, I had started looking at leadership differently.
It wasn't about adding another title beside my name.
It was about responsibility.
How do we help more students start?
How do we make technical sessions genuinely useful?
How do we collaborate instead of operating in isolation?
How do we create opportunities for students who might never walk into a major Community Day on their own?
And how do we build things that continue helping people even after an event ends?
Those questions eventually led to something much bigger.

AWS Summit Mumbai — Seeing the Community at a Much Bigger Scale
Soon after the transition from AWS Cloud Clubs to AWS Student Builder Groups, I got the opportunity to attend AWS Summit Mumbai.
For me, this was very different from the student community events I had attended before.
The scale was much bigger, the conversations were different, and there were developers, builders, community leaders, customers, AWS teams, and people from so many different backgrounds all in the same place.
But what made the experience even more special was that I wasn't there only as an attendee.
I also got the opportunity to volunteer at the Developer Booth, supporting both AWS Builder Center and the AWS User Group community.
That meant I could spend time talking directly with developers, helping people discover community resources, interacting with builders who were exploring AWS, and seeing how developer-focused programs are represented at a large event like AWS Summit.
It was one of those experiences where I was learning simply by being present.
I also got to meet so many fellow captains and Student Builder Group leaders in person.
Some were people I had only spoken with online before. Others were completely new connections.
We talked about what everyone was building in their colleges, the challenges they were facing while running communities, event ideas, collaborations, and what we could potentially do together.
That part mattered a lot to me.
Community feels very different when a name you have seen in a group chat suddenly becomes a real conversation over coffee at an AWS event.
I also met many completely new people from the broader AWS ecosystem, and those conversations helped me understand how much bigger the community really is beyond one college, one city, or even one student program.
Volunteering at AWS Summit Mumbai gave me another perspective on Developer Relations as well.
I was watching how developers discover resources, what kind of questions they ask, what attracts them to a booth, and how a simple conversation can help someone find the right community, learning resource, or next step.
It reminded me again that helping developers doesn't always have to begin with a stage or a technical session.
Sometimes it starts with simply being there when someone asks:
“Where should I start?”
AWS Summit Mumbai was one of those moments where I could clearly see how my journey had expanded.
I had started by trying to build something useful inside my college.
Now I was standing at one of the biggest AWS events in the country, volunteering for AWS Builder Center and the AWS community, meeting builders from everywhere, and representing the same student ecosystem that had helped me start.
That felt special.



AWS Gujarat Students Builder Week
One of the things I'm most proud of from this year is AWS Gujarat Students Builder Week 2026.
The idea started with a simple observation.
There were AWS student communities operating across different colleges and cities in Gujarat. Everyone was organizing events, running sessions, and trying to help their own students.
But we started wondering what would happen if we stopped thinking only at the college level.
What if multiple student communities actually built something together?
That thought became a seven-day initiative.
AWS Gujarat Students Builder Week brought together 14 AWS Student Builder Groups, 3 AWS User Groups, and students from 14 colleges across Gujarat.
Behind the initiative was a five-member core team along with 16 volunteers.
For seven days, we ran sessions around different AWS topics with speakers and community members contributing their time and knowledge.
On the first day, around 2,500+ students joined live, and hundreds continued joining across the sessions that followed.
Seeing that number was exciting.
But when I think about Builder Week now, attendance is honestly not the first thing I remember.
I remember the collaboration.
Student leaders from different colleges helping each other.
Volunteers handling problems together.
Speakers joining because they wanted students to learn.
Different communities sharing the same initiative instead of competing for attention.
And students coming back the next evening because they wanted to learn the next topic.
That experience gave me one of my strongest community lessons so far:
communities become much more powerful when people stop trying to own everything individually.
Builder Week wasn't something one person could have created.
That was the entire point.
It worked because many people decided to build it together.

Community Work Didn't Stop There
Becoming an AWS Student Builder Groups Leader also gave me opportunities to become involved beyond my own campus.
I'm currently volunteering with AWS Community Day Ahmedabad | DevOps Day, and I'm also helping with other AWS Community Day initiatives wherever I can contribute.
What I enjoy about this stage of the journey is that the question has changed.
Earlier, I would think:
“How can I attend this event?”
Now I often find myself thinking:
“How can I help make this event better?”
That's a small change in wording, but it represents a much bigger change in mindset.
I still love attending sessions and learning from speakers. But now I also enjoy helping other organizers, supporting communities, sharing things I've learned from our own events, and contributing wherever another community needs an extra hand.
I have benefited enormously from people who helped me when I was starting.
Trying to do the same for somebody else's community feels like the natural next step.



The Next Stage: AWS Student Community Day Panipat
And this journey is still moving.
On September 11, 2026, I'll be speaking at AWS Student Community Day Panipat.
The fact that I can now write that sentence still feels a little strange.
A year ago, I was still figuring out what community leadership looked like for me.
Now I'm getting opportunities to travel to different communities, speak with students, and share what I've learned along the way.
What excites me the most isn't simply getting another speaking slot.
It's knowing that somewhere in that audience there may be someone attending their first AWS community event.
I know what that feels like.
I was that person not very long ago.
If something I share can make that person explore AWS, build their first project, apply for a community opportunity, or simply introduce themselves to another builder in the room, then the session has done its job.

Sometimes I Build Things Because I Wish They Existed
As I spent more time speaking with students, I kept hearing a simple question:
“Is there an AWS Student Builder Group near me?”
The problem wasn't that communities didn't exist.
Students simply didn't always know how to find them.
So I built something for that.
I created an AWS Student Builder Groups Map that helps students discover groups around them and understand where they can start connecting.


It isn't the most technically complex application I've ever worked on, and that's exactly why I like using it as an example.
Developer-focused projects don't always need to be massive.
Sometimes a developer has a very specific point of friction.
If you can remove that friction, you've created something useful.
A student shouldn't have to spend hours randomly searching for a community if we can make discovery easier.
Sometimes one event changes someone's direction.
Sometimes one conversation does.
Sometimes it is simply one link that gets them into the right room.
There are lots of Projects I have created related to AWS Builder Center as well. I'm going to launch them soon.

Developer Relations Started Making Sense
Somewhere during all of these experiences, another part of my journey started making much more sense.
I had always enjoyed development.
I enjoyed cloud and AI.
But I also enjoyed teaching, speaking, creating technical content, organizing events, helping developers discover tools, and talking to communities.
For a long time, I treated those interests as separate things.
Then I started understanding Developer Relations.
Suddenly, a lot of the things I enjoyed had a common direction.
Developer Relations sits at an intersection I genuinely enjoy:
technology, developers, content, education, products, and community.
AWS gave me a place where I was already practicing many of those skills without necessarily calling them DevRel.
Every technical session taught me how to communicate more clearly.
Every beginner question taught me that documentation and explanations need to meet developers where they are.
Every event taught me something about developer communities.
Every demo taught me to think about how someone experiences technology rather than only whether the technology technically works.
And every community interaction reminded me that developers are people before they are users.

DevRel Uni Helped Me Put Structure Around It
Getting into DevRel Uni helped me take that interest more seriously.
Before that, I knew that Developer Relations sounded very close to what I wanted to do, but I was still trying to understand what DevRel looked like beyond speaking at events.
DevRel Uni helped me think much more intentionally about developer education, community, developer experience, content, technical advocacy, and how all of those pieces connect.
It also made me reflect on the AWS work I was already doing.
When I simplify an AWS concept for a beginner, that's developer education.
When I build something like the Student Builder Groups map, I'm thinking about developer experience and community discovery.
When I speak at an event, I'm advocating through education.
When I organize a learning initiative across multiple communities, I'm thinking about ecosystem building.
When I write about something I learned, I'm creating a resource another developer can discover later.
DevRel Uni didn't suddenly give me a completely different direction.
It gave language and structure to a direction I was already moving toward.
That was valuable.
And AWS has been one of the biggest environments where I've been able to put those lessons into practice.
I had opportunity to be in Podcast with Manik (Fellow DevRel Uni Cohort 7 Member) : Â https://youtu.be/UzFeRDMJig8?si=OTvlCZZfHBc13jcOÂ



Then I Started Building My Own Community
After spending so much time inside different communities, I eventually started asking myself another question:
What would I build if I created my own community from zero?
That question became NavraCommunity.
Navra is something I'm building around developers, creators, builders, gaming, learning, and people who simply enjoy making things together.


Starting something of your own makes you appreciate community organizers even more.
Suddenly you're thinking about onboarding, identity, content, events, partnerships, moderation, member experience, branding, and whether the things you're creating are actually useful.
A lot of the lessons I learned through AWS communities naturally influence the way I think about Navra.
I've seen how much a welcoming environment matters.
I've seen how much students grow when somebody trusts them with responsibility.
I've seen communities work incredibly well when collaboration comes before credit.
I've also seen events that looked great externally but didn't necessarily create much long-term value.
All of that influences what I want to build.
I'm still learning how to do it properly.
And I think that's exactly how it should be.

AWS New Voices — Becoming a Better Speaker
Another important part of my journey has been AWS New Voices, where I’m learning how to become a better technical speaker.
It has helped me work on things beyond just knowing the topic — structuring a talk, building a stronger story, understanding the audience, improving delivery, and making technical sessions easier to follow.
For me, it has been a chance to level up my speaking skills intentionally, learn from experienced speakers, and become more confident in the way I communicate technical ideas.
The more I speak, the more I realize that good technical speaking is not about sounding complicated.
It is about making the audience feel, “I understand this, and I can try it too.”



The Part That Doesn't Usually Make It Into Posts
If I only wrote about the events, stages, titles, and numbers, this would sound like a very clean journey.
It wasn't.
There were sessions where I knew I could have explained things better.
There were event ideas that never happened.
There were messages that didn't get replies.
There were people who said they would help and couldn't.
There were plans that changed at the last minute.
There were moments where I questioned whether I was technical enough to teach something.
There were times where managing multiple communities became overwhelming.
And there were definitely nights where I opened my laptop and thought:
“How are we actually going to make this happen?”
But those moments are probably responsible for more of my growth than the perfect ones.
Community leadership doesn't really have an answer key.
You try.
You get something wrong.
You ask for help.
You improve it.
And when the next problem appears, you realize you're slightly more prepared than you were last time.
That is how most of this year felt.

More Than a Title
When I first became an AWS Cloud Club Captain, the title meant a lot to me.
Today, being an AWS Student Builder Groups Leader means something different.
I still value the role, but when I hear the title now, I don't immediately think about the name of the program.
I think about everything attached to it.
I think about my first AWS Student Community Day.
I think about volunteering behind the scenes in Ahmedabad.
I think about representing my community in Pune.
I think about sharing leadership lessons at CHARUSAT.
I think about speaking in Amravati.
I think about all the sessions with Student Builder Groups.
I think about Gujarat Students Builder Week.
I think about the volunteers who became friends.
I think about students who messaged after sessions.
I think about people who gave me opportunities before I was completely confident I was ready for them.
I think about the communities I'm now able to help in return.
That's why this journey became more than a title.
A title might be what appears on a profile.
The real value is everything it allows you to experience, learn, and eventually give back.

And Now I'm 23
For the 23 days leading up to my birthday, I gave myself another challenge:
23 certifications before turning 23.
And somehow, I finished all 23.
23 days.
23 certifications.
It was fun, slightly chaotic, and definitely one of those ideas that sounded easier when I first thought about it.
But when I sat down to reflect on the year before turning 23, I realized that the 23 certificates were not actually the biggest thing I gained.
The biggest thing was clarity.
A year ago, I knew I wanted to do something meaningful in technology, but I didn't fully know what that looked like for me.
Today, I understand it a little better.
I want to become technically stronger.
I want to keep building with cloud and AI.
I want to continue speaking.
I want to write content that developers genuinely find useful.
I want to contribute to communities beyond my own.
I want to keep learning Developer Relations properly.
And I want to build experiences that make another developer's first step easier than mine was.
AWS has been a very important part of helping me discover that direction.
It gave me technology to learn, stages to speak on, communities to contribute to, people to learn from, and enough unfamiliar situations to force me to grow.
But more than anything else, the AWS community gave me people to learn and build with.
That is something no certification can really capture.
Exactly one year ago, one leadership opportunity became the beginning of a completely different year.
Today, I'm 23, still learning, still experimenting, still getting things wrong, and still trying to build something meaningful.
There is a lot more I want to do.
But for now, I'm grateful for how far one year of simply showing up has taken me.
To every builder, student, speaker, organizer, volunteer, community leader, friend, and person who gave me an opportunity somewhere along the way:
thank you for being part of this chapter.
Maybe 23 really is my lucky number.
Thanks, 23.
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article