I've been watching a slow convergence over the past 3 years and I think it's time to name it.Platform engineering is not a specialisation of software engineering. It is becoming the context in which all software engineering happens.The distinction that used to exist product engineers who build features, platform engineers who build the infrastructure those features run on is collapsing. Not because the work is the same, but because the platform is increasingly inseparable from the product.Let me be specific about what I mean.The Feature Is the PlatformFive years ago, a "platform" meant the infrastructure layer: Kubernetes, CI/CD pipelines, monitoring systems. Something product teams used but didn't think about. The plumbing.Today, for an increasing number of companies, the platform is the product.Stripe's developer platform is the product. Twilio's API infrastructure is the product. Vercel's deployment platform is the product. These companies sell developer experience, and the platform engineering team is not a supporting function — it is the product engineering team.For organisations that don't sell to developers, the same dynamic is playing out internally. The Internal Developer Portal, the Golden Path, the self-service infrastructure — these are what enable the product teams to ship features. The quality of the platform directly determines the velocity of the product. The platform IS the competitive advantage.In this world, the distinction between platform engineering and software engineering starts to look artificial.The AI InflectionAI is accelerating this convergence in a specific way.When AI-powered features move from "nice to have" to "table stakes" — which is happening faster than most organisations anticipated — the infrastructure required to support them becomes a primary product constraint.A product team that can't ship an AI feature because the platform doesn't support LLM inference, or because there's no evaluation pipeline, or because the cost attribution for AI workloads is missing — that product team is blocked by the platform's capability gaps.The platform is not neutral infrastructure anymore. It is the ceiling on what the organisation can ship.That makes platform engineering not just important, but strategically central in a way it has never been before.What This Means for the People in the RoleIf platform engineering is becoming the central technical function rather than a supporting function, several things follow:Platform engineers need product skills. Understanding your developers as users, measuring adoption, designing for self-service, iterating based on feedback — these are product management skills. The best platform engineers I know already think this way. It will become a baseline expectation.Platform engineering compensation should reflect strategic importance. The persistent gap between platform engineer and product engineer compensation at many organisations is based on an outdated model where platform was supporting. As platforms become strategic, compensation models will need to follow.Platform engineering leaders will have direct business impact. Not "we improved developer velocity by 30%." "We enabled the company to ship three new AI-powered product lines in Q2 that wouldn't have been possible on the previous platform." The business case becomes direct and measurable.The Thing I Keep Saying That People Push Back OnWhen I tell senior engineering leaders that their platform team is now as important as their product team, the most common pushback is: "But they don't ship revenue."This is true in the same way that saying "the road doesn't carry passengers" is true. The road is what makes the transportation possible. The platform is what makes the product velocity possible.In a world where delivery speed is the primary competitive advantage — and it is, in almost every software-driven sector — the constraint on delivery speed is the platform.The teams that understand this are making platform investments that pay off in product velocity. The teams that don't are wondering why their product teams are shipping slower than their competitors, quarter after quarter, despite having similar headcount and similar technical talent.Platform engineering didn't eat the world. But it's eating the constraints on the world.And I think we're just getting started.Agree, disagree, or want to add nuance? Make the argument. I read every comment.