5 Weeks That Changed How I Show Up as an Engineer

I have been an AWS Community Builder for a while now. I have written blogs, built projects on Amazon Bedrock, and spent more hours than I can count in the AWS console. But there was a dimension of the community I had not fully stepped into: standing up literally or virtually and sharing what I know with a room full of people.

AWS New Voices was the structured, supportive push I needed to do exactly that.

I applied because I recognised something in myself: I had more to give to the AWS community than I was currently giving. I had real experience building multi-agent AI systems on Bedrock, managing CloudOps workflows, solving the kind of gnarly infrastructure problems that turn into great stories. What I had not done was translate any of that experience into something I could share confidently at a meetup, a user group, or a community event.

That felt like a skill gap worth closing. And AWS New Voices was exactly the right environment to close it.

I will not share the specifics of the programme the content and curriculum belong to the experience, and part of what makes AWS New Voices valuable is discovering it yourself. What I will share are the four real shifts that happened in how I think, communicate, and show up as an engineer.

The programme culminates in a five-minute presentation to the cohort. I have not delivered mine yet — that moment is still ahead of me. But the preparation is already one of the most useful things I have done as a community member.

My talk is titled "You Are Not a Cloud Engineer Anymore. You Are an AI Engineer. You Just Don't Know It Yet."

The opening I am planning: ask the room to raise their hand if they have ever touched a Bedrock API, a Lambda that calls a model, or a pipeline that feeds an LLM. Then ask them to look at how many hands are up. The argument makes itself before a second word is said.

The core idea is the identity shift happening quietly across the AWS community. Engineers who see themselves as infrastructure people are already doing AI work — building with foundation models, connecting data pipelines to LLMs, automating workflows that would have required a data science team two years ago. The ones who recognise that earliest are the ones who move fastest.

I plan to ground it in my own Bedrock project: a multi-agent CloudOps assistant that resolves cloud incidents in 93 seconds, built part-time over five weeks, for under $7 a month in AWS costs. Not a demo. A real system running against real CloudWatch alarms.

I will update this post once the talk is delivered. The real test is not the preparation it is the moment the words leave your mouth and you find out whether they land. That part is still coming. And I am ready for it.

The five weeks are going to be done. The shifts are not. Here is what is concretely different about how I operate as an engineer and community member:

If you are an AWS Community Builder, AWS Hero, or User Group Leader — yes. Not because you need to fix something. Because you already have something worth sharing, and the programme will help you share it at its full potential.

The engineers who gained the most from this cohort were not the ones with the most presenting experience. They were the ones who came in with real projects, real opinions, and a genuine desire to connect with the community — and left knowing exactly how to do that in a room full of people.

Watch the AWS Community Builders channels for the next cohort announcement. When it comes apply before you start weighing it up. The five weeks will pass either way. You might as well spend them levelling up.