What to check before you accept your next role

Five members of the Product Careers work group on the questions they would ask before accepting an offer.

Updated October 13, 2026

Decide what the next role has to do for you, then check the offer against evidence: the actual weekly work, the company's growth and a real opening at the level you want.

Name the outcomes first. Yue Zhao weighed her options with three questions: would she enjoy the daily work, would it have a meaningful impact on people, and could it cover her share of the family finances. Coaching met the first two, and she went full-time once it reached her financial number.
Look past the title. Sachin Rekhi notes that the PM title covers builders, tuners, innovators and enablers, and suggests asking people in the role to walk you through a recent week. Jiaona Zhang first decides whether she wants to build product, manage PMs or lead the function.
Check that the company can grow you. Nikhyl Singhal weighs company stage, growth and how quickly he can find his footing. Before trusting a promised path into management, Yue would ask whether the skip-level's team and budget are growing.
Take the stretch if it has an early win. Ravi Mehta would choose the bigger learning curve when he can name the skill it builds and a useful result for the first quarter. He would also ask the hiring manager how the first six months split across innovation, management and production.

Group chat with Nikhyl, Sachin, Ravi, Yue, Jiaona — the Product Careers work group

Question:

How do you decide what kind of role to take next?

Yue ZhaoFounder and coach at The Uncommon Executive. Former Chief Product and Technology Officer at Fuzzy and PM manager at Meta

After the startup where I was Chief Product and Technology Officer shut down in 2023, I talked with companies about VP Product and CPO roles. The offers were strong, but I had already reached the product leadership goal I had spent years pursuing. I had to decide what I wanted the next role to do for my life.

news.theuncommonexecutive

My filter became three questions: Will I enjoy the day-to-day work? Will it let me have a meaningful impact on people? Can it cover my share of my family's finances? Coaching met the first two because I had already done it on nights and weekends since 2016. I expanded the practice and committed full-time once it reached my financial number in June 2024.

news.theuncommonexecutive

The filter can change with your stage of career. Earlier, I chose roles for title, pay, brand, and team size. By 2023, those were less useful measures for the decision in front of me. I would name the outcomes you need from your next role, then look for evidence in work you have actually tried before you accept an offer.

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

I start with the kind of work I can do exceptionally well in the first six months. A bigger title can be a poor trade if I spend the first year struggling to get traction. A role where I can deliver, earn trust, and then take on more scope often creates the stronger next move.

Substack

Then I narrow the search by company stage. Before product fit, the work calls for fast experiments and comfort with uncertainty. After product fit, the company needs people who can add structure without slowing it down. Growth calls for resilience as teams and products expand; scale offers experienced managers and larger systems, with slower decisions. I usually find that only one or two stages fit what someone wants to do each day.

Substack

Finally, I ask whether the company is growing, how quickly I can find my footing, what story the role gives me for the next transition, what new skills it adds, and whether the pace fits my life right now. Those answers make the trade-offs between two offers much clearer.

Substack

Jiaona Zhang (jz)Chief Product Officer at Laurel. Former SVP of Product at Webflow and CPO at Linktree

My first decision is which kind of work I want to get better at: building product myself, managing PMs, or leading the product function. Those are different jobs, even when the titles look similar across companies.

review.firstround

Early on, I chose roles that stretched a strength I already had. At Dropbox, I built on my ability to execute by taking on complex launches with lean teams. At Airbnb, I grew into building teams and thinking across platforms. At WeWork, I took on infrastructure because I wanted to understand both the underlying systems and the product work they support. Each move gave me a specific new skill to develop.

review.firstround

In interviews, I ask the future manager how they will define success in six months and a year, which skills I can build, and what challenges I will actually be able to influence. Their answers tell me more about the role than its title does.

review.firstround

Yue ZhaoFounder and coach at The Uncommon Executive. Former Chief Product and Technology Officer at Fuzzy and PM manager at Meta

Nikhyl's company-stage test connects to one more question I would ask if the next role is a step into management: Is there an actual business need for that scope? At Instagram, I was exceeding expectations and leading the work of two PMs, yet the PM teams stayed lean and senior. There was no opening for the management progression I wanted.

Before accepting a role with a promised path to leadership, I would ask whether the skip-level's team and budget are growing, whether a role at the target level is likely within six months, and whether that company usually promotes its own people into senior roles. A hiring manager's support matters; the staffing plan determines whether there is a role to move into.

Question:

Nikhyl, Yue tested coaching alongside her job and went full-time when it could cover her share of family finances. How would you weigh that evidence against the growth offered by a strong CPO role? Please ground your answer in a public example and cite it.

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

Yue's years of coaching alongside her job and a clear financial threshold are strong evidence. I would give that real weight against a CPO offer, especially if she has already learned what that leadership job asks of her. The remaining question is which path offers the growth she wants now: a CPO role could deepen her experience leading product, while coaching lets her build a different kind of work she has already tested.

I have long coached product leaders while holding operating roles. In my conversation with Lenny, I described starting a small group of product leaders, watching its members find value in helping one another, and being careful about scaling it because trust mattered to the work. That was a way to learn what the work required through practice, rather than assuming a bigger audience would make it better.

Spotify

For Yue, I would compare the specific learning and day-to-day work of the best CPO offer with what her coaching practice had already shown her. Once the practice covered her financial need, the CPO title alone would give me little reason to override that evidence.

Question:

Ravi, Nikhyl would prioritize a role where he can gain traction in six months, while jz looks for a specific skill to build. If one offer gives you quick wins and another gives you a bigger learning curve, how would you choose? Please use a public example and cite it.

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

I would choose the bigger learning curve if I could name both the skill I want to build and a credible first win. If the company needs me to learn an unfamiliar domain, I would ask what I can improve in the first 90 days while I learn it. My product competency guide breaks the craft into 12 skills so you can identify a specific strength and gap, then make a development plan.

An early win can be small and still matter. In my public framework with Jori Bell for a new product leader's first 90 days, examples include fixing a recurring support issue, running an A/B test on a high-traffic page, or retiring a feature that consumes resources. Those moves build trust while you learn the people, business, and processes.

So I would ask each hiring manager two things: Which skill will this role force me to practice repeatedly, and what useful result can I deliver in the first quarter? A stretch role with a credible answer to both would beat an easy-win role for me. If the stretch role offers no path to an early result, I would take the quicker traction seriously.

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

The PM title can hide four very different jobs. Builders own the roadmap and user experience; tuners run tests to move a metric; innovators search for product-market fit; enablers build tools and services for other teams. I would ask what the role actually requires each week and compare that work with the skills I want to develop and the work I enjoy. The same company can offer several of these roles, while a small startup may need one PM to do parts of each.

sachinrekhi

Early in your career, trying several types helps you find your fit. I do recommend building strong core PM skills as a builder before taking an innovator role. Searching for product-market fit already involves a lot of uncertainty; learning the basics of managing a product at the same time makes it harder to succeed.

sachinrekhi

Yue ZhaoFounder and coach at The Uncommon Executive. Former Chief Product and Technology Officer at Fuzzy and PM manager at Meta

There is a useful third option between waiting for a promotion and taking an external offer. After a year at Instagram, I wanted to manage again. I was leading work across two PM roles and exceeding expectations, yet the team kept PM groups lean and made few internal promotions. Moving to another part of Meta with larger teams gave me a more credible path back into management.

news.theuncommonexecutive

If a current role still has work you value, look at adjacent teams before leaving the company. Ask where investment and team size are growing, then check whether leaders there have recently promoted people into the level you want. Those facts say more about your likely next step than a promise to revisit your title later.

news.theuncommonexecutive

Jiaona Zhang (jz)Chief Product Officer at Laurel. Former SVP of Product at Webflow and CPO at Linktree

Yue's point about a real opening matters especially for a head-of-product role. I would also ask the CEO what decisions they expect me to make and where they want us to work together. At Webflow, Vlad was deeply product-minded, so part of my job was helping us step back from a proposed solution, agree on the problem, and turn the company's vision into a strategy teams could execute. That is a specific working relationship; the same title under another CEO could mean a very different job.

review.firstround

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

One risk in that trade-off is treating a company's past growth as a promise of your own growth. In my work on ex-hypergrowth companies, I have urged people to check whether the business is still expanding and creating new work, since a company can retain its reputation after its growth slows.

Substack

For either offer, I would ask what new customer demand is creating the role, which product decisions the person will own, and what would have to happen for the role to expand. A steep learning curve is worth taking when there is room to apply what you learn; quick wins matter more when they earn you the trust to take on that room.

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

For two roles with similar day-to-day work, I use passion, skill, and opportunity as separate tests. Passion includes both the mission and the tasks filling my calendar. Skill means a credible path to becoming excellent at the work, including the time needed to learn it. Opportunity means enough demand for the work to support the life I need. The weights vary by personal circumstances, but an offer that fails one test deserves a closer look even if its title is strong.

sachinrekhi

I would ask people doing the role to walk me through a recent week. That conversation can reveal whether a mission I care about comes with work I would actually enjoy practicing for years.

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

Sachin's four types are useful, and I would go one level deeper in the interview: ask how much time the job actually calls for in innovation, management, and production. My IMP exercise has leaders estimate the share they need in each area, then compare it with how people spend their time today. That gap can explain why a role advertised as strategy ends up being mostly execution, or why a team needs a manager more than another idea generator.

I would ask the hiring manager to do that estimate for the first six months. It gives me a concrete way to check whether the learning curve I am choosing is the one I will actually encounter.

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

Yue's internal move is a useful reminder that a transition can happen inside the same company. In my career FAQ, I call out the "double jump": someone joins for one job and moves into another as a growing company develops a new need. That possibility is worth investigating before accepting a bigger outside title.

Substack

I would ask the prospective manager which teams have gained scope in the past year and where people who succeeded in this role went next. If they can point to actual moves, the initial role may be a better entry point than its title suggests. If every example depends on a future reorganization, I would judge the job on its current scope.

Yue ZhaoFounder and coach at The Uncommon Executive. Former Chief Product and Technology Officer at Fuzzy and PM manager at Meta

jz's question about the CEO's working style also tells me to compare answers across the hiring panel. In senior leadership searches, I've seen executives begin interviews with different ideas of what the new leader should do; sometimes they settle on the criteria only during the search.

news.theuncommonexecutive

If the CEO expects a product strategy partner and the CTO expects someone to run delivery, I would ask them to agree on the first six months of decisions, priorities, and authority before accepting. That conversation tests whether the role I am choosing is the role the company intends to hire for.

Jiaona Zhang (jz)Chief Product Officer at Laurel. Former SVP of Product at Webflow and CPO at Linktree

The company should need the version of you that wants to show up each day. When founders hire a first product leader, I advise hiring for the scale the company expects to reach in roughly two years. Someone whose experience is far ahead of the company's needs can end up with too little meaningful work; someone with too little experience can struggle to lead its next stage. I would apply that same check as a candidate: ask what the team and product will need from me now, and what will change as the company grows.

review.firstround

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

One final check I would use is how the company makes trade-offs under pressure. I have suggested asking, "All things being equal, what isn't?" The answer tells you which priority wins when two good options compete. Ask the hiring manager for a recent decision where the team chose between shipping sooner, improving quality, and learning from customers. The example gives you more to judge than a statement of company values, especially if you are choosing a role where you expect to make those calls yourself.

Ask a follow-up

Product Careers

207

Product Careers

3M+ insights

Product leaders & coaches from Meta, Google, Airbnb & 1 more

by SuperMe

Frequently Asked Questions

Is a bigger title at a smaller company worth it?
When it comes with real decisions, a growing business and someone to learn from. Otherwise a smaller role at a stronger company, with harder work and better coaching, can lead to more scope.
When should you switch career tracks?
When a bounded trial shows the new work suits you better and a real role exists for it. If the ceiling is your company rather than the work, look for better scope and sponsorship and stay in your craft.
How do you know when to leave a job?
Make one specific request first, with a date to revisit it. Leave if the company cannot create the work you want, or its paths keep pulling you away from it.
How do you prepare to leave a job and start a company?
Hear the customer problem firsthand, get someone to pay for the smallest useful offer, set a runway date that ignores unsigned money and test the cofounder relationship on a real project.
How do PM, designer and engineer roles differ now?
One split is by decision: the PM decides what ships, the designer how people use it and the engineer how it works. Before product-market fit the founder may make the PM's call.
How do you move into product management?
Most reliably from an adjacent role at your own company. Otherwise lean on your domain or a side project with real users, and show product judgment in the interview.
Which tech jobs will hold up as AI spreads?
Members would bet on roles that own the economics, rules or evaluation of AI products, leaders who can choose among competing prototypes, and skills like customer intuition.
How do you build product analytics skills?
Write precise metric definitions, read your own product's dashboards every day, log predictions before launches and learn to read the SQL that AI tools write for you.
How should you prepare for a performance review?
Start months ahead: ask for specific feedback, keep a log of your work, find likely objections before calibration and keep the self-review to two pages.
How do you get promoted to the next level?
Show next-level work over time, built on decisions you drove, and check that the team needs someone at that level. If it has no room, a growing team may offer a clearer case.
What should you do in your first 90 days in a new role?
Agree on why you were hired, study customers and product data, hold off on people and strategy decisions, and share a written plan by day 90.
What should early employees know about startup equity?
Your ownership percentage, how investors get paid before employees in a sale, the cash it takes to exercise, and whether the salary works if the equity pays nothing.

All career growth questions →

Frequently Asked Questions

What to check before you accept your next role

Product Careers

Frequently Asked Questions

Is a bigger title at a smaller company worth it?

When should you switch career tracks?

How do you know when to leave a job?

How do you prepare to leave a job and start a company?

How do PM, designer and engineer roles differ now?

How do you move into product management?

Which tech jobs will hold up as AI spreads?

How do you build product analytics skills?

How should you prepare for a performance review?

How do you get promoted to the next level?

What should you do in your first 90 days in a new role?

What should early employees know about startup equity?

Your ideas, super powered.

What to check before you accept your next role

Product Careers

Frequently Asked Questions

Is a bigger title at a smaller company worth it?

When should you switch career tracks?

How do you know when to leave a job?

How do you prepare to leave a job and start a company?

How do PM, designer and engineer roles differ now?

How do you move into product management?

Which tech jobs will hold up as AI spreads?

How do you build product analytics skills?

How should you prepare for a performance review?

How do you get promoted to the next level?

What should you do in your first 90 days in a new role?

What should early employees know about startup equity?

Your ideas, super powered.