A product manager's guide to evaluating a new role (without getting burned)

Most PM job searches end with a negotiation about salary. The conversations that actually matter, about product culture, engineering relationships, strategic clarity, and what the role will feel like in month six, often don't happen at all.

This is how PMs end up in roles that looked right on paper and felt wrong by the end of the first quarter. Here's what to ask, and what to listen for.

Understand where the product actually sits in the company

Not where it sits on the org chart, where it sits in terms of real priority. Ask the hiring manager: what are the top three things the company is trying to achieve in the next twelve months? Then ask where product fits in each of them.

If product is genuinely central, they'll be able to answer this concisely and confidently. If they pivot to talking about the product team's internal goals rather than business outcomes, that's a signal. It may mean product is a delivery function in this company, not a strategic one. That's not always wrong, but you should know it going in.

Also ask: when was the last time a PM recommendation materially changed the company's direction? How it happened, who was involved, and what the outcome was. Strong product cultures have an answer to this. Cultures where product is order-taking usually don't.

Get specific about the engineering relationship

This is the relationship that will define whether you enjoy the job. Ask to speak to an engineer or engineering lead as part of the process. If the company won't arrange this, that's information.

When you speak to them, ask what they find most useful about working with the product team. Ask what frustrates them. Ask how decisions get made when product and engineering disagree. The answers will tell you more than any interview with a hiring manager.

Watch for phrases like 'we're very collaborative' without specifics. Ask for an example of a specific decision where collaboration changed the outcome. If they can't give you one, the collaboration may be more aspiration than reality.

Ask about the last PM who left

This is the most useful question most candidates don't ask. Why did the last person leave? How long were they in the role? What did they go on to do?

You won't always get a fully honest answer. But the way the question is answered is revealing. If they struggle to explain it, if the answer is vague, or if the tenure was notably short, those are signals worth following up on. Ask what the company learned from that experience and what they'd do differently in the hire.

A company that has thought carefully about why a previous PM didn't work out is a better hiring partner than one that treats it as an embarrassing anomaly.

Understand what 'ownership' actually means here

'High ownership' is in every job spec. It means different things everywhere. In some companies it means you set the strategy and the team executes to it. In others it means you write the tickets and attend the standups. In others it means you're accountable for outcomes you don't fully control.

Ask directly: who has the final call on what gets built? When there's a conflict between what the PM wants to prioritise and what engineering or leadership wants, how does it get resolved? Has that happened recently, and how did it go?

You're not looking for a company where the PM always wins. You're looking for a company where there's a clear, fair process for resolving these tensions, and where the PM's input is genuinely weighted.

Evaluate the product honestly

Use the product before you accept the offer. If it's B2B and you can't access it, ask for a demo and watch carefully, not just what the product does, but the quality of the thinking behind it. Is it coherent? Does it solve the problem it claims to solve? Are there obvious gaps that haven't been addressed?

This matters because the product tells you about the company's product culture more honestly than anything a hiring manager will say. A product with years of accumulated debt and inconsistency tells you something about how decisions have been made. A product that's clean, coherent, and well-considered tells you something different.

Neither is necessarily disqualifying. But you should be clear-eyed about what you're walking into.

Trust the briefing you get before the interview

When we represent a role to a candidate, we give them a full briefing: what the company is actually building, what the team dynamic looks like, what the hiring manager is really testing for, and what we think you should explore in the conversation.

This briefing should prepare you to ask the questions that matter, not to perform in the interview, but to make a good decision about whether this is the right role for you. If the recruiter you're working with isn't giving you this, ask for it. If they can't provide it, that's a signal about how much they actually know about the role.