Amazon's tech employees share what it's like to work at the company in the annual Tech Survey – About Amazon

As part of our efforts to continuously improve for our team, today we shared the results of our annual internal Tech Survey—which is sent to technology-focused employees across the company to understand their sentiment, experience, ability to innovate, and culture of customer obsession. The effort is driven by developers, for developers, and has been a part of Amazon’s builder culture for more than 20 years.
The survey was administered this year by the Amazon Software Builder Experience team, led by Eric Docktor. The team was formed in February to continuously improve the day-to-day experience of builders across the company and to empower individuals and teams to do the same.
Read the email Eric sent to employees (below) to learn more about this year’s results:    
I’m excited to announce that the results of the 2022 Tech Survey are now available on the Tech Survey site. The Tech Survey is an important tool for how both the tech community—as well as individual teams—understand and continuously improve the experience for tech builders across the company. Over the years, the survey has changed a lot—the questions and job families that we include, the size of the community that participates, and the functionality we deliver to you to understand your results. But its focus has remained the same: to hear directly from the tech community about what’s going well and where there are opportunities to improve, and to empower teams to go make those improvements.
As you review the results with your team to identify your teams’ successes and areas for improvement, I wanted to share some high-level takeaways that stood out to me and the Software Builder Experience team (ASBX). This is the first year that ASBX has managed the Tech Survey (with ASBX just coming together in February 2022), and we are humbled by the increased response rate, with nearly double the participation rate this year compared to last year. We see that as a signal of rising engagement in the tech community and increased trust in our collective dedication to improvement. The ASBX team will continue to dig into the results over the coming weeks as we identify what’s working well and where we can continually raise the bar. I hope you will do the same with your team.
Some of the highlights of the survey include:

While there are many areas to celebrate, we will continue to focus on areas where we have work to do.
While 74% of respondents said they can meet their career goals at Amazon, and 10% are considering an internal transfer to further develop themselves, we also see that 5% are considering leaving Amazon in the next six months. Among that 5%, about half cited base pay as their primary concern. As you’re likely aware, earlier this year Amazon announced increases in salary bands across many job families, including an increase to the U.S. base pay cap. The Compensation team has learned a lot based on feedback from that announcement, and the team regularly assesses data to reflect changes in the marketplace as they continue to review compensation packages across Amazon.
We also heard that bug fixes cause frustration for some teams, with about 22% of those who write code reporting that bug fixes usually or always interrupt their work. We heard a desire to streamline processes and maintenance work so that builders can spend more time on innovation. We are working to make that easier, or automated, for the software you consume (see more below). And if you’re in a team that sees these interruptions related to code produced in your team, we hope you use these results as a call to action to invest in your own test automation and quality processes.
The next step in the Tech Survey cycle happens at the company, org, team, and individual levels. We expect teams and leaders to dig in to these results and learn where they’re leading (and maybe sign up to host a Principals of Amazon talk to show us how!), and where you have opportunities to improve in your own teams.
From a company perspective, the ASBX team will keep looking through these results for feedback on our own roadmap—and for areas where we will advocate for improvements across the company. We also look at how we, in ASBX, can directly deliver improvements. To that end, I wanted to share some key wins since ASBX’s founding in February:
Those two wins really highlight the two major ways the ASBX organization is driving improvements for builders. In some ways, like automated patching, we’ll launch things that will immediately improve things for you. And sometimes, like fixing stuck pipelines, we can’t fix it for you, but we can improve the visibility so you know where to invest to improve your team’s builder experience. We’ll keep innovating to make you more efficient, like we did by improving search in SIM Ticketing, centrally handling upgrades to Amazon Linux 2 for 1.8M hosts so you didn’t have to, and reducing Apollo deployment time by 75% for large fleets. And yet, we know there’s more to do, and we’ll use what we learn in the Tech Survey (and other feedback forums) to influence our roadmap.
I hope you and your teams make some time to digest the tech survey to learn what improvements you can make, as well. I look forward to seeing what we all do with it!
Let’s keep building together,
Eric

source

Leave a Comment

Your email address will not be published.