Product and Platform Engineers
The divide between frontend and backend engineers is increasingly less useful:
Backend developers are often forced to choose between two paths: writing more frontend code to support their backend, or moving closer towards managing, maintaining, and building software infrastructure used by the former developers.
AI-enhanced developers have shifted the focus from simply writing code to creating great products. Startups are increasingly feeling this shift, running a more lean engineering team that uses LLMs and coding copilots to move faster.
Consider two different verticals: Product and Platform Engineers.
What are Product Engineers?
Product Engineers work backwards from the desired product experience to the set of technologies that enable it. They consider the frontend, backend, design, and everything in between to create a great user experience.
They don't need to understand every part deeply, a common misconception of "fullstack". Instead, they have a broad understanding of the available tools and deep experience applying those tools to build products.
Some qualities of a great Product Engineer:
Iterative: They value iteration velocity and incremental correctness. They'd rather ship, get feedback from customers, and adjust along the way—rather than building in a silo.
Customer focused: They aren't afraid to engage with customers and learn how to improve the product. At a larger company, the Product Manager might specialize here, but should work closely with the engineer to apply those learnings to the correct solutions.
Okay, so what does that leave the other half of the software engineers?
Product vs. Platform Engineering
While Product Engineers focus on building and enhancing features that solve end user problems, Platform Engineers focus on the infrastructure that supports the product.
Platform Engineering teams are building or buying tools to support Product Engineers and make them more efficient, productive, and happier. They're typically making the infrastructure choices for the Product teams.
Typically, platforms teams were only something accessible for larger organizations. Increasingly, a small but effective group of Platform Engineers can make incredibly impactful decisions, even for smaller teams. They are thoughtful about evaluating and purchasing software to grow with the scale of their product team.
Most startups are looking for Fullstack Engineers but actually need Product Engineers.
The best Product Engineers share two common qualities:
A passion for building high-quality experiences
A constant drive to learn and explore new ideas
They're not pixel-pushers; they're creators who take pride in their work and are not afraid to stand behind their products. They should have plenty of examples of their work, because so much of it is user facing.
The title shift from Fullstack → Product Engineer has some prior art.
Design has seen a similar shift. Titles like UI/UX Designer and Graphic Designer are increasingly being replaced by Product Designer.
Great Product Engineers don't stop at visually complete. They carefully consider the user journeys. What happens if there's slow (or no) internet connection? What if this API returns an error? How does this experience work on touch devices? What latency numbers should we strive for?
What seems like an excessive amount of polish to others is normal for these developers.
When I tweeted "Product Enginner > Fullstack Engineer", I was surprised by the response.
Product Engineers represent a shift in web development. Especially with the rise of AI, there's a growing need for developers who do more than "just write code" — developers who understand the bigger picture, who can work across various technologies, and who focus on delivering exceptional products to the end user.