What is a technical product manager?

What changes when the customer is an engineer

Developers evaluate products by trying them, not by taking a demo. That inverts the entire go-to-market: documentation is the sales page, the first API call is the pitch, and a confusing error message is a lost customer.

Stripe's advantage came from taking this seriously earlier than anyone else. Docs, error messages and the quality of the first integration experience were treated as core product surface rather than support material, and developers made the buying decision before any salesperson was involved.

Vercel's position comes from the same recognition applied to deployment — that the workflow friction engineers tolerated was itself the opportunity.

The extra depth required

You need to hold a conversation about architecture without being carried. Not to design the system, but to distinguish a genuine constraint from a preference, understand why one approach costs three weeks and another costs three months, and notice when a technical answer is really a scoping decision in disguise.

This is also what makes discovery different. Engineers describe problems in terms of their current workaround, and interpreting that requires understanding the workaround.

Where the title gets misused

Two common misuses. Some companies apply it to any PM working with an engineering team, which is all of them. Others use it to mean a project manager for technical work, which is a different job entirely — closer to technical programme management.

Before taking a role with the title, ask who the customer is. If the answer is developers, platform teams or systems, it's a genuine technical PM role. If the answer is "the engineering team, and I'd coordinate their delivery", the title is doing something else.