Latest / Job Hopping with Fexingo: Tenure, Loyalty, and the Modern Career Resume / How Job Hopping Reshapes Your Managerial Reputation
Transcript
- Lucas: So we've spent a lot of episodes talking about job hopping from the perspective of the individual contributor — how it affects your negotiation leverage, your vesting schedule, your health insurance. But there's a whole other dimension that shows up when you become the person other people report to. Luna: You mean when the job hopper becomes the manager? Lucas: Exactly. And the dynamic flips in some pretty unexpected ways. Because as an IC, a short tenure can signal adaptability, hunger, exposure to different environments. But as a manager, a short tenure can signal something else entirely — unreliability, lack of commitment, maybe even that you're using the team as a stepping stone. Luna: I've seen that firsthand. I had a manager at a previous company who left after about 14 months. And in that short time, she was great — smart, supportive — but when she left, it really rattled the team. We'd just gotten used to her style, she'd just started to understand our projects. And then she was gone. Lucas: That's exactly the kind of story I want to drill into. Let's use a concrete case. There's a SaaS company — let's call it CloudLogix, mid-size, about 400 employees — where a team lead joined to run a product engineering group. She had a strong track record as an IC at two different startups, each for about two years. So she was a classic job hopper, but in a good way. Luna: Right, that background probably helped her get the job in the first place. Lucas: It did. But after she took the role, she stayed 14 months. The team she inherited had about eight engineers, some of them quite tenured — three, four years at the company. And when she left, three of those engineers also left within the next six months. And in exit interviews, they explicitly said that her departure made them question the company's stability and their own growth path. Luna: So her decision to leave created a ripple effect that went beyond just her own career. Lucas: Exactly. And this is the thing: as an individual contributor, when you leave, you might burn a bridge with your boss, but your teammates can usually absorb it. As a manager, your departure sends a signal to your entire team — about whether the company is a place worth investing in, whether they should start looking too. Luna: There's also the mentorship piece. If you're a manager who's only been in the role for a year, you probably haven't had time to develop your direct reports meaningfully. You've been learning the org yourself. So your team might feel like they didn't get the career development they were promised. Lucas: And that affects your reputation in a way that's harder to measure than the number of years on a resume. A 2025 LinkedIn survey found that 62% of employees said that a manager who left within a year of their own start date negatively impacted their career growth. That's a huge number. It means that as a manager, your tenure isn't just your own data point — it becomes part of your team's narrative. Luna: So how do you counteract that if you're a job hopper moving into management? Do you have to change your behavior? Lucas: I think you have to be intentional in a few specific ways. First, if you know you tend to move every 18 to 24 months, be upfront about it during the interview process. Not in a way that sounds like a warning — but frame it as part of your career philosophy. Say something like, 'I tend to stay in roles until I feel I've delivered maximum impact, and then I look for the next challenge.' That sets expectations without scaring anyone. Luna: That's smart. It also lets the hiring manager decide for themselves whether they're okay with that risk. Lucas: Second, once you're in the role, invest in documentation and knowledge transfer as if you're planning to leave in six months. That sounds counterintuitive, but if you build systems that outlast you — runbooks, decision logs, mentoring notes — your team can survive a transition. And it actually builds trust, because your team sees you're not hoarding information. Luna: That's a good point. It's almost like leaving a legacy even if you leave early. Lucas: Right. And third, try to stretch your tenure to at least 18 months when you're leading a team. That's the minimum threshold where you've gone through a full performance cycle — you've done at least one round of reviews, you've set goals for a full fiscal year. Anything shorter, and you're really just passing through. Luna: It's interesting — the advice for ICs is often to move faster, but for managers, it's almost the opposite. You need to show stability. Lucas: And that's the paradox at the heart of this episode. The same behavior that makes you appealing as an individual contributor — breadth of experience, adaptability — can hurt you as a manager. Because as a manager, your team's trust is built on continuity. They need to believe you'll be there when they hit a rough patch or when they're up for promotion. Luna: I wonder if that's changing with the generational shift. Younger managers who are themselves job hoppers might be more understanding of a short tenure. Lucas: Maybe, but the data doesn't show it yet. The same LinkedIn survey broke it down by age, and even among Gen Z employees, a majority said a manager leaving within a year hurt their growth. So the expectation of managerial stability seems pretty universal. Luna: There's also the reference check problem. When you're a job-hopping manager, your former reports are often contacted in reference checks. And if they felt abandoned, that's going to come through. Lucas: Absolutely. I've talked to recruiters who told me that they specifically ask about a candidate's management tenure — not just how long they stayed, but how long they managed each direct report. If you managed someone for only six months before leaving, that's a red flag. Luna: So it's not just about the number of years at the company, but the depth of the relationships you built while you were there. Lucas: Exactly. And that's a harder sell on a resume. You can list 12 companies in 10 years and claim you learned a lot. But if you're applying for a management role, the question becomes: did you actually lead anyone, or did you just occupy the title? Luna: Speaking of the value of this kind of career insight — we keep these episodes free and ad-free on purpose. No sponsors, no interruptions. If you've found this discussion useful, and you want to support that approach, the simplest way is to visit buy me a coffee dot com slash fexingo. It's a small gesture that helps us keep going. Lucas: Yeah, honestly, it makes a difference. Just knowing people appreciate the no-ads format keeps us motivated to dig into these niche angles. So thank you to anyone who's contributed. Luna: Alright, back to the thread. So we've established that managerial job hopping carries different risks. What about the upside? Are there situations where a shorter tenure actually helps you as a manager? Lucas: There are a few. If you're brought in as a turnaround manager — to fix a broken team or process — then a short tenure can actually be a positive signal. It shows you came in, made an impact, and left when the job was done. That's a strong narrative. Luna: Like a hired gun. Lucas: Exactly. In tech, we see that with interim CTOs or engineering VPs who come in for a year, stabilize the org, then hand it off. That's a different context. But for a line manager — a team lead, a department head — the expectations are different. Luna: So the key is to match your tenure to the context. If you're in a high-churn industry like consulting or project-based work, short stints are normal. But if you're in a traditional corporate environment, you need to be more careful. Lucas: Right. And I think the best strategy is to be self-aware. If you know you're someone who gets bored after 18 months, either don't take a management role, or be very selective about where you take one. Look for companies that have a high tolerance for turnover, or where the role is explicitly project-based. Luna: Or consider a player-coach role — where you still have individual contributor responsibilities alongside management. That way, your value isn't entirely tied to your tenure. Lucas: That's a great point. A tech lead who codes 50% of the time and manages a small team can afford to move more frequently, because the team still gets value from their technical contributions. The risk is lower. Luna: I also think that as a manager, you can build trust by being transparent with your team about your own timeline. Not in a scary way, but just — 'I'm committed to being here for at least the next 18 months, and I'll give you plenty of notice if that changes.' That honesty can actually strengthen relationships. Lucas: Absolutely. The worst scenario is when a manager leaves abruptly without any warning. That's what erodes trust. If you signal your intentions early, the team can plan around it. Luna: So to sum up — job hopping as an IC is generally seen as a positive, but as a manager, it's more nuanced. You need to manage the perception of stability, invest in your team's growth even if you won't be there long, and be upfront about your career patterns. Lucas: Exactly. And the bottom line is: if you want to be a manager who job hops successfully, you have to think about your team's experience, not just your own. Because their references will shape your reputation for years to come. Luna: So the takeaway might be that your managerial reputation is built on the trust you leave behind, not the number of years you stay. Lucas: That's the line right there. And maybe the next time you're updating your resume, look at the 'management' section not as a list of roles, but as a list of teams you built or sustained. That's what hiring managers are really evaluating. Luna: Good perspective to end on. Thanks, Lucas. Lucas: Thanks, Luna. And thanks to everyone listening. We'll see you next time.