Latest / The Internal Move Podcast with Fexingo: Lateral Roles, Internal Transfers, and Staying at Your Company / How to Use an Internal Transfer to Break Into Product Management
Transcript
- Lucas: Let me start with a specific number. According to a 2025 LinkedIn analysis I saw, about 15 percent of product managers came from a completely non-product function within the same company. That is not a huge number, but it is growing — and it is significantly higher than it was five years ago. Luna: So more companies are actually looking internally first for PM talent? Or are people just getting better at pitching themselves? Lucas: I think it is a bit of both. But the really interesting thing is that internal transfers into product have a higher one-year retention rate than external hires — something like 92 percent versus 78 percent, according to a Reforge study I read. That gives internal candidates an argument that most people never use. Luna: That is a massive stat. Why would hiring managers not prioritize internal candidates more? Lucas: Partly because internal candidates often lack the formal product portfolio. They have not shipped a feature from scratch. They have not owned a backlog. So the hiring manager defaults to the person who has done it before somewhere else. But the thing is, product management is one of those roles where domain context matters enormously. If you already know the customer, the data, the internal systems — that is a huge head start. Luna: Okay, so how do you actually make that case? Let us say I am a senior marketing associate at a mid-size fintech. I want to move into product. What is the first concrete step? Lucas: First step is to stop thinking about your resume and start thinking about your internal project portfolio. The people who successfully transfer into product almost always have two or three examples where they acted like a product manager without having the title. Maybe they led a cross-functional initiative to improve the onboarding flow. Or they ran an A/B test on a feature and presented the results to engineering. Those are product muscle moves. Luna: So it is less about taking a course and more about doing the work inside your current role? Lucas: Exactly. I talked to a woman named Priya who did this at a payments company. She was in customer marketing. She noticed that the product team had no visibility into why certain user segments churned after the first transaction. So she built a churn analysis dashboard using SQL she taught herself over two weekends, and she walked the PM team through it. That single project became her portfolio piece. When a junior PM role opened up six months later, the VP of product already knew her name. Luna: And she did not ask for permission first? She just built it? Lucas: She asked her manager if she could spend 20 percent of her time on a cross-functional exploration. That is a key move. You frame it as a learning experiment that benefits the team. Most managers will say yes if they see it as skill-building that does not hurt your core deliverables. And if your manager says no, that is useful information — it tells you whether internal mobility is actually supported at your company. Luna: Right. And if the answer is no, you might want to look externally. But let us assume the answer is yes. What is next after you have one or two projects? Lucas: Next is the shadow board. Not a formal advisory board — I mean a group of three to five people who already work in product and who you can observe, ask questions, and eventually get feedback from. This is not mentorship in the traditional sense. You are not asking them to be your coach. You are asking if you can sit in on their sprint retrospectives or their customer research calls. Most product people love talking about their work, especially if you show genuine curiosity. Luna: And you want a mix of people — maybe a senior PM, a product designer, and a data analyst, right? Lucas: Yes. The goal is to absorb the vocabulary and the decision-making framework. You want to understand how they prioritize, how they say no to stakeholders, how they write a product requirements document. That cultural fluency is what makes you seem like someone who already belongs on the product team. When you finally interview, you will not sound like an outsider trying to break in — you will sound like someone who has been preparing for months. Luna: If today was actually useful to you, the way these stay ad-free is listener support — buy me a coffee dot com slash fexingo. It is a small way to keep conversations like this going without sponsors. Lucas: Yeah, we really appreciate it. Every contribution helps us keep the show focused on practical, concrete advice. Now, back to the shadow board idea — once you have built those relationships, the next move is to have a stay interview. Luna: A stay interview? I have heard of those as a retention tool for managers, but what does it look like from the employee side? Lucas: You schedule a meeting with your manager — call it a career development check-in — and you say something like, 'I really want to stay at this company long-term, and I think my next growth step is in product. Can we work together on a six-month transition plan?' That framing is powerful because it signals loyalty. You are not threatening to leave. You are asking for help to stay and grow. Luna: And you want to come with a concrete proposal, not just an ask, right? Lucas: Exactly. You say, 'I have already done X and Y. I am planning to do Z. Here is how I think we can backfill my current role. Can we identify a product team where I could do a three-month rotation?' The more specific you are, the easier it is for your manager to say yes. Most managers would rather help you transfer internally than lose you to a competitor. Luna: That makes sense. But what about the actual interview process? If you are internal, you probably have to go through a real interview loop. How do you prepare for the product sense question when you have never been a PM? Lucas: Product sense interviews are about how you think, not what you know. As an internal candidate, you have a massive advantage because you can reference actual company data. When they ask, 'How would you improve the checkout flow?' you do not have to guess. You can say, 'I looked at our funnel data last quarter and saw that 30 percent of users drop off at the payment method step. I think we should test offering a one-click option there.' That specificity beats any generic framework. Luna: So it is less about being clever and more about being informed. Lucas: Exactly. And that is why internal candidates can outperform external ones on product sense if they prepare. They already have the data. They just need to practice articulating their reasoning in a structured way. I recommend doing two or three mock interviews with a friend who is a PM — ask them to grill you on a feature you know well. Luna: One thing I have seen trip people up is the politics. When you transfer internally, you leave your old team. Sometimes your manager feels betrayed, or your colleagues resent that you are leaving them with more work. How do you navigate that? Lucas: That is the hardest part. The key is to make your transition as seamless as possible for your old team. Offer to document your processes. Train your replacement. Stay on for a month as a part-time resource if needed. When you show that you care about the team you are leaving, people do not feel abandoned. They feel like you are helping them level up too. Luna: And that also builds goodwill with the new team. They see you as someone who handles transitions professionally. Lucas: Right. And one more thing: do not badmouth your old role or your old manager during the interview. Even if you hated it. Internal interviews are relational. If you are negative about your current team, the product team will wonder if you will be negative about them too. Luna: So frame it as growth. 'I loved the marketing work, but I am ready for a new challenge where I can build products directly.' Lucas: Exactly. And finally, have a backup plan. Not every internal transfer works out. Sometimes the role gets frozen. Sometimes your manager blocks it. Sometimes you interview and you are just not ready. In that case, ask for feedback, set another six-month goal, and keep building your portfolio. The average successful internal transfer into product takes 12 to 18 months from the moment you start preparing. Luna: That is a realistic timeline. And if you get the role, what is the first thing you should do in your first 30 days? Lucas: Listen. Do not try to prove yourself right away. Your biggest asset as an internal hire is that you already know the context, but you do not know the product team's specific rituals. So spend the first month mapping stakeholder relationships, understanding the roadmap, and building trust with your engineers. If you do that well, you will be way ahead of any external hire. Luna: That is solid advice. I think a lot of people assume that because they are internal, they can hit the ground running immediately. But every team has its own culture. Lucas: Exactly. And that humility is what makes people want to work with you. So to sum up: start with a concrete project, build a shadow board, have a stay interview with a transition plan, prepare for the interview using your internal data, and then onboard with curiosity. That is the playbook. Luna: And if you want to dig deeper into any of those steps, we have earlier episodes on the stay interview and the shadow board. Links in the show notes. Lucas: Next week we will talk about how to use an internal transfer to move into a completely different industry without changing companies. That one surprised me. Luna: Looking forward to it.