Latest / The Internal Move Podcast with Fexingo: Lateral Roles, Internal Transfers, and Staying at Your Company / How an Internal Transfer Can Help You Escape a Toxic Team Culture
Transcript
- Lucas: You know that moment when you walk into the office — or log onto Slack — and your shoulders literally tense up? That feeling that the air in the room is just... off. Luna: Yeah, I think most people have felt that at some point. But the tricky part is figuring out whether it's you, your team, or the whole company. Lucas: Exactly. And for today's episode, I want to focus on that middle layer: your immediate team. Because sometimes the company as a whole is fine, but your micro-culture is toxic. And an internal transfer can be the cleanest way out. Luna: Let's ground this in a specific story. Who are we talking about? Lucas: Let's call her Priya. She's a mid-level product manager at a Fortune 500 tech company — think one of the big cloud infrastructure players. She'd been on the same team for three years, working closely with a sales-adjacent unit. On paper, the team was high-performing: they shipped fast, hit targets. But the culture was brutal. Luna: What made it toxic specifically? Lucas: Three things. First, decision paralysis disguised as 'rigor.' Every product decision went through five layers of review — not because the work was complex, but because no one trusted anyone else's judgment. Second, defensive communication. People preemptively blamed each other in emails. You'd get a 'just to cover my bases' message that was really a CYA missile. Third, chronic turnover. In three years, nine out of twelve people on her immediate team had left. But the company's overall attrition was normal. Luna: So the company wasn't the problem — the team was. That's exactly the scenario where an internal transfer makes sense. Lucas: Right. But here's the thing Priya had to figure out: how do you leave a toxic team without looking like the problem? Because the hiring manager on the other side is going to wonder, 'Why is this person leaving their team?' Luna: And if you bad-mouth your current team, you risk sounding difficult or disloyal. Lucas: Exactly. So Priya did something smart. She framed her move around what she wanted to learn, not what she wanted to escape. She told the new manager, 'I've spent three years in a fast-paced, revenue-driven environment. I've gotten really good at shipping under pressure. Now I want to go deeper — I want to work on long-term platform reliability, which is what your team does.' That's a pull, not a push. Luna: That's a great reframe. But she also needed to make sure the new team wasn't just a different flavor of toxic. How did she vet the culture? Lucas: She did something I'd recommend to anyone considering an internal transfer: she asked for a 'cultural interview.' Not an official term, but she essentially requested informal 15-minute chats with three potential teammates — no managers present. She asked them two questions: 'What's the most frustrating part of working here?' and 'When was the last time someone on this team made a mistake and it was handled well?' Luna: Those are really specific. What did she learn? Lucas: The first person said the most frustrating part is that decisions can take too long because they involve too many stakeholders. That sounded like a red flag — similar to her old team. But then the second person said, 'Actually, we're pretty good about making decisions quickly once we have the data. The frustration is getting the data from other departments.' That's a different kind of bottleneck. And the mistake question? Two of the three told her about a recent bug that got shipped, and how the team held a blameless post-mortem — no finger-pointing. That was the green light. Luna: So she wasn't just running away from something. She was running toward something she had evidence for. Lucas: Exactly. And that's the key distinction. A transfer motivated purely by escape is risky. You might land in another bad situation. But a transfer motivated by a specific pull — validated through these cultural interviews — has a much higher success rate. Luna: I want to push back a little though. Is it really possible to know a team's culture from a few 15-minute chats? People can put on a good face. Lucas: Fair point. You're not going to get the full picture. But you can look for patterns. If two out of three give you similar answers about frustration — especially if it's about something structural like decision velocity or communication norms — that's a signal. And you can also ask about tenure. Priya asked each person how long they'd been on the team. One was three years, another five, another two. That's a good sign. On her old team, the average tenure was 14 months. Luna: That's a huge red flag — low tenure across the board. Lucas: Yeah. So she had data. And that gave her the confidence to make the move. She transferred to the R&D team about eight months ago. And recently she told me it's like working at a different company. The same building, same badge, same CEO — but completely different day-to-day experience. Luna: So what's the one concrete thing you'd tell someone listening who's in a toxic team situation right now? Lucas: First, diagnose whether it's the team or the company. Look at turnover rates for your immediate team versus other teams in the same function. If your team's turnover is significantly higher, that's a team issue. Second, identify one or two teams that have a reputation for stability and collaboration — ask your HR business partner or a trusted mentor. And third, do the cultural interviews before you apply. Don't just apply blindly. Luna: And if they're worried about their current manager finding out they're looking? Lucas: That's real. In most companies, you can have confidential conversations with internal recruiters or HR. You don't have to tell your manager until you have an offer in hand. But once you do, frame it as a growth opportunity, not an escape. Say, 'I've learned so much on this team, and I'm ready for a new challenge in X area.' Your manager may still be upset, but it's harder to argue with that framing. Luna: It's almost like you're managing your brand inside the company. Lucas: Exactly. And that's a skill in itself. Priya actually told me that the move taught her more about navigating internal politics than any project ever did. She learned how to build trust with strangers quickly, how to ask for information without seeming nosy, and how to tell her story in a way that made people root for her. Luna: You know, this episode is a good example of why we keep this show ad-free. We're not trying to sell you anything — just give you practical, experience-based advice that might help you make a better career decision. If that's valuable to you, and you want to support the show staying independent, you can find us at buy me a coffee dot com slash fexingo. Lucas: Yeah, we really appreciate that. And honestly, it's because of listeners like you that we can keep the focus on the content, not the commercials. So thank you. Luna: Alright, back to the nuts and bolts. Lucas, you mentioned that Priya's move was eight months ago. Has she seen any downsides? Lucas: One downside she mentioned: she had to rebuild her reputation from scratch. On her old team, she was the person who could get a feature out in two weeks. On the new team, that's not what they value. They value thoroughness, documentation, and long-term thinking. So for the first few months, she felt like she was starting over. That's uncomfortable. Luna: So there's a reset cost. You lose your social capital and your track record. Lucas: Exactly. And she had to consciously resist the urge to 'show off' by shipping fast. She had to learn the new rhythm. But she said it was worth it, because now she's building a more sustainable reputation — one that aligns with her actual strengths, not just the pressures of her old team. Luna: That's a good point. Sometimes we develop skills that are actually survival mechanisms in a toxic environment — like moving fast to avoid blame. Those skills may not serve us in a healthier team. Lucas: That's a really sharp observation. And it's why the cultural interview is so important — because you want to understand what behaviors are valued in the new team. If they value collaboration over speed, you need to demonstrate that in the interview and then live it once you arrive. Luna: What about people who are in a toxic team but feel stuck because they think no other team will take them without a referral from their current manager? Lucas: That's a common fear. But internal transfers often don't require a reference from your current manager — especially if you go through an internal job board or a recruiter. The new manager will usually check with your current manager as a courtesy, but you can ask the recruiter to delay that until after you've had a chance to talk to the new team. And if you're worried your manager will bad-mouth you, you can preempt that by being transparent with the new manager about what you're looking for — again, framed positively. Luna: So the playbook is: diagnose team vs. company, identify target teams, do cultural interviews, frame your narrative as pull not push, and manage the reference process carefully. Lucas: That's the whole thing in five steps. And if I could add one more: don't wait until you're desperate. The best time to explore an internal move is when you still have some emotional energy left. Once you're burned out, you're more likely to make a reactive decision or leave the company entirely. Luna: What if there's no other team at the company that seems like a good fit? Lucas: Then the internal move might not be the right answer. If the culture is company-wide, you might need to leave. But I'd argue that in most large companies — especially ones with 10,000+ employees — there are pockets of great culture. You just have to find them. Priya's case is a good example: the company wasn't toxic, her 12-person team was. Luna: Alright, so for someone listening right now who's in Priya's shoes — shoulders tense every morning — what's the one step they should take today? Lucas: Open your company directory and look at teams that do work you find interesting. Then find two people on those teams who have been there more than two years. Send them a brief, polite message: 'I'm curious about your team's work. Would you have 15 minutes to chat this week?' That's it. No agenda, no pressure. Just curiosity. Luna: And if they say no? Lucas: Ask someone else. You're not proposing marriage — you're just gathering information. Most people are happy to talk about their work. And every conversation gives you more data about whether the grass is actually greener, or just a different shade of brown. Luna: That's a good note to end on. I think Priya's story shows that an internal transfer isn't just a job change — it's a culture change. And the research part is just as important as the move itself. Lucas: Absolutely. Next episode we'll talk about something related: how to leave a team gracefully — because you never know when you might need to work with those people again.