When I first discovered the AWS Community Builders Program, I assumed it was mainly intended for established content creators, frequent conference speakers, or people who were already well known within the AWS community.
I was wrong.
The program is not about having the largest audience or knowing everything about AWS. It is about being genuinely curious, sharing what you learn, and helping others move forward in their cloud journeys.
Today, I am proud to be part of the AWS Community Builders Program in the Serverless category.
During my first year, I have probably learned far more than I have contributed. Between maternity leave, becoming a first-time mother, studying for an AWS certification, and trying to find a new rhythm, some of my community plans naturally moved more slowly than I expected.
Receiving my AWS Community Builder welcome kit gave me exactly the push I needed to become more active, share what I have learned, and give something back to this wonderful community.
If you have ever wondered whether you are experienced, visible, or “ready enough” to apply, this article is for you.
What Is the AWS Community Builders Program?
AWS Community Builders is a global program for people who are passionate about AWS technologies and enjoy exchanging technical knowledge with others.
Its members come from many different backgrounds. They include cloud engineers, developers, solutions architects, students, content creators, user group organizers, and people who are simply enthusiastic about building and learning with AWS.
Community Builders contribute in many different ways, including:
- Writing technical articles and tutorials
- Creating videos and live streams
- Building open-source projects
- Sharing GitHub repositories
- Speaking at conferences and meetups
- Answering questions in technical forums
- Organizing workshops and study sessions
- Publishing educational content on social media
- Supporting local cloud communities
There is no single “correct” way to contribute.
You do not need to become a YouTuber, launch a podcast, or speak at a major international conference. What matters is finding a format that suits you and using it to create genuine value for other people.
Who Can Apply?
According to the official AWS Community Builders page, anyone aged 18 or older who is passionate about building on AWS can apply.
You do not need to hold a senior position, work for a large technology company, or have thousands of followers. Students, beginners, career changers, and experienced professionals can all bring something valuable to the community.
What can strengthen your application is evidence that you are already sharing your knowledge publicly.
This could include:
- A blog post explaining an AWS solution
- A tutorial based on a real problem you encountered
- A public GitHub project
- A technical presentation or workshop
- A video demonstrating an AWS service
- Helpful answers in technical forums
- Participation in an AWS User Group
- Educational posts that make complex topics easier to understand
A small number of thoughtful and original contributions can say much more about you than a large amount of generic content.
At the time of writing, applications are still being accepted. If you are considering applying, this is a good time to organize your public contributions and tell your story.
What Did I Include in My Application?
Before applying, I had delivered two technical talks—one at the AWS User Group Thessaloniki and another at the AWS User Group Athens.
My presentations focused on Amazon EC2 and practical AWS topics based on real tasks and situations I encounter in my daily work as a Cloud Infrastructure Engineer.
I believe this is important because your contributions do not need to be based on abstract or overly advanced topics. You can share the problems you solve at work, the decisions you make, the approaches you follow, and the lessons you learn along the way—provided that you do not disclose confidential company information.
Real-world experience can make technical content more practical, relatable, and useful to others.
Those two talks demonstrated that I was willing to step outside my comfort zone, share what I knew, and actively participate in my local AWS community.
You do not need dozens of talks or articles before applying. A few genuine contributions that clearly demonstrate your interest and community involvement can provide a strong foundation.
You Don’t Need to Be an Expert
One of the biggest misconceptions is that you must already be an AWS expert before you can contribute.
You do not.
Some of the most useful technical content comes from people who have recently solved a problem and still remember exactly which parts were confusing.
You can document:
- What you were trying to build
- Which approaches you considered
- What did not work
- How you identified the problem
- What finally solved it
- What you would do differently next time
That learning process has real value.
For example, while preparing for my AWS certification, I discovered several gaps in my own knowledge. The exam was strongly focused on CloudFormation, while most of my daily infrastructure-as-code work is based on Terraform.
I did not pass on my first attempt.
However, that first attempt showed me exactly what I needed to study more deeply. When I eventually passed, the result was important, but the notes, scenarios, mistakes, and lessons I collected along the way were even more valuable.
Those lessons can now become articles or practical guides that may help someone else avoid the same confusion.
You do not have to wait until your journey looks perfect before you start sharing it.
What Makes a Strong Application?
A strong application should make it easy for the reviewers to understand three things.
1. What Are You Genuinely Interested In?
Choose the category that reflects your real interests, professional experience, and the subjects you want to explore further.
Do not select a category simply because it sounds popular. Your application will feel more authentic when it is connected to the work you actually do and the topics you naturally enjoy discussing.
I joined the Serverless category because it gives me the opportunity to learn, experiment, and share more about building applications and solutions without managing traditional server infrastructure.
Your chosen category does not have to represent every part of your professional experience. It should represent the area in which you would like to participate, learn, and contribute within the program.
2. How Are You Helping Others?
Show how your contributions support other people.
Perhaps your tutorial saved someone several hours of troubleshooting. Maybe your repository provides a reusable example. Your presentation may have introduced beginners to a difficult concept, or your post may have encouraged someone to attempt a certification.
Community impact does not always have to be measured through thousands of views.
A meetup talk delivered to a smaller local audience can still create meaningful conversations. An article read by only a few people can still help someone solve a real technical problem.
Helping even a small audience in a meaningful way matters.
3. Are Your Contributions Genuinely Yours?
Your personality and perspective are part of the value you offer.
Avoid trying to sound like every other technical writer. Explain concepts in your own way, include lessons from real projects, and be honest about challenges or mistakes.
Originality does not mean discovering something nobody has ever discussed before. It means adding your own experience, understanding, and voice to the conversation.
How to Prepare Your Application
If you are interested in applying, do not wait until the last moment to begin your community journey.
Start now.
Create a Consistent Public Identity
Set up your AWS Builder ID and try to use a consistent name across the platforms where you publish.
This makes it easier for reviewers and other community members to recognize your work and connect your different contributions.
Choose a Subject You Genuinely Enjoy
Focus on an area that connects with your real interests or professional experience, such as:
- Serverless
- Cloud Operations
- Containers
- Security
- Networking
- Storage
- Data
- AI and Machine Learning
- Infrastructure as Code
- DevOps
- Developer Tools
A clear focus helps people understand what they can learn from you, but it does not prevent you from exploring other AWS topics.
My previous talks focused on Amazon EC2 and topics related to my daily work, while I am now part of the Serverless category. Your existing contributions and the direction in which you want to grow do not always have to be identical.
Publish Useful Public Contributions
Create two or three strong pieces of work that clearly represent your knowledge and willingness to help.
Quality matters more than publishing as much content as possible. One detailed article based on a real technical problem can be more valuable than several rushed or generic posts.
If writing is not your preferred format, you could deliver a meetup talk, create a video, share a useful repository, or contribute to a technical discussion.
Keep a Record of Your Work
Save the public URLs of your articles, repositories, videos, talks, event pages, and other contributions.
When you complete your application, you will already have your strongest examples organized and ready.
For talks and community events, keep links to event announcements, presentation materials, recordings, or public posts that confirm your participation whenever possible.
Tell Your Real Story
The application is not only a list of links. It is also an opportunity to explain why you contribute, what you have learned, and what being part of the community would mean to you.
Be concise, specific, and honest.
You do not need to exaggerate your achievements or present yourself as someone who never encounters difficulties. Your real progress, motivation, and willingness to help are more meaningful.
There Is Room for Honest Mistakes
It is also worth knowing that there is some room for genuine mistakes during the application process.
In my case, I accidentally submitted two applications.
I completed my first application without a referral. When I later received a referral, I submitted a second application so that I could include it.
Submitting two applications was not ideal, and it is certainly not something I would recommend. However, the AWS team did not criticize or disqualify me because of it.
They understood that it was an honest mistake, and I was still accepted into the program.
Review your application carefully before submitting it, but do not allow the fear of making a small mistake to stop you from applying. Behind the process, there are real people who understand that applicants are human too.
What Do AWS Community Builders Gain?
The program provides access to learning resources, educational opportunities, networking, and connections with AWS experts and community members from around the world.
Depending on the current program cycle, members may also receive additional resources, recognition, community activities, or other benefits.
Since these benefits can change, applicants should always check the official AWS Community Builders page for the latest information instead of relying on lists from older articles.
The most important benefit, however, is difficult to measure.
It is the opportunity to meet people who are learning, building, experimenting, and sharing just like you.
Being surrounded by an active technical community can expose you to new ideas, encourage you to leave your comfort zone, and give you the motivation to turn your private notes and experiences into something useful for others.
My Advice to Future Applicants
Do not create content only because you want to add links to an application.
Share because you encountered something worth explaining.
Share the answer you wish you had found when you were stuck. Document the mistakes that taught you something. Turn your notes into a guide that makes another person’s journey a little easier.
Most importantly, do not reject yourself before AWS has the opportunity to review your application.
You may be a student, a beginner, an experienced engineer, a career changer, or a parent trying to find time between new responsibilities. None of these prevents you from becoming a meaningful member of a technical community.
I am a Cloud Infrastructure Engineer, a first-time mother currently on maternity leave, and an AWS Community Builder in the Serverless category.
Before applying, I shared parts of my professional experience through two talks about Amazon EC2 and practical AWS topics at the AWS User Groups in Thessaloniki and Athens.
During my first year in the program, I focused more on learning than contributing. My journey has not always moved as quickly or perfectly as I would have liked, but I am still here, still learning, and now ready to share more and give back to this wonderful community.
If I can be part of this program, why not you?
Start with one useful contribution. Then create the next one.
Your community journey may have already begun before you even realized it.
Top comments (0)