3 ms·
It's important to understand their prior roles and responsibility in detail at the start of the interview. The Product Manager title can mean very different thi
by PragmaticPulp 6y ago
It's important to understand their prior roles and responsibility in detail at the start of the interview. The Product Manager title can mean very different things depending on the company.
At some companies, Product Manager is a high responsibility, high accountability position that drives the roadmap. They are responsible for deciding what gets built and ensuring that it's both feasible and will generate the highest ROI. They are accountable for moving the product forward and coordinating across departments to make sure the right work is getting done.
On the other end of the spectrum, some companies treat the Product Manager like a communication switchboard or a Jira ticket manager. These positions don't have much power, don't make major decisions, and mostly follow orders from someone else. They spend their days sifting through Slack channels, Jira tickets, and nagging developers for updated estimates.
The trick is to get the person to elaborate on their experience before you tell them what type of Product Manager you're looking for. The challenge is that if you describe the position too much up front, most candidates will simply adjust or embellish their experience to match what they think you want to hear. If you instead ask them detailed questions about what they did at previous companies, you'll get a more unbiased view of their prior experience.
> Here is the interview https://prodjeeves.com/transitioning-into-product-owner-role-interview/ https://prodjeeves.com/transitioning-into-product-owner-role...
Be careful about using Product Manager and Product Owner interchangeably. They mean different things at different companies.