Most early-stage startups split product and engineering into two separate people (and teams) way too early.
One team and its leader owns the "what." Another owns the "how." And then they spend half their time aligning with each other. By doing that at an early stage, you create a problem you don't need to have. Everything ends in never-ending alignment meetings, handoffs, and decision paralysis because no one knows who has the final say or who should close the discussion.
When One Person Holds Both
When one person holds boths, things get simpler:
- 👉 MVPs become actually minimal.
- 👉 Bad ideas die before they waste anyone's time.
- 👉 When something is stuck, there's no escalation, just prototyping, validating, and moving on.
The AI Factor
This matters even more now when AI has collapsed the distance between "idea" and "working prototype" from weeks to hours. Product people are expected to build prototypes. Engineers are expected to think about user value.
LinkedIn replaced their Associate Product Manager program with a "Product Builder" program that trains people across product, design, and engineering. Some companies are adding AI prototyping rounds to PM interviews. The old "I write the spec, you build it" model is fading.
The Catch
The catch? Finding someone who can genuinely merge both worlds is hard. Product thinking and engineering thinking pull in different directions, one pushes for speed and user value, the other for correctness and scalability. Holding that tension in one head without letting one side consistently win over the other is a skill that takes years to develop. Most people default to whichever side they came from. The ones who can actually manage that internal conflict, and make the right call depending on the context, are rare. But when you find them, everything else gets easier.
Have you worked at a startup where product and engineering sat with one person, or where the split caused friction?