Roles by discipline
Platform roles where the platform is the product
There is a version of this job where you build the thing that stops the pager firing, and a version where you answer it. Same title, same stack, frequently the same salary. What separates them is whether unplanned work is measured, whether the modernisation track has its own budget, and whether anyone has ever been told no on cloud spend. None of that is in the ad, so we ask.
What we ask before we post one
The questions the ad never answers.
- How many engineering teams does the platform serve, and how many people run it?
- What share of recent work was unplanned?
- How often did the pager fire outside working hours, and who carried it?
- Is there a funded modernisation track, or feature work with infrastructure attached to it?
- Can a product engineer ship to production without opening a ticket with your team?
- Who signs off cloud spend, and has anyone been told no?
What we will not post
We do not post an on-call rotation with a platform title on it.
For hiring teams
Hiring for this discipline?
We work through the role and hiring criteria with your team as part of embedded recruitment. Talk to Jonathan about what you need to hire.