In 2023 I would have told you that job hopping stigma was basically dead. The post-pandemic market had normalized two-year tenures. LinkedIn profiles with 6 companies in 10 years looked like ambition, not instability. Hiring managers at growth-stage startups treated it as a positive signal.
That’s changed somewhat. The 2025 slowdown in tech hiring brought back scrutiny of short tenures, and I’ve heard from enough recruiters in the past year that it’s worth revisiting the actual dynamics rather than relying on conventional wisdom from either direction.
What the salary data shows
The core financial argument for strategic job moves holds up. Internal raise cycles at most companies run 3-5% annually. External offers for the same role at a competitor typically come in 15-30% higher. The LinkedIn Economic Graph’s 2024 Workplace Learning Report found that employees who had changed jobs in the previous two years showed notably higher compensation gains than those who hadn’t, controlling for seniority level.
The math favors moving every few years, in the right circumstances. But the circumstances matter more than the math suggests.
When short tenures hurt you
There are a few patterns that consistently draw negative responses from hiring managers I’ve talked to. These aren’t my opinions about what should matter; they’re what actually moves a hiring decision.
Leaving before shipping. If you were on a project for 11 months and left before it launched, you have a project on your resume that shows up as work-in-progress with no resolution. Do this twice and interviewers start wondering whether you avoid accountability. This is probably unfair in many cases. It still affects how resumes get read.
Lateral moves dressed as growth. Moving from a senior engineer role at Company A to a senior engineer role at Company B every 18 months, with no increase in scope or seniority, looks like optimization for pay without accumulation of skill. That read may be wrong. It’s still a common one.
Many jobs in a short time in a bad market. When the job market is tight (as it was through most of 2024 and 2025 in tech), multiple short stints can look like involuntary churn rather than strategic movement. Context helps, but context requires the interviewer to give you the benefit of the doubt, which isn’t guaranteed.
When it works in your favor
The situations where job hopping clearly helps are more specific than the general “move for salary” argument implies.
Early career skill stacking. In the first 6-8 years of a career, exposure breadth matters more than most people realize. Moving across industries or tech stacks accelerates the range of problems you’ve seen. A generalist who’s shipped things in 4 different environments is genuinely more valuable in certain roles than someone with 8 years at one company, regardless of what resume screeners might initially think.
Escaping a dead-end org. Some companies have frozen hiring above a certain level, or have cultural dynamics that actively prevent people from growing. Staying out of loyalty in that situation is expensive and somewhat irrational. The tenure argument cuts both ways: if staying another year doesn’t get you a promotion and leaving does, leaving is the rational move.
Industry-specific norms. Consulting, agency work, and contract roles have always operated on shorter engagements. A consultant with 12 employers in 15 years looks normal. The same resume in a regulated financial services context looks erratic. Know your industry’s norms before assuming the general rule applies to you.
How interviewers actually evaluate it
The way hiring managers respond to short tenures in an interview depends almost entirely on how you frame them. A pattern of moves that you can narrate as a coherent trajectory, each one increasing scope or compensation or skill range, reads very differently from the same moves framed apologetically or left to be interpreted from a list on a resume.
The Stack Overflow 2024 Developer Survey found that 62% of developers reported having changed employers at least once in the previous two years, which means interviewers in tech are seeing this constantly. The question isn’t whether you moved; it’s whether you can explain why in a way that sounds intentional rather than reactive.
The candidate I’ve seen handle this best said something like: “I was at Company A for two years, long enough to ship the main project I came in to do. Then I took the Company B role because they were doing the infrastructure work I couldn’t get exposure to where I was.” Short, specific, no defensiveness. It doesn’t work if the story isn’t true, but it works very well when it is.
What nobody tells you about the long game
One thing I genuinely don’t have good data on is how job hopping patterns affect the very senior levels, principal engineer or VP and above. My intuition is that at those levels, the projects you finished matter much more than the number of employers you had, and that a coherent narrative of increasing scope overrides almost everything else. But I’m speculating. I don’t have a good sample to work from there.
What I do think, with some confidence: the “job hopping is fine” norm that dominated 2021-2023 was partially a product of an unusual labor market. It hasn’t entirely reversed, but the calculus is more nuanced now than the blanket advice in either direction suggests.
If you’re heading into interviews where you’ll need to explain a busy resume, practicing the narrative out loud helps more than having the right answer in your head. Craqly’s mock interview tool is one way to do that, specifically for the “tell me about your career path” type questions where the coherence of your answer depends on how you deliver it, not just what you say.
Has job hopping helped or hurt you? The answer probably depends more on your specific field and timing than on any general principle.