You Hired a Developer but Expected a Product Manager

You hire a developer, hand over a feature list, and later feel disappointed that nobody challenged the list.

The developer may have done exactly the job you hired them to do. The missing responsibility was product ownership.

Do Not Order a Taxi and Expect a Tour Guide

A taxi driver can take you efficiently to the address you provide. A tour guide helps decide where you should go, what is worth seeing, and how to use limited time. Both roles are valuable. Confusing them creates a bad trip and an unfair evaluation.

Software work has the same distinction. Implementing a defined behavior, designing the technical route, and deciding which customer problem deserves investment are connected but different responsibilities.

“Developer” describes technical capability. It does not automatically assign product strategy, research, prioritization, or stakeholder coordination.

Name the Decisions You Need Help With

• Who will clarify the user and business outcome?
• Who can remove or reshape a requested feature?
• Who decides when evidence is sufficient to release?
• Who reconciles design, engineering, commercial, and operational constraints?
• Who owns the result after the implementation is technically complete?

A strong engineer may contribute excellent judgment to all of these. The mistake is assuming that contribution, authority, and accountability are included without discussing them.

Test Product Thinking With a Real Problem

During evaluation, describe a user situation instead of handing over a polished specification. Listen for questions about the current workflow, risky assumptions, smallest valuable outcome, failure cases, and proof.

Ask what they would not build. Somebody who can only add requirements may be a capable implementer and still not be the product partner you need.

Pushback Must Be Useful

Having opinions is not enough. Good pushback connects a concern to evidence or a clear risk and proposes a route forward.

For example: “I would not build the admin dashboard in the first release because the team can perform that operation manually while we test the customer journey. Here is the threshold that would justify automating it.” That is a product decision a founder can evaluate.

Sometimes You Need More Than One Person

One product-minded engineer cannot always replace product management, design, research, and technical delivery. Complex products need distinct expertise and enough capacity. Combining roles to save coordination can simply hide missing work.

Hire the role you need. Then give that role the context and authority required to do the job.