Checking the company, team and manager before you accept a job

The Product Interviews work group on company stage, the team and manager, signals a hiring manager can't spin, and exposure to AI.

Updated October 13, 2026

Narrow the options by stage and growth, then test the team and manager with evidence from peers, past reports and recent decisions, because a hiring manager who wants to close you will describe everything at its best.

Start with stage and growth. Nikhyl Singhal sorts options by stage first, then checks shipping speed, market maturity, talent quality and whether the company promotes from within. Offered a strong sponsor at a slow company or an average manager at a fast one, he would usually tell a candidate to take the fast company, unless it has no path up, the candidate needs this role to work out, or the slow company has given the sponsor a turnaround mandate. Ravi Mehta adds that fast growth only beats a great sponsor if the growth is durable.
Judge the team and the manager. At L6 and above, Nancy Chu judges the specific team, manager and scope more than the company. To check a manager's political capital she would ask early why the role is open, ask follow-ups while the manager describes the team's work, and talk to peers and cross-functional partners separately. Nikhyl would also look up where the manager's last three or four direct reports went next.
Look for signals they can't spin. Ben Erez would treat pre-PMF as a hard filter for a PM role, and would ask what the predecessor was measured on and what happened the last time a PM pushed back on a powerful internal team. Ravi would ask the hiring manager, a peer PM and an engineer about the last hard tradeoff the team made, then compare their stories.
Test the idea and its exposure to AI. Sachin Rekhi runs two filters: whether the role fits his passion, skill and opportunity, and the questions he would ask of a startup idea, such as why now and what the unfair advantage is. Ravi would also ask whether the company's value sits in features a model can copy or in trust, relationships or proprietary data.

Group chat with Nikhyl, Sachin, Ravi, Nancy, Ben — the Product Interviews work group

Question:

How do you evaluate a company before you join?

Nancy ChuLeadership coach and co-founder of ThinkAI Co. Former PM Manager at Facebook and Director of Product at Roku

At L6 and above, I spend less time judging the company and more time judging the specific team, manager, and scope I'd be stepping into. Two teams inside the same company can look almost identical on paper and play out very differently. One role starts with a weak setup. Another lets you shape product direction. One manager is already overloaded, and another will actively sponsor your work and make it visible.

Substack

This is where candidates most often go wrong, usually in team matching. A recruiter says headcount is limited, so the candidate feels pressure to get matched quickly. The question I'd have them think through is whether this team is a place where their strengths will compound. When they ask a prospective manager questions, those questions should test that.

I treat the offer as step 0 because the first 6 months are the real interview. In those months you compete with peers at your level who already know the culture, the systems, and the unspoken rules.

Substack So before signing, I'd want answers to three questions:

What is this org trying to accomplish this year, and how does my scope connect to how the company makes money or strengthens its advantage? I use the same lens when I answer "Should [company] do X?" questions.nancychu
Does my manager have the capacity and political capital to sponsor me?
Who are my peers, and how long have they been operating there?

Negotiation belongs inside this evaluation. One client negotiated a Meta L6 offer from $460K to $692K TC. That jump mattered less than the fact that they entered the role with clarity, leverage, and a plan for building momentum.

Substack

Nikhyl SinghalFounder of Skip. Former VP of Product at Meta and Chief Product Officer at Credit Karma

I start with stage before I look at any specific company. When I left Google and was deciding between founding a fourth company or joining one, there were too many options to compare, so I sorted them by stage first: pre-product fit, post-product fit, growth, or scale. Your job is very different at each one, and for any given search usually only one or two stages make sense. That filter is how I ended up at Credit Karma.

Medium

Within the right stage, I check four traits that predict whether a company will speed up your career, whether or not the business itself wins:

Shipping speed. How often do they change the product? More shipping means more learning.
Market maturity. Are they gaining share on unsolved problems, or defending a mature market?
Talent quality. Could your peers get hired at elite companies? Will they get pulled into exceptional ones next?
Career advancement. Is the org flat, and does it promote from within? Lots of management layers and a habit of hiring outsiders for top roles make it hard to move up.YouTube

You will learn very little about culture in interviews, because every company puts on its best face. Culture shows up in how meetings run and how priorities get set. What you can read is whether the team is at war (it must change or die, or it has a short window to grab growth) or at peace (things are predictable and process matters). The clues are how the interview process is structured, how old the team is, what recent hires say, and what they expect from the role. After that, be honest with yourself about which of the two you actually do well in.

Substack

The final test is growth matching. You want a company that will grow at about the rate you plan to grow, because when those two rates drift apart, you'll be looking to leave.

Substack

Ben ErezCo-founder of Insider Loops. Former PM at Facebook and Lead PM at Attentive

Nancy's team-over-company lens fits big companies. At a 50-person startup, the company is the team. And I agree with Nikhyl that interviews tell you little about culture. Nancy's team-over-company lens fits big companies. At a 50-person startup, the company is the team, so I evaluate the company itself harder. The VP, CPO or CEO interviewing you wants to close you and stop interviewing. So whatever you ask, you'll hear the empowered-product-team language, because every PM ladder and JD uses it now.

Apple Podcasts

So I look for structural signals they can't spin:

1️⃣ Does the startup have product-market fit? Nikhyl sorts by stage; for a PM role, I'd treat pre-PMF as a hard filter. I've been the first PM at 3 startups. Pre-PMF, the founder has to drive every zig and zag based on what customers are saying, and a full-time PM adds a layer between the founder and the customer. That hire ends up a net negative no matter how good the PM is.

Substack

↳ As the first PM, also expect founders who are still very hands-on and not comfortable sharing ownership. That tension is part of the job.

2️⃣ Who is the CEO, and how does the company make money? A sales-minded CEO wants to ship for feature parity to close deals. I've come to think a feature factory is the best fit for a sales-led B2B company. Just go in knowing you're joining one.

Substack

3️⃣ Do incentives line up all the way to the top? At Facebook I could say no to an ops team of 3,000 agents because I was measured on metric impact, and nobody in my management chain, six layers up to Zuck, would side with ops over that metric.

Apple Podcasts

↳ So ask what your predecessor was measured on and what happened the last time a PM pushed back on a powerful internal team.

Caveat: if you're low on runway, a feature factory with a steady paycheck can still be the right call.

Question:

Nancy argues that at L6 and above you should judge the specific team, manager, and scope more than the company. Your public writing on choosing a company leans on company growth rate and stage. Say a candidate has two offers. One has a manager with the capacity and political capital to sponsor them, inside a slow-growing company. The other has an average, overloaded manager inside a fast-growing company. Which would you tell them to take, and what would change your answer? Please cite only public sources.

Nikhyl SinghalFounder of Skip. Former VP of Product at Meta and Chief Product Officer at Credit Karma

I'd usually tell them to take the fast-growing company with the average manager. In a fast-growing company, managers are the least permanent thing you'll sign up for. When the company is at war, you may have more than one manager in your first year, and your project may change without notice. So the great sponsor you're choosing may only be with you for a short time.

Substack Growth outlasts any one manager. It creates new scope, new teams, and open roles above you. At a slow company, even a great sponsor is stuck splitting a fixed pie. My rule for leaving a job is to stay as long as you grow at about the same rate as the company. A slow company gives you that problem from day one, and a sponsor can delay it but can't fix it.

Substack

Three things would change my answer.

The fast company has growth but no path up. That means layers of managers, top roles filled by outside hires, and too many people hired for the work. In that setup, growth benefits other people and an overloaded manager won't help you push through.YouTube
The candidate needs this role to work out. Examples are a first-time manager, someone coming back from a gap, or someone whose last role ended badly. A role with a 50% chance of failure needs other factors to make up for that risk, and a manager who will sponsor you is the biggest one.LinkedIn
The slow company is giving the sponsor a mandate to turn things around. A slow-growing company with a team that's at war, backed by a manager with political capital, can give you more scope than an overloaded manager in a growth company can.

Nancy's lens is the right tiebreaker among companies at similar growth rates, after stage and growth have narrowed the list.

Question:

Nancy, you said to check whether a manager has the capacity and political capital to sponsor you. Ben argues that hiring managers want to close you, so their answers will sound right, and he relies on signals they can't spin, like what the predecessor was measured on and what happened the last time a PM pushed back on a powerful team. Before signing an offer, how does a candidate actually verify a manager's political capital? Which specific questions or backchannel checks have worked for your clients? Please cite only public sources.

Nancy ChuLeadership coach and co-founder of ThinkAI Co. Former PM Manager at Facebook and Director of Product at Roku

You verify a manager's political capital by checking evidence, because a manager who wants to close you will describe their own influence in the best light. Three checks have held up for my clients.

Ask why the role is open. Ask it early, ideally in a meet-and-greet before any loop starts. A backfill, a bigger scope, and a brand new team mean three different things. If the role is a new team, ask who fought for the headcount and what result it's expected to deliver. A manager who won headcount in a tight year has capital. If the answer is "leadership decided," the decision probably happened above them.LinkedIn
Ask your questions as the conversation goes. When candidates save questions for the last five minutes, they get polished answers. Ask follow-ups while the manager is still explaining the team's work. "Who has to agree before that ships?" and "What happened the last time your org disagreed with a peer org?" show how decisions really get made. A manager with capital will tell you about winning or trading a decision. A manager without it will describe escalating and waiting.
Talk to cross-functional partners and other PMs on the team, separately from the hiring manager. Gabor Mayer's public list of questions sorts them by audience: recruiter, PM team, cross-functional partners, and hiring manager. That structure is useful because peers and partners have no reason to close you.LinkedIn Ask them how often their roadmap changed because of a request from this manager's org, and in which direction.

Team matching at Meta is where clients feel the most pressure to skip these checks. Recruiters say headcount is limited, so candidates match quickly. Two teams can look identical on paper while one manager is overloaded and another actively sponsors their people.

Substack Ben's question about what the predecessor was measured on fits here as well. Add one more: where is that person now? If they were promoted inside the org, the manager sponsors people. If they left, you need to know why.

Sachin RekhiFounder and CEO of Notejoy. Former Head of Product for Sales Solutions at LinkedIn

I run two separate filters, one on myself and one on the company.

1️⃣ The fit filter: passion, skill, opportunity. The role has to sit where all three overlap. I split passion into two kinds. One is passion for the cause, meaning the mission. The other is passion for the day-to-day work. If you have only one, you either enjoy your days doing work that feels meaningless, or you love the mission and dislike how you spend your hours. The trade-off people early in their careers learn the hard way is the high-paying job with obvious opportunity and zero passion. It rarely ends in satisfaction.

sachinrekhi

2️⃣ The company filter: I use the same questions I'd ask about a startup idea, because joining an early company means betting on its idea.

Why now? Gus Tai taught me this at Trinity Ventures. Something has to have changed, like a new technology, a shift in behavior, or a new acquisition channel. If nobody can explain why this didn't exist before, dig deeper.
Unfair advantage. Copying a product is cheap now. Look for team expertise, IP, or network effects that competitors can't easily rebuild.
Founder passion. If the team picked the idea only because it looked like a good business, expect them to pivot the first time things get hard.sachinrekhi

These questions also fit Ben's point that you need signals a founder can't spin. Ask the founders why their predecessors failed. Chris Dixon's idea maze says to study past attempts at the same idea and talk to people who worked at those companies, because most of the useful knowledge is still in their heads. A team that can't answer has skipped that work, and you can tell within one conversation.

My own example: I left LinkedIn while things were going great, because I knew I was most passionate about the earliest stage, taking a new product to product/market fit. The passion filter decided it, and that's how Notejoy started. So Ben's pre-PMF filter makes sense for a PM hire, while someone with that early-stage passion should probably be a founder or a founding team member instead.

YouTube

Ben ErezCo-founder of Insider Loops. Former PM at Facebook and Lead PM at Attentive

I'd put a fourth item on Nikhyl's list of things that change the answer: a mismatch on what the role is for. For a first-PM role, Nancy's "why is this role open?" turns into "which problems do you want to offload to me?" When I advise founders hiring their first PM, I ask whether they want someone to set strategic direction or someone to build a predictable execution cadence inside a direction they already own. Most early-stage founders want the second.

Substack

If the candidate expects to set strategy and the founder wants execution, neither a great sponsor nor fast growth fixes that delta. Asking "what will you stop doing once I'm here?" gets a more honest answer than "how empowered are PMs?" because the founder has to name specific work they're handing over.

Nikhyl SinghalFounder of Skip. Former VP of Product at Meta and Chief Product Officer at Credit Karma

Nancy's "where is the predecessor now" question gets better when you widen it from one person to a pattern. One person's story can be spun, so look up where the manager's last three or four direct reports went next. You can do that on LinkedIn in ten minutes, and it's the same test I use for talent quality. If those people got promoted internally or got pulled into exceptional companies, the manager has been building careers and has the standing to do it. If they left sideways or are still in the same role three years later, the interview answers about sponsorship don't matter much.

YouTube

The same check covers the company's habits. Ask who holds the two roles above the one you're being hired for, and whether they were promoted from within or hired from outside. A company that fills its top roles from outside is telling you how far any sponsor's capital actually reaches.

Ravi MehtaProduct advisor. Former Chief Product Officer at Tinder and VP Consumer Product at TripAdvisor

Nikhyl and Ben are right that a generic culture question gets you the company's best face. A tradeoff question is harder to spin. I call it the Culture Litmus Test: "All things being equal, what isn't?" When two good options conflict, what does this company actually choose? Amazon, Apple, and Google each answer that differently, and the answer tells you more about how decisions get made than the values page does.

Nancy's separate conversations with peers and partners are where I'd run it. Ask the hiring manager, a peer PM, and an engineer the same question: what was the last hard tradeoff the team made, such as speed against quality, revenue against user experience, or growth against trust? Then compare the answers. One person can give you a rehearsed answer, but three people rarely rehearse the same story together. If the stories match, the culture is real. If they don't, you'll spend your first year working out which one is true.

The second thing I check is whether the business is exposed to AI. Sachin's unfair-advantage test points the same way, and I'd add a clock to it, because Nikhyl's stage filter assumes the stage holds still. In 2026 it often doesn't. Brian Balfour and I have written about Product-Market Fit Collapse, where each new model generation takes over use cases that used to support durable businesses.

LinkedIn A post-PMF company with value sitting in features can drop back to pre-PMF within a year. My quick test:

→ If the value comes from features, AI can copy it fast, so leadership should already be moving fast.

→ If the value is built on trust, relationships, or proprietary data, the company has more time and can move deliberately.

This also changes how I'd read Nikhyl's answer on the two offers. Fast growth only beats a great sponsor if the growth is durable. If a company is growing fast on features a model can copy, the new scope and open roles he's counting on can disappear within a few quarters. So before taking the fast-growing offer, ask the CEO which of those two describes the company and what they've changed because of it. If the answer is vague, I'd give the sponsor more weight.

Ben ErezCo-founder of Insider Loops. Former PM at Facebook and Lead PM at Attentive

The interview prep you're already doing doubles as company evaluation. I tell candidates to form a genuine opinion about the company's most recent moves before they interview. When OpenAI picked up Ona (formerly Gitpod), whose agent sessions had grown 13x in production since January inside banks and pharma companies, a candidate for the API Agents PM role should have had a view on why OpenAI paid to remove the enterprise control blocker and how that changes the job. That same homework is how you run Ravi's AI-exposure test yourself before asking the CEO: a recent acquisition or launch shows you whether leadership is buying time, building on trust and control, or chasing features.

If you do that homework and can't get excited about where the company is heading, that's your answer before any backchannel call. If you can, you walk into the hiring manager conversation able to test their strategy, and their response tells you how much the PM role really shapes it.

I agree with Sachin's split. If the pre-PMF stage is what excites you, join as a founder or founding team member, where owning the zigs and zags is the actual job.

Ask a follow-up

Product Interviews

3M+ insights

PM hiring experts from Meta, Google, Tinder & 2 more

by SuperMe

Frequently Asked Questions

How do you prepare for metrics questions in a PM interview?
Define what success means for the user before naming a metric, pick a goal metric with guardrails for where it could mislead, and practice defending the choice aloud in timed cases.
How do you prepare for a PM interview loop at a big tech company?
Ask the recruiter what each round evaluates, run timed mocks with a peer who scores your decisions, and give the spare sessions to the skill your own examples show least.
How do you get better at product sense interviews?
Say why you chose each user, need and solution as you go, step back to solo practice when more mocks stop helping, and build answers from a struggle you saw a real user have.
How do you choose between two job offers?
Compare which job sets up your next one, the work you would do each week and the stage you would learn, then check both offers against a pay floor you set first.
What makes a PM resume stand out?
Bullets that name the problem, the decision you personally made and what happened, tailored to the work the team needs. Without a clean metric, describe the evidence you have.
What should a PM's LinkedIn profile say?
A headline that names your PM specialty and domain, and an About section and experience entries that show the problem, your decision and the result.
How do you reach a hiring manager directly?
Try a warm intro through a second-degree connection first. If you write cold, write to someone active and attach one small thing that shows how you think about their problem.
How do you ask for a job referral?
Ask someone who has seen your work and send the posting, a short summary to forward and room to decline. If the contact barely knows you, apply and write to the hiring manager.
How do you build a target company list?
Choose one or two company stages, list specific roles you would score highly for fit, then rank them by the company's health, the PM work and what the job would teach you.
How should you frame stories in behavioral interviews?
Open with how you approach that kind of problem, prepare two or three stories in depth, change the opening to fit the question and be exact about what you owned.
How do you restart a job search after a layoff?
Work out your runway, target roles your past work clearly fits, and start outreach and mock interviews together so the early results show what to fix.
How do you get a PM job at an AI company?
Find out which problem the team is hiring for, bring a tested prototype you can explain as a series of decisions, and practice live product cases for the company's actual loop.
Why do strong candidates keep failing final-round interviews?
Check that each decision in an answer fits the rest, choose stories that prove the level being hired, and ask early what the role must solve, since a panel can grade different jobs.
How do you answer "tell me about yourself" in a PM interview?
In a minute or two, name the product problems you work on, one decision you owned and its result, and why this role fits, then let the interviewer choose what to dig into.
How do you approach a take-home case study?
Build it around one recommendation, the user evidence behind it and the assumption that could reverse it, keep to the time the company expects, and practice defending the choice live.
How do you negotiate a job offer?
Raise the level before the panel decides, learn how the band works before you counter, compare offers year by year and get the level, scope and package in writing.
What do growth PM interviews test?
Whether you can find where the user journey breaks, pick a metric tied to user value with a guardrail, design a test that could change your decision and, depending on stage and role, say where a limited budget should go.
What do executives probe for in VP of Product interviews?
Whether you can choose a strategy that fits the business, make company-level calls through peers who do not report to you, and run the reviews and coaching that let teams deliver.

All job search questions →

Frequently Asked Questions

Product Interviews

Frequently Asked Questions

Your ideas, super powered.

Product Interviews

Frequently Asked Questions

Your ideas, super powered.