Platform & Developer Experience
Platform Lead & Engineering Manager
A different job from senior platform IC, assessed on a different axis, and the one most often entered by accident.
What the job actually is
You run a team whose customers are other engineers inside the same company — which makes it the hardest kind of product management disguised as engineering management. Your users cannot be acquired, they can only be convinced; they can route around you; and your budget is justified by adoption you do not control.
The single test that separates candidates: can you run platform as a product? Roadmap, internal customers, deprecation, and the willingness to kill something you built.
Titles this hides behind
The loop
Prepare like this
- Prepare a deprecation story. Something you turned off, how you migrated the holdouts, and the one team that refused. Nothing demonstrates platform leadership faster.
- Know your adoption numbers from your last role — percentage of teams on the paved path, and the trend.
- Have the build-versus-buy framework ready, with a case where you chose buy and were right, and one where you chose build and were wrong.
- Be ready to defend headcount in business terms, not engineering ones.
Be ready for
- "Three teams refuse to migrate to your platform. What do you do?" Mandate is the weak answer. They want to hear you diagnose why the platform is not worth adopting yet.
- "Your platform team is seen as a blocker. Fix it."
- "What would you deprecate in your first ninety days, and how would you know you were wrong?"
Compensation
A day that is actually representative
| Time | What you are actually doing |
|---|---|
| 09:00 | Adoption numbers per team, and the trend. |
| 11:00 | A deprecation conversation with the team that will not move. |
| 13:30 | Roadmap against internal customer demand you cannot fully meet. |
| 15:00 | Justifying the platform's existence in a budget review. |
| 16:30 | Hiring — the two senior people who will define the next year. |
Real cases worth being able to discuss
The platform / stream-aligned / enabling / complicated-subsystem split has become the common vocabulary for organising platform work, precisely because it makes the platform's customer explicit.
Use it to say: “I use it to settle the recurring argument about whether the platform team should embed or provide — enabling teams embed temporarily, the platform team provides.”
A three-week plan
Week 1 — the numbers
Days 1–3: Reconstruct adoption, support load and time-to-first-deploy for a platform you know.
Days 4–5: Write the business case in the CFO's language.
Week 2 — the hard call
Days 1–3: Write a deprecation plan with a date, a migration path and a reversal criterion.
Days 4–5: Prepare the three-teams-refuse answer.
Week 3 — rehearse
Days 1–3: Platform strategy round, out loud.
Days 4–5: People stories: a manager you hired, one you got wrong.
The book for this field
Infrastructure & Reliability
Reliability and error budgets, capacity arithmetic, networks, storage and the restore you have not tested, the physical layer, a debugging method that transfers, running production, and an honest look at Kubernetes. Plus a Middleware section — web and application servers, messaging (IBM MQ, Kafka) and managed file transfer, from basics to licensing and cost.
Also read for this role
Cloud Platform Engineering
Seven chapters comparing the three major clouds where they genuinely differ: the compute spectrum and the ceilings that decide it, managed Kubernetes and the address exhaustion nobody plans for, identity models that do not transfer, networking and the internal traffic that outcosts your egress, storage and database traps, committed-use and spot mechanics, and an honest read on frameworks, market share and certifications.
Cross-cutting
Skills every archetype tests
These are shared across every field on this site — the same question asked in different vocabulary — so preparation here compounds rather than being spent once. The book above is specific to your field.
Practice the 35 Platform questions → · Back to Platform & Developer Experience →