Platform & Developer Experience
7 · 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
What this role tests
Themes, and where to learn them
These chapters are shared across every role that tests them, so preparation here compounds rather than being spent once.
Practice questions across all themes → · Back to Platform & Developer Experience →