How can you become an AWS Community Builder?

Ahmed Srebrenica - May 1 - - Dev Community

Introduction

In January of this year, AWS issued a call to fill out applications for the AWS Community Builders program — and I applied. I honestly hoped to be accepted because I know how much effort I put in to meet certain criteria. On March 4th, my happiness knew no bounds when I received an email from AWS stating that I was accepted into the AWS Community Builders program. To experience the same joy as me and to gain all the benefits that this program offers, I will give you some tips to increase your chances of being accepted into this prestigious program.

Picture 1. AWS Community Builders logo — downloaded from: https://aws.amazon.com/blogs/aws/announcing-the-new-aws-community-builders-program/

What is the AWS Community Builders program?

According to AWS, The AWS Community Builders program offers technical resources, education, and networking opportunities to AWS technical enthusiasts and emerging thought leaders who are passionate about sharing knowledge and connecting with the technical community.

Interested AWS builders should apply to the program to build relationships with AWS product teams, AWS Heroes, and the AWS community.

Throughout the program, AWS subject matter experts will provide informative webinars, share insights — including information about the latest services — as well as best practices for creating technical content, increasing reach, and sharing AWS knowledge across online and in-person communities. The program will accept a limited number of members per year. All AWS builders are welcome and encouraged to apply.

How to increase your chances of being selected?

I will share with you a few tips on how to be selected for this program. I will share exactly what I did:

  1. Engage in the community — I think this is the key thing you need to do. Engaging in the community can involve several things. My way of engaging in the community was mostly through writing articles for Medium and sharing those articles on various platforms. It’s very satisfying when someone reaches out and tells you that your article helped them with a certain problem. My articles usually include some demos, but yours don’t have to be the same as mine; they can be of any nature. Also, engaging in the community can involve attending various lectures, webinars, hands-on workshops, blogs, social media, and forums, and being active in everything I mentioned.

  2. Contribute to specific projects — I remember in the application I wrote for this program, there was a requirement for contribution. It wouldn’t hurt to contribute to specific projects, even if it’s just writing documentation or something simpler.

  3. Be active, be a leader, be an ambassador — AWS wants you to be active and help the community, what does that mean? Join some of the Slack or Discord channels where there are topics related to AWS and help others. For example, someone may have a problem creating an EC2 instance; if that’s not a problem for you, reach out to that person, help them, and explain how to create an EC2 instance.

  4. Connect with existing members — Use social networks to connect with existing members who have been accepted into the AWS Community Builders program. But not only with them, but connect with prominent AWS professionals and people who contribute a lot to the community. Through social networks, share their posts related to AWS that can help the community.

  5. Make sure to write a good application — When writing your application, make sure it’s as good as possible. In my application, I also wrote about things unrelated to AWS and IT in general. Since I was a basketball player, coach, and assistant at the university, I mentioned these experiences to let AWS know that I have experience working with communities.

WARNING: Don’t use AI tools in your texts that would write documentation instead of you. It is allowed to use them for code; however, a big NO is placed on everything else. Also, don’t use AI in writing the application for this program, otherwise, you will be rejected.

What are the benefits of this program?

There are many benefits to this program. Depending on what you need most, that will be the greatest benefit for you. Some of the benefits include a $500 credit to your AWS Account, a SWAG package, becoming part of the AWS Community Builders community on Dev.to, joining the Slack community (with over 3000 users), daily communication in various ways with other AWS Community Builders, and the privilege of attending various lectures by different AWS experts.

Personally, for me, the greatest benefit is being part of the Slack community. Why specifically that? I have the opportunity to learn a lot from other AWS Community Builders, both through the content they share and if I ask a question, someone will surely provide an answer for what I’m looking for. I’ve met new people, made new friends, and that is currently the biggest benefit for me. Certainly, the $500 credit is also helpful, but the community is what brings us together, and Slack is the best place for that.

Conclusion

You don’t need any special experience to be accepted into this program. It’s enough to put in effort and work, and the right people will notice. Follow my advice and you’ll likely be accepted. The next application cycle is in 2025, so start preparing now. Become part of this prestigious AWS community. PS. If you follow this text and pass the application next year, let me know the result, and we can celebrate with an online coffee.

Add your name to the waitlist for the January 2025 application cycle.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .