AWS Builder Center
From Technical Expertise to Finding My Voice: My AWS New Voices Journey

From Technical Expertise to Finding My Voice: My AWS New Voices Journey

How AWS New Voices challenged me to grow beyond technical knowledge, become a better communicator, and discover new ways to contribute to the AWS community.

Being Technical Doesn't Automatically Make You a Good Speaker

I've spent many years working in technology. My professional journey has taken me from systems administration and IT infrastructure to technology leadership, cloud operations, and eventually my current role as a DevOps SRE.
Throughout that journey, I've learned something important: technology never stops challenging you.
There is always a new service to understand, an architecture to improve, an incident to investigate, or a problem you haven't encountered before.
I've invested countless hours in learning, building, troubleshooting, and earning certifications. I've worked with real production environments, managed complex AWS infrastructures, and faced situations where finding the right solution required much more than theoretical knowledge.
But at some point, I started asking myself a different question:
What good is all that experience if I can't communicate it effectively and help others learn from it?
Knowing how to solve a technical problem is one thing. Standing in front of an audience, explaining that problem clearly, connecting with people, and inspiring them to explore the solution themselves is something entirely different.
That realization became an important part of my professional development.
And it's one of the reasons I decided to take on the AWS New Voices challenge.

Why AWS New Voices Mattered to Me

In 2026, I was selected to participate in AWS New Voices.
By that time, I was already involved in the AWS community as an AWS Community Builder and the founder of CloudOps Guild, a community where I share knowledge about AWS, DevOps, SRE, cloud architecture, and artificial intelligence.
I was creating technical content, building hands-on labs, participating in community initiatives, and looking for opportunities to speak at technical events.
But I knew I still had room to grow.
My goal wasn't simply to add another badge to my profile.
I wanted to become a better technical speaker.
Someone capable of taking a complex subject and turning it into a story people could understand, remember, and apply.
Someone who could connect real-world engineering experience with practical learning.
And, most importantly, someone who could encourage others to believe that they, too, could build a career in technology.
For me, AWS New Voices represented an opportunity to work intentionally on that side of my professional growth.

My Journey Wasn't a Straight Line

One of the most meaningful parts of my AWS New Voices experience is that I didn't complete the journey in a single attempt.
I went through two stages before successfully completing the program.
And I want to emphasize that because we often share our achievements without talking about everything that happened along the way.
When people see a badge, a certification, or a graduation announcement, they usually see the final result.
They don't always see the extra practice, the adjustments, the moments of reflection, or the persistence required to get there.
In my case, taking longer to complete the journey turned out to be valuable.
It gave me more opportunities to practice, meet people from different parts of the world, exchange experiences, and continue developing my communication skills.
I could have focused only on the fact that I needed another opportunity to finish.
Instead, I chose to see it as additional time to learn.
That perspective has accompanied me throughout my career.
I've experienced something similar while preparing for demanding AWS certifications, working through challenging technical projects, and solving production incidents.
Things don't always work on the first attempt.
What matters is what you learn, how you adapt, and whether you're willing to keep improving.
Completing AWS New Voices reinforced that belief.

The Biggest Lesson: Communication Is a Technical Skill Too

As engineers, we spend a significant amount of time developing technical expertise.
We learn services, frameworks, tools, architectures, and methodologies.
We study how systems behave, how failures happen, and how to build more reliable solutions.
But how much time do we intentionally dedicate to communicating what we know?
That question stayed with me throughout my journey.
I've come to believe that communication should be considered an essential part of an engineer's professional toolkit.
Think about our daily responsibilities.
When an incident occurs, we need to explain what happened, why it happened, and what we're doing to restore the service.
When proposing an architecture, we need to communicate trade-offs, risks, costs, and benefits.
When mentoring someone, we need to translate our experience into something they can understand and use.
And when speaking at a technical conference, we need to do more than present information.
We need to create understanding.
The value of our knowledge increases when we can make it useful to someone else.
This is one of the most important lessons I take away from AWS New Voices.

Bringing Real-World Experience to the Stage

During 2026, I had opportunities to share technical knowledge through community talks, workshops, and educational sessions.
One experience that stands out was my participation as a speaker at AWS Community Day Data & AI in Colombia.
My talk explored a challenge that I find particularly interesting as a DevOps and SRE professional: what happens when a generative AI application appears technically healthy but is actually producing incorrect or unreliable answers?
It's a problem that connects two areas I'm passionate about: cloud operations and artificial intelligence.
Traditional observability can tell us whether an API is responding, whether a Lambda function is executing successfully, or whether infrastructure metrics are within expected thresholds.
But does that necessarily mean an AI application is delivering useful and trustworthy responses?
Not always.
That was the central idea I wanted to communicate.
Rather than presenting a collection of AWS services, I wanted to build a narrative around a problem that engineers could recognize and explore.
The experience reinforced an important principle for me:
A technical presentation becomes more valuable when the audience understands the problem before exploring the solution.
It also helped me connect my development as a speaker with the work I do every day.
My professional experience gives me stories, challenges, and lessons worth sharing.
Improving my communication skills helps me turn those experiences into learning opportunities for others.

The Community Makes the Journey More Valuable

Another aspect I particularly appreciated about AWS New Voices was the opportunity to connect with people from different parts of the world.
Technology brings us together, but our experiences, professional backgrounds, and perspectives are not always the same.
And that's a good thing.
Every conversation can challenge the way we think about a problem or introduce us to a different approach.
As an AWS Community Builder and the founder of CloudOps Guild, I strongly believe that communities accelerate professional growth.
I've experienced it personally.
Sharing knowledge has pushed me to study more deeply, validate my ideas, build better examples, and question my own assumptions.
When you prepare a workshop or explain a concept to someone else, you quickly discover whether you truly understand it.
Teaching becomes another way of learning.
That's why I see speaking, mentoring, and community building as connected activities rather than separate goals.
A technical talk can inspire someone to start learning.
A hands-on lab can help that person develop a new skill.
And a supportive community can encourage them to keep going when things become difficult.
That's the kind of impact I want to continue creating.

What Comes Next?

Completing AWS New Voices in October 2026 was an important milestone for me.
But I don't see it as the finish line.
I see it as another step in a much longer journey.
I want to continue growing as a technical speaker, sharing real-world experiences, participating in AWS community events, and creating content that helps engineers develop practical skills.
I also want to keep challenging myself.
There are still many things I can improve: how I structure technical stories, how I connect with different audiences, and how I turn complex engineering concepts into memorable learning experiences.
Through CloudOps Guild, I plan to continue connecting technical articles, workshops, hands-on labs, and community conversations.
My focus remains on AWS, DevOps, SRE, and the growing intersection between artificial intelligence and cloud operations.
But beyond the technologies themselves, I want to help more people discover what they're capable of building.
And I want to encourage other technical professionals to share their experiences, even if they don't feel completely ready.
Because that's another lesson I've learned:
You don't have to be a perfect speaker to start sharing your knowledge. You become a better speaker by sharing, learning, and improving along the way.

A Final Reflection

Looking back, I'm grateful that my AWS New Voices journey required more than one attempt.
It reminded me that progress isn't always linear.
Sometimes the experiences that take longer are the ones that teach us the most.
I'm proud to have completed the program, but I'm even more grateful for the learning, practice, and connections that came with it.
To everyone who contributed to this experience and to the people I've had the opportunity to meet along the way: thank you.
And to any engineer who has thought about speaking at a meetup, writing a technical article, or sharing a lesson from a challenging project but hasn't taken that first step yet, I'd like to leave you with this thought:
Your experience has value, and your voice deserves to be heard.
You don't need to know everything.
You don't need to have all the answers.
You just need to be willing to share what you've learned and keep growing.
That's what AWS New Voices means to me.
And this is only the beginning.


Mario Serrano is a DevOps SRE, AWS Community Builder, AWS New Voices 2026 graduate, and founder of CloudOps Guild. He shares practical knowledge about AWS, DevOps, SRE, and artificial intelligence through technical talks, hands-on labs, and community initiatives.
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article