Platform engineering went from a conference concept to a standard job title in about 18 months. Before you add it to your org chart, it is worth having a clear definition of what the role actually does and how it differs from DevOps.
DevOps is a practice, not a role. The original idea was to break down the wall between development and operations by having the same people responsible for both writing code and running it in production.
Platform engineering is the practice of building internal products for developers — tools, platforms, and services that make other engineering teams more productive. The platform team treats internal developers as customers.
DevOps as a practice: from day one. A dedicated DevOps engineer: when infrastructure complexity exceeds what product engineers can maintain, usually around 10 to 20 engineers. A platform team: when you have multiple product teams stepping on each other’s infrastructure, usually 50 to 100+ engineers.
Hiring platform engineers before you have the scale that justifies the role. A three-person platform team for a 15-person engineering organization is spending 20 percent of your engineering capacity on tooling that a product engineer could maintain in 10 percent of their time. The ROI is negative at that scale.
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
Unordered list
Bold text
Emphasis
Superscript
Subscript
.svg){kind=icon}
%20(1)-2.svg)
