Platform Engineering, two years in

Two years ago, every Series B–D scale-up we spoke to was hiring (or trying to hire) their first Platform Engineering team. The discipline had a moment, the conference circuit had its phase, and the briefs flooded in.

Two years later, the picture has settled. Platform Engineering as a discipline is now mainstream at scale-ups — and the shape of the work, the seniority of the hires, and the expectations on the function have all materially clarified.

What we now see in briefs

The typical Platform team at a Series C–D scale-up is four to ten engineers, led by a Head of Platform or Senior Engineering Manager, and reporting to a VPE or Director of Engineering. The team owns three or four things consistently: the deployment platform, the observability stack, the internal developer portal, and some opinionated subset of the security and compliance work.

What’s changed: the briefs now arrive with a clearer sense of what they want. Two years ago a typical brief was “we need someone to figure out our platform story.” Today the brief is “we have a Kubernetes-based platform, we have these specific reliability problems, we have these specific developer experience problems — we need a Principal Platform Engineer who’s solved this shape of problem before.”

This is healthy. The discipline has matured. The hiring is correspondingly easier — although still difficult enough that we get the briefs.

What we hear from candidates

The strongest Platform engineers we know are increasingly selective about which firms they’ll take meetings with. The most common candidate questions, in roughly declining order:

• What does the engineering leadership care about? (Platform engineers can spot indifference from a mile away.)
• What’s the realistic budget for the platform team? (Headcount is a proxy for organisational seriousness.)
• What’s the existing platform? (Greenfield is rare and not always desirable.)
• What does the on-call rotation look like? (Frequently a deal-breaker.)

The candidates we work with at Staff and Principal level are now in a position to be choosy. The good ones are choosing.

What separates the best Platform teams

In our data, the Platform teams that retain senior engineers and ship meaningful work have three things in common. First, they have engineering leadership that takes platform seriously as a discipline rather than as a cost centre. Second, they have a Head or Principal who can write — internal documentation, design proposals, and the careful artefacts that platform engineering depends on. Third, they have a healthy relationship with the broader engineering organisation rather than an adversarial one.

These are not exotic requirements. They are also surprisingly rare.

What we tell new clients

If you’re hiring your first Platform team, the highest-leverage hire is the Head of Platform or Principal IC, not the staffing-out below. Get that right and the rest follows. Get it wrong and you’ll re-staff in two years anyway.

We talk to firms about this regularly. The conversation is no obligation and frequently saves the firm money.