Let's Talk About Rejection

On March 4th, 2025, I woke up thinking it was just another Tuesday morning. Like many people, I started my day by making a cup of coffee and scrolling through social media. But this day was different because it was the AWS Community Builder acceptance day, a big deal for many in the tech world. As I scrolled through my feed, I saw tons of excited posts from people celebrating their acceptance into the program. There were newcomers thrilled to join for the first time and returning builders eager to continue their journey. Even AWS Heroes, who are highly respected in the community, were joining in to congratulate everyone. The excitement and sense of community were really strong. With my own anticipation growing, I checked my email, and there it was…

Unfortunately, our team did not select you to join the program this cycle. Evaluations were primarily based on the links to the content you submitted for consideration — and alignment to your chosen topic area — along with your AWS journey, background, and other information in the application.

It felt like a punch in the gut. I've been part of the AWS Community Builder's program since 2020. I've written over 10 tutorials on getting started with AWS Serverless that have more than 12,000 views. I maintain over 10 GitHub repositories that have helped new AWS developers learn common Serverless patterns. I'm a Director of Engineering at a startup that builds exclusively with AWS Serverless technology. I was even interviewed by AWS and am still featured in the AWS Amplify customer section. As I sat there staring at the rejection email, I couldn’t help but think, “What went wrong?”

I'm not sharing this experiences to brag about accomplishments or complain about the selection process, but to start a conversation about normalizing rejection. Rejection is tough. It can feel discouraging, but it's something we all experience, both personally and professionally. By discussing it openly, my goal is to remove the stigma. Rejection doesn't define your abilities or worth. It should be seen as an opportunity to grow. It's a chance to reflect on ourselves and consider how we can improve.

So, what does this moment mean for me? How can I turn this rejection—this obstacle—into an opportunity? I haven't written any new AWS content in over a year, and during that time, our industry has changed a lot. AI has become a major focus, and I haven't shared any opinions, guides, or insights on it. I use AI and AWS Serverless technology every day, both at work and in side projects. I've been building a lot, but writing and sharing very little. Community building is all about just that—building community! So that’s my commitment for the next year. I plan to write and share more about my experiences with AWS and Serverless. These hands have some dirt on them, and I want to show it.

Rejection sucks, especially in our field, but it's part of the journey. In fact, one could argue that achievements aren’t meaningful without rejection. Here are a few ways we can turn these moments into growth opportunities:

1. Reflect and Learn: Take a moment to understand what happened. Was there feedback? Use it. Every piece of criticism is a chance to improve.

2. Stay Connected: Lean on your community. Share your experiences; you'll find you're not alone. Engaging with others can offer new perspectives and support.

3. Keep Building: Don't let rejection stop your progress. Dive into new projects, contribute to open-source, or write about your experiences. Continuous learning and sharing keep you moving forward.

4. Take Care of Yourself: It's okay to feel down. Acknowledge it, but don't dwell on it. Engage in activities you enjoy, and remember to balance work with rest.

Remember, rejection doesn't define us. It's just a detour, not a dead-end. Keep pushing, keep coding, and keep sharing. I know I plan to. To all the Community Builders, congratulations! I'll see you all next year.