The Product-Adjacent Inroad
Break into PM by moving internally from a product-adjacent function, trading domain knowledge for the role.
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 85%
Gupta's path-into-product framework, informed by her own engineering-to-PM move at LiveRamp and years of teaching PM at Stanford GSB. Don't switch company and function simultaneously. Join a product-adjacent function, build credibility, then convert — bringing a specific asset (support's problem knowledge, sales' objection handling, engineering's technical depth) that means you only need training on core PM, not on the business or the technology.
Origin
Anneka Gupta (CPO, Rubrik; lecturer on product management at Stanford GSB), based on her own move from software engineer to PM at LiveRamp and on observing which paths her Stanford students actually succeed with.
Core principles
- 01Switching company and function at the same time is the hard mode; do one at a time.
- 02Credibility inside the company is the currency that buys a product leader's chance on you.
- 03Nearly every function is product-adjacent — what function does product not engage with?
- 04Bring an asset: the function you came from is what makes you worth the bet.
- 05The real PM skill is driving increasing clarity out of ambiguous situations — not tools.
How to run it
- 1
Get in via a product-adjacent function
Join a company in the closest product-adjacent role you can get — support, sales, engineering, product marketing. Prefer moving into product inside a company you're already in over trying to switch companies and roles at once.
- 2
Build credibility by crushing the job you have
If you don't yet have credibility in the company, go crush your current job first. Credibility is the precondition for a product leader taking a chance on you without PM experience.
- 3
Calibrate whether to declare the ambition
Company stage decides this. At a 20-person startup with no product team, Gupta said in her engineering interview that she wanted to become a PM — worth saying. At a 5,000-person company, telling a product marketing hiring manager you actually want product will likely land badly.
Pro tip The smaller the company, the more openly you can declare the trajectory.
Watch out Declaring the ambition in a large-company interview for a different role can cost you the role and the inroad.
- 4
Raise your hand into product work
Interact with the product team, take on projects with product surface area, and build a relationship with a product leader who can take a chance on you. At a small startup with no PM function, simply do the product management work nobody is doing.
Pro tip At a tiny company, the PM work is unowned — take initiative and you effectively create the inroad.
- 5
Convert with your function-specific asset
Make the case on what you bring: from support, deep knowledge of the biggest problems customers call in about; from sales, what resonates and how objection handling works; from engineering, how the product is actually built. You need training on core PM — not on the business or the technology.
Pro tip The transferable skill to develop and demonstrate is taking ambiguous situations and consistently driving more clarity over time — not learning Figma or a process.
In the wild
She joined LiveRamp as a software engineer at 20 people and said explicitly in the interview process that she wanted to become a product manager — worth saying because the company had no product team yet and she wanted to signal the growth path.
→ She moved into product inside the company and ultimately became President, GM and head of product over 11 years.
Looking at how her Stanford GSB students actually land PM roles: very few go directly into a PM role at an established company (and most who do already had PM or engineering experience). The vast majority join product-adjacent roles, or go to small startups where they might be the first PM or run product-plus-chief-of-staff.
→ The two consistently successful paths are the adjacent-function inroad and the very-small-startup route — direct entry into an established company is the exception, not the plan.
Common mistakes
Trying to learn the tools instead of the skill
Gupta's students most often asked to be taught Figma and PM tooling. The actual job is taking ambiguous situations and consistently driving more clarity over time; tools and process are not what makes you successful.
Switching company and function at once
You arrive with neither PM experience nor internal credibility, so nobody has a reason to take a chance on you. Move one variable at a time.
Declaring the pivot in the wrong context
Telling a 5,000-person company's hiring manager you're interviewing for product marketing but really want product will likely be received badly and cost you the entry point entirely.
Is it for you?
Best for
Aspiring product managers in engineering, support, sales, or product marketing roles trying to make the transition into product.
Not ideal for
Experienced PMs looking for their next role, and anyone unwilling to spend a stretch in a non-PM function first.
From the transcript
“I definitely think doing it within the same company is a lot easier than trying to switch companies and switch jobs at the same time”
“take on projects and do things that allow you to get some experience and build a relationship with a leader on the product team”
“I think join a product adjacent function which honestly pretty much every function is product adjacent”
“the vast majority of them are joining product adjacent roles or they're going to small startups where they might be doing product management”
“I think what you need to learn to be successful is how to take very ambiguous situations and consistently drive more and more clarity over…”
From the episode
Becoming more strategic, navigating difficult colleagues, harnessing founder mode, and more
Anneka Gupta (Chief Product Officer at Rubrik)