<p>Source: I'm a Platform Engineer, (though not in a strict DevOps sense).</p>

<p>I manage Office 365 for my employer.  Particularly the Identity, Authentication, Messaging portions.  I don't build Exchange servers (under normal circumstances) but I do manage all changes in the service and "own" the platform.</p>

<p>As <a href="https://devops.stackexchange.com/a/1007/10110">hvindin's answer</a> also calls out, I am equally responsible for evangelizing the platform I own as well as maintaining it.</p>

CC BY-SA 4.0
2017-04-24T21:17:28.107Z
2018-10-01T13:02:20.990Z
2018-10-01T13:02:20.990Z
blaughw
<p>I think you would be hard pressed to get a straight definite definition of a Platform Engineer.</p>

<p>Where I'm currently positioned everyone on the team starts out with their own special role but very quickly the end-game seems to be to feel comfortable enough to be called, or to call ones self, a platform engineer.</p>

<p>When I was first told that officially a platform engineer the brief explanation of what that meant, for me at least, was that I was going to need to do a whole lot more defending of my platform.</p>

<p>I wasn't quite so focused on helping our developers directly (although that's still the goal obviously) but as the platform owners our jobs was mostly to make sure that our developers where being good citizens by making sure we designed the platform so that we could show them what they did wrong if something happened and we could give them all the information they needed to fix their code.</p>

<p>The obvious implication of this is that our platform is perfect, which it obviously isn't. But at least we can support the developers in a way that gets them working on a solution on their end while we're fixing up our side of the agreement.</p>

CC BY-SA 3.0
2017-04-24T17:36:54.967Z
2017-04-24T17:36:54.967Z
hvindin
<p>I've been called many things over my career, most of them polite - more recently the work to build CI/CD pipelines has been termed "Platform Engineer" or "Platform Engineering".  The risk of such a title is that you get typecast into the role of an engineer who develops platforms for use by Developers and doesn't necessarily include any of the Ops bit of DevOps.</p>

<p>In my experience, however, the roles have involved a great deal of Operations Discipline work such as designing Major Incident Management Processes, Alerting, and Monitoring solutions.</p>

<p>In the role it "feels" like it has a lot in common with Site Reliability Engineering, in that both roles are engineering roles somehow set apart from software engineering they seem to have a similar <a href="https://trends.google.co.uk/trends/explore?q=Platform%20Engineer,Site%20Reliability%20Engineer" rel="noreferrer">Google Trends Pattern</a> though:</p>

<p><a href="https://i.sstatic.net/QHL6A.png" rel="noreferrer"><img src="https://i.sstatic.net/QHL6A.png" alt="Site Reliability Engineer vs Platform Engineer"></a></p>

<p>Is there a canonical definition of a Platform Engineer or is it like SRE simply an implementation of a DevOps capability within an organisation?</p>

CC BY-SA 4.0
2023-09-08T10:43:01.363Z
[What it takes to be a Platform Engineer in 2020](https://ataiva.com/what-it-takes-to-be-a-platform-engineer-in-2020/) covers the basics pretty well.
AO_
<terminology>
What is a Platform Engineer?
Richard Slater
# What is a Platform Engineer?

(Asked by: username_0 on 2017-04-24)

I've been called many things over my career, most of them polite - more recently the work to build CI/CD pipelines has been termed "Platform Engineer" or "Platform Engineering". The risk of such a title is that you get typecast into the role of an engineer who develops platforms for use by Developers and doesn't necessarily include any of the Ops bit of DevOps.

In my experience, however, the roles have involved a great deal of Operations Discipline work such as designing Major Incident Management Processes, Alerting, and Monitoring solutions.

In the role it "feels" like it has a lot in common with Site Reliability Engineering, in that both roles are engineering roles somehow set apart from software engineering they seem to have a similar [Google Trends Pattern](https://trends.google.co.uk/trends/explore?q=Platform%20Engineer,Site%20Reliability%20Engineer) though:

[![Site Reliability Engineer vs Platform Engineer](https://i.sstatic.net/QHL6A.png)](https://i.sstatic.net/QHL6A.png)

Is there a canonical definition of a Platform Engineer or is it like SRE simply an implementation of a DevOps capability within an organisation?

**Tags:** terminology

> **Comments:**
> **username_1**: [What it takes to be a Platform Engineer in 2020](https://ataiva.com/what-it-takes-to-be-a-platform-engineer-in-2020/) covers the basics pretty well.  

---

## 2 answers

### Answer by username_3 on 2017-04-24. Score: 16 | Accepted answer

I think you would be hard pressed to get a straight definite definition of a Platform Engineer.

Where I'm currently positioned everyone on the team starts out with their own special role but very quickly the end-game seems to be to feel comfortable enough to be called, or to call ones self, a platform engineer.

When I was first told that officially a platform engineer the brief explanation of what that meant, for me at least, was that I was going to need to do a whole lot more defending of my platform.

I wasn't quite so focused on helping our developers directly (although that's still the goal obviously) but as the platform owners our jobs was mostly to make sure that our developers where being good citizens by making sure we designed the platform so that we could show them what they did wrong if something happened and we could give them all the information they needed to fix their code.

The obvious implication of this is that our platform is perfect, which it obviously isn't. But at least we can support the developers in a way that gets them working on a solution on their end while we're fixing up our side of the agreement.


---

### Answer by username_2 on 2017-04-24. Score: 3

Source: I'm a Platform Engineer, (though not in a strict DevOps sense).

I manage Office 365 for my employer. Particularly the Identity, Authentication, Messaging portions. I don't build Exchange servers (under normal circumstances) but I do manage all changes in the service and "own" the platform.

As [username_3's answer](https://devops.stackexchange.com/a/1007/10110) also calls out, I am equally responsible for evangelizing the platform I own as well as maintaining it.


---

