Latest / The Internal Move Podcast with Fexingo: Lateral Roles, Internal Transfers, and Staying at Your Company / How an Internal Transfer Can Accelerate Your Skill Development
Transcript
- Lucas: Let me walk you through a story I came across last week. A marketing manager at a midsize tech company—call her Priya—decided she wanted to move into product analytics. She applied for an internal role, got it, and here's the part that stopped me: she told her mentor she reached full productivity in five months. Luna: Five months? That's way faster than a typical external hire in analytics, which I've heard is more like a year. Lucas: Right. And Priya herself said if she'd left the company and taken a similar role elsewhere, she would have expected twelve to eighteen months to ramp up. So why was she so much faster internally? It's not because the job was easier—it was actually more complex than her marketing role. Luna: What was the difference? Was it just knowing the product? Lucas: That was part of it, but honestly the bigger thing was institutional knowledge. She already knew the company's data infrastructure—which tables to pull from, which reports were reliable, which departments hoarded their data. She knew the customer base from her marketing campaigns. And crucially, she knew who the informal decision-makers were—the people who could greenlight a project without waiting for a formal meeting. Luna: That's the stuff you can't put in a job description. New hires spend months just figuring out who to talk to. Lucas: Exactly. There's a study from the Corporate Executive Board—which is now part of Gartner—that looked at internal versus external hires. They found that internal employees reach full proficiency six to eight months faster than external hires in comparable roles. That's a massive time saving. Luna: That number sticks with me. Six to eight months of salary either wasted on ramp-up or invested in actual output. Lucas: And it's not just about speed. There's a second layer here that Priya's story highlighted. Because she was already employed, she could negotiate something really smart: a 90-day learning sprint with reduced deliverables. Luna: What does that mean exactly? Like a probation period with lower expectations? Lucas: More formal than that. She and her new manager agreed that for the first 90 days, she'd only be responsible for learning—shadowing, reading documentation, attending meetings, building a dashboard prototype. No urgent tickets, no fire drills. That's almost impossible to negotiate as an external hire because you're being hired to fill a gap, and they need you producing from day one. Luna: So internal transfers can actually shape their own onboarding experience. That's a huge advantage. Lucas: It is, but it's not automatic. You have to ask for it. Priya said she framed it as a win-win: 'I'll be fully productive in five months instead of eight if you give me this protected learning period.' And her manager bought it because she had a track record inside the company. Luna: Let me push back a little. This works in marketing to analytics, but what about highly technical fields? If I'm a software engineer moving from backend to infrastructure, is the learning curve still that much shorter internally? Lucas: Great question. I found a case at a major bank—one of the big ones—where a quant moved internally from risk management to algorithmic trading. That's a pretty dramatic shift. The tools were different, the models were different, the culture was different. Luna: Okay, so that's a big jump. How did it play out? Lucas: He reached full productivity in about nine months. The typical external hire for that kind of quant-trading role at the same bank took around eighteen months. So still a huge gap, even in a technically demanding field. The reason? Same as Priya: he already understood the bank's risk infrastructure, its data systems, and its internal compliance requirements. He didn't have to learn those from scratch. Luna: So the common thread is that internal transfers carry over 'organizational operating system' knowledge. The unwritten rules, the data shortcuts, the stakeholder map. Lucas: Exactly. And that's what makes internal moves so powerful for skill development. You're not starting from zero. You're starting from maybe sixty percent, and you only have to learn the forty percent that's genuinely new—the specific domain knowledge of the new role. Luna: That suggests there's a strategy here. Before you apply for an internal role, you should map out what you already know that will transfer. Lucas: Yes. I'd recommend making a two-column list. On the left, what you know about the company—systems, stakeholders, processes, culture. On the right, what you'd need to learn for the new role—technical skills, domain knowledge, new tools. Then you can see exactly where your internal advantage is. Luna: And you can use that list in the interview to make your case. 'I already know our data warehouse, I've worked with the product team before, I understand our customer segmentation model—so I'll ramp faster than any external candidate.' Lucas: That's a much stronger pitch than 'I'm a hard worker.' It's concrete and it's backed by data. And it's honest, which managers appreciate. Luna: One thing I'm wondering: does this skill development advantage carry over to cross-functional moves? Like moving from marketing to sales, or from HR to operations? Lucas: I think it's actually even stronger there, because the company-specific knowledge is often more valuable than the functional expertise. An operations person who moves into HR knows how the company's supply chain works—that's rare and useful when you're designing people policies for warehouse workers, for example. Luna: That's a good point. You're bringing a perspective that an external HR specialist wouldn't have. Lucas: Right. And you're learning a new function faster because you don't have to learn the company at the same time. You can focus entirely on the new discipline. Luna: So the real takeaway for someone listening today might be: don't underestimate how much you already know. Before you look externally, ask yourself if there's a role inside where your institutional knowledge would be a superpower. Lucas: Absolutely. And if you do make that move, negotiate for a learning sprint. It's one of the most undervalued perks of an internal transfer. Luna: Speaking of things that are undervalued—I want to take a quick second to talk about how this show stays on the air. We don't run ads, and that's intentional. A small group of listeners supports us monthly through buy me a coffee dot com slash fexingo. Lucas: Yeah, and that literally funds the research and production of episodes like this one. If you've gotten value from thinking through career moves with us, that's the whole engine right there. No pressure, just a genuine 'this is how it works.' Luna: Exactly. And we'll keep making them regardless, it just helps us know the content is hitting the mark. Okay, back to skill development—one last thought. Lucas: Sure, go ahead. Luna: I think there's a hidden risk here too. If you transfer too often internally, you might never develop deep expertise in any one function. There's a trade-off between breadth and depth. Lucas: That's a fair caution. The research on career trajectories shows that people who change roles every eighteen months—whether internal or external—tend to stay at a generalist level. But if you're deliberate, like Priya, and you use an internal move to build a T-shaped skill set—deep in one area, broad in a few others—that's a powerful combination. Luna: So the key is intentionality. Know what you're after before you make the move. Lucas: Exactly. And that's the best use of an internal transfer: not just a lateral shuffle, but a strategic step toward a specific skill set you want to develop. Luna: Priya's five-month ramp-up is a great benchmark. If you can cut your learning curve in half, that's a huge career accelerator. Lucas: It is. And it's available to almost anyone at a company big enough to have multiple departments. You just have to ask.