Skip to content
← Writing← 写作

Org Chart组织架构图

Created in April 2025 · 263 words · 2 min read

2025 · corporate · organization

Hits




Continuous updates


2026

Reporting Chain

President and CEO, Corporate <- CEO, AWS <- SVP, AWS Compute & ML Services <- VP, Compute AI Services <- L7 Sr. Manager, AI Platforms <- 👨🏻‍💻


2025

Reporting Chain

President and CEO, Corporate <- CEO, AWS <- SVP, AWS Utility Computing <- VP, AWS Compute & ML Services <- VP, Serverless Compute <- L8 Director, AI Platforms <- L7 Sr. Manager <- 👨🏻‍💻

Org Structure

Reporting Chain

President and CEO, Corporate <- CEO, AWS <- SVP, AWS Utility Computing <- VP, AWS Compute & ML Services <- VP, Bedrock Core Platform <- L8 Director <- L7 Sr. Manager <- 👨🏻‍💻

Org Structure


2024

Reporting Chain

President and CEO, Corporate <- CEO, AWS <- SVP, AWS Utility Computing <- VP, AI and Data <- VP, AI/ML Services & Infrastructure <- VP <- L7 Sr. Manager <- L6 M2 <- 👨🏻‍💻

President and CEO, Corporate <- CEO, AWS <- SVP, AWS Utility Computing <- VP, AI and Data <- VP <- L7 Sr. Manager <- L6 M2 <- 👨🏻‍💻


2023

Reporting Chain

President and CEO, Corporate <- CEO, AWS <- SVP, AWS Utility Computing <- VP, AI and Data <- VP <- L7 Sr. Manager <- L6 M2 <- 👨🏻‍💻

Org Structure

Reporting Chain

President and CEO, Corporate <- CEO, AWS <- SVP, AWS Utility Computing <- VP <- L8 GM <- L8 Director <- L7 Sr. Manager <- L7 Sr. Manager <- L6 M1 <- 👨🏻‍💻

Org Structure

Reporting Chain

President and CEO, Corporate <- CEO, AWS <- SVP, AWS Utility Computing <- VP <- VP, S3 <- L8 Director <- L7 Sr. Manager <- L7 Sr. Manager <- L6 M1 <- 👨🏻‍💻

Org Structure


2022

Reporting Chain

President and CEO, Corporate <- CEO, AWS <- SVP, AWS Utility Computing <- VP, DECS <- VP, Serverless Compute <- L7 Sr. Manager <- 👨🏻‍💻

Org Structure


Reporting Chain

President and CEO, Corporate <- CEO, AWS <- SVP, AWS Utility Computing <- VP, Compute Services <- L8 GM <- L7 Sr. Manager <- 👨🏻‍💻

Org Structure


2021

Reporting Chain

President and CEO, Corporate <- CEO, AWS <- SVP, AWS Utility Computing <- VP, Compute Services <- L8 GM <- L7 Sr. Manager <- L5 👨🏻‍💻

Org Structure


2020

Reporting Chain

Founder & CEO, Corporate <- CEO, AWS <- SVP, AWS Utility Computing <- VP, Compute Services <- L8 GM <- L7 Sr. Manager <- L5 👨🏻‍💻

Org Structure


2016

Reporting Chain

Founder & CEO, Corporate <- CEO, AWS <- SVP <- VP <- VP <- L8 Director <- L8 Director <- L6 M2 <- L6 M1 <- L4 👨🏻‍💻

Org Structure


Two-Pizza Team

The concept of two-pizza teams is straightforward: no team should be big enough that it would take more than two pizzas to feed them. Putting aside the number or the nature of toppings (we don’t have time and space to solve the “does pineapple belong on pizza?” debate here), ideally, this is a team of less than 10 people: smaller teams minimize lines of communication and decrease overhead of bureaucracy and decision-making. This allows two-pizza teams to spend more time focusing on their customers, and constantly experimenting and innovating on their behalf – the biggest priority of high-performing teams

Note: In reality, however, for various reasons, each M1 'two-pizza team' usually has more than 10 team members.

See also: A return to two-pizza culture — Werner Vogels, June 2026. "Two pizzas were always about ownership culture, and the tools have caught up to the culture."