[ad_1]
As part of our efforts to continuously improve our team, today we shared the results of our annual internal tech survey—which is sent to tech-focused employees across the company to understand their feelings, experiences, creativity, and customer culture. An obsession. The effort is led by developers, by developers, and has been part of Amazon’s developer culture for more than 20 years.
The study was conducted this year by the Amazon Builder Experience team led by Eric Doctor. The group was formed in February to improve the day-to-day experience of builders across the organization and to empower individuals and teams to do the same.
To learn more about this year’s results, read Eric’s email to staff (below):
I’m excited to announce that the 2022 Tech Survey results are now available on the Tech Survey site. Tech Survey is a tool for both the tech community—as well as individual teams—to understand and continuously improve the experience of tech developers across the company. Over the years, the survey has changed a lot—the questions and job families we include, the size of the community involved, and the activities we provide for you to understand your results. But the focus remains the same: to hear directly from the tech community about what’s good and where there are opportunities for improvement, and to encourage teams to make improvements.
As you review the results with your team to identify your team’s successes and areas for improvement, I wanted to share some top takeaways that stood out to me and the Software Developer Experience Team (ASBX). This is the first year that ASBX has administered the Tech Survey (when ASBX comes 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 it as a sign of increased participation in the technology community and increased confidence in our collective commitment to improvement. The ASBX team will continue to dig into the results in the coming weeks as we identify what works well and where we can continually improve. I hope you do the same with your team.
Among the main points of the survey:
- As the response options for these questions changed in 2019, we saw “I enjoy working for Amazon” (86%) and “I would recommend Amazon as a great place to work to others in the field” (81%) among the top scores. And we saw the lowest negative response to these questions. This is probably the biggest topic for me – we know we have a lot of work to do, and the ASBX organization is well aware of the repetitive work that some Amazon software developers have to do to continue to delight customers. We are focused on the company to continue to improve, and I am motivated to see this result.
- Relatedly, 91% of those surveyed feel encouraged to share their ideas, 74% feel confident that working at Amazon will meet their career goals, and 91% feel comfortable with their manager to express their concerns.
- Respondents trust their organizations and their leaders, with 85% of respondents reporting that their managers seek diverse opinions when making decisions and 82% reporting that their jump-level manager is an effective leader. We saw high scores on other questions related to managers, including managers helping team members understand what is expected of their roles, managers giving practical feedback on performance, and managers explaining how performance is evaluated. I’m really happy to see these results, because I know from my own Amazon experience that this is hard work. I encourage managers and teams to examine their own results and not take this as a declaration of victory. It takes work every year!
- Customer focus is high, with 86% of respondents saying their teams are working on the right thing for customers and 75% saying they’re truly innovating for customers.
Although there are many places where the festival can be celebrated, we will focus on the areas where we still have work to do.
We see that 74% of respondents say they can meet their career goals at Amazon and 10% are considering an internal transfer to further develop themselves, while 5% are considering leaving Amazon in the next six months. About half of these 5% cited basic pay as their top concern. As you may know, earlier this year Amazon announced increases in salary bands across several job families, including an increase in the U.S. base pay ceiling. The compensation team learned a lot based on that announcement, and as the team continues to review compensation packages across Amazon, it regularly reviews data to reflect changes in the marketplace.
We also heard that bug fixes are a source of frustration for some teams, with 22% of coders reporting that bug fixes are often fixed or always interrupt their work. We’ve heard the need to streamline processes and maintenance so builders can spend more time on innovation. We’re working to make that easier for the software you use (see below). And if you’re on a team that’s seeing these outages related to developed code, we hope you’ll 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 occurs at the company, enterprise, team, and individual levels. We expect teams and leaders to dig into these results and learn where they’re headed (and sign up to host an Amazon talk with principals to show us how!) and where there are opportunities for improvement within your own teams.
From a company perspective, the ASBX team will continue to look at these results to get feedback on our own roadmap and areas where we can make improvements across the company. We at ASBX will also look at how we can provide updates directly. To that end, I wanted to share some key wins since ASBX was founded in February:
- Year-over-year, we automatically resolved 20% of blocked software issues—a software update so urgent that teams are blocked from deploying anything else before the update is completed—versus 0.5% in 2021. Software developers. They haven’t lifted a finger to incorporate these improvements into their apps. We made a big bet on this in an area where we thought we could significantly reduce fatigue around Amazon by 2022, and we’re very pleased with our initial results. We will continue to drive this program to increase the percentage of blocked software issues that are resolved automatically.
- We launched the Pipeline Effectiveness Dashboard in June to show teams across Amazon how healthy their pipelines are and where there are opportunities to improve pipeline health. So far By 2022, the percentage of pipelines that are regularly integrated from the live version set will increase from 61% to 83%. Software developers used the dashboard to locate and fix clogged pipelines, reducing overall manual intervention on clogged pipelines by 6.6 percent. To put that in context, that’s about 17 thousand times. per week To solve the problems of the management pipeline, software developers are not cut off from the construction.
Those two wins highlight two key ways the ASBX organization is bringing improvements to builders. In some ways, like automated folding, we start things that improve things right away. And sometimes, like fixing stuck plumbing, we can’t fix it for you, but we can improve visibility so you know where to invest to improve your team’s developer experience. We continue to innovate to make you more efficient by improving search in SIMTicket, deploying Amazon Linux 2 updates to 1.8M hosts, and reducing Apollo deployment times by a whopping 75%. Ships. However, we know there’s more to do, and we’ll use what we learn from the Tech Survey (and other feedback platforms) to influence our roadmap.
I hope you and your teams will take some time to digest the technology survey to see what improvements you can make. I look forward to seeing what we all come up with!
Let’s continue to build together
Eric
[ad_2]
Source link