
With PlatformCon NYC and LDN this summer, I might’ve talked to more people about platform engineering in the last 3 months than ever before. There is something that has really stuck with me since then. Platform engineering initiatives near and far are desperate for leadership.
In an article I wrote a few months ago on the Head of Platform Engineering role, I broke down a HOPE’s (lol) key responsibilities:
- Defining the platform strategy
- Improving developer experience and productivity
- Balancing standardization and flexibility
- Collaboration across engineering and business units
- Driving AI and automation in platform engineering
Sound like something your platform initiative might be missing? You could be the change you want to see.
Every day, I am talking to engineers in grassroots platform initiatives that are stepping up and making a huge difference, or to platform team leads who’re soaking up knowledge from the community to make their platform teams better.
What do you think?














.webp)
.webp)




.webp)
.webp)


.webp)
.webp)

.webp)


-1.webp)














.jpg)
.jpg)
.jpg)
.jpg)
.png)
.jpg)
.png)
.jpg)
.jpg)
.jpg)


.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.png)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.png)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
.jpg)
























