You Need 10 Jobs to Find the One That Changes Everything

Most engineers treat job changes like bus stops. You wait until you’re uncomfortable, then you get on whatever’s moving.

That’s not a career growth strategy. That’s just leaving.

I’ve watched hundreds of engineers’ careers from the inside of Facebook’s hiring process. I’ve seen resumes from people who’ve had eight jobs in twelve years and can’t get a call back. I’ve seen resumes from people with the same eight jobs and can’t stop getting offers. The difference wasn’t the number of moves. It was whether each move had a reason.

The “10 Jobs” Math Nobody Talks About

The title sounds like I’m advocating for job hopping. I’m not. What I’m saying is that if you work for 35-40 years and average 3-4 years per company, you’ll have somewhere between 9 and 13 jobs. That’s just arithmetic.

The question isn’t whether you’ll move. You will. The question is whether you’re moving toward something or away from it.

Most engineers move away. They leave because their manager is bad, or they didn’t get the raise they expected, or they’re bored. All valid reasons. But “away from bad” and “toward great” are completely different trajectories, and they compound over 30 years in ways that are almost impossible to overstate.

The engineers I hired who were genuinely interesting to me could tell me exactly why they’d made each move. Not a rehearsed answer. They actually knew. “I needed distributed systems experience and my previous company didn’t have the scale for it.” “I wanted to work on a team that would eventually push me to a staff level, and I’d gone as far as I could there.” Every move had a thesis.

The engineers who struggled to explain their moves? They could tell me what they left. They couldn’t tell me what they were building toward.

What Facebook Taught Me About Career Architecture

I spent a long time at Facebook watching how intentional career moves played out. The pattern was consistent enough that it stopped surprising me.

Engineers who made it to Staff weren’t usually the most technically gifted people in the building. Some of them were. Most weren’t. What they had was a clear map of the capabilities they needed to develop and a history of making moves (internal and external) that filled specific gaps.

One thing Facebook did well was forcing engineers to articulate their growth areas during performance cycles. Not as a formality. As actual self-diagnosis. The engineers who took that seriously had a real advantage: they knew what they were missing. And when they knew what they were missing, they could go find it, either inside the company or outside it.

The engineers who stayed stuck, sometimes for years, were often the ones who couldn’t answer the question “what do you need to learn next?” They were excellent at their current job. They’d optimized for that. But they hadn’t thought about what the next job required.

Staff engineer promotion isn’t a reward for doing your current job well for long enough. It’s recognition that you’re already operating at the next level. The only way to start operating at the next level is to deliberately put yourself in situations that require it.

The Three Moves That Actually Matter

Not every job change advances a career. Some are lateral. Some are backslides. Based on what I’ve seen, there are three types of moves that actually build toward something.

Scope expansion. You’ve maxed out the technical complexity available to you in your current role. You need a larger system, a harder problem, or more ambiguity. This is the most common reason strong engineers move and the easiest to explain in interviews. “I’d learned what I could at that scale. I needed to work at ten times the traffic.” That’s a real reason. It lands.

Skill acquisition. You’re missing something specific and your current company can’t give it to you. This is the most intentional kind of move. You’ve diagnosed a gap, you’ve confirmed your company can’t close it, so you go somewhere that can. Engineers who make this move deliberately tend to accelerate faster than their peers because they’re not waiting for the right opportunity to materialize. They’re engineering it.

Positioning. Sometimes the move is about putting yourself in a room with the right people, the right problems, or the right visibility. This one is harder to explain in interviews without sounding mercenary, but it’s legitimate. Working at a company known for producing strong staff engineers is not the same as working at a company that happens to employ some strong engineers. The culture, the bar, the calibration of what “good” looks like - all of it rubs off.

Moves that don’t fit any of these categories aren’t necessarily wrong. But they should at least be honest. “I left for more money” is a complete answer. Constructing a post-hoc narrative about growth and opportunity when you just needed the raise isn’t doing you any favors. Interviewers who have hired a lot of people can hear the difference.

Why “Job Hopper” Is Usually a Misdiagnosis

When I saw short stints on a resume, my first question wasn’t “is this person flaky?” It was “is there a pattern here?”

One short stint is noise. Two short stints with a consistent story is a person who had bad luck or found their way to the right place faster than expected. Three short stints with no coherent thread is a signal worth paying attention to.

The engineers who got dismissed as job hoppers weren’t dismissed because they moved. They were dismissed because they couldn’t connect the moves into a coherent narrative. The moves looked reactive. Each one was an escape from something, not a step toward anything.

The fix isn’t to stay longer. The fix is to have a reason before you move, not after.

If you’re sitting somewhere right now thinking about leaving, ask yourself: what will this next role give me that I can’t get here? If you can answer that with something specific, you’re making an intentional career move. If the best you can do is “I just need a change,” you might be right that you need to leave. But you haven’t thought about where you’re going yet.

Do that first.

What Intentional Career Moves Actually Look Like

Engineers who build the careers they want tend to do a version of the same thing. They look two or three moves ahead. Not in a rigid way. More like a general direction with specific next steps.

“I want to be operating at a staff level in five years. To do that, I need experience leading cross-team projects. I’m not getting that here. So I’m looking for a role where that’s a core part of the job, not a stretch opportunity someone might let me try.”

That’s it. That’s the whole framework. Where do you want to be? What does that require? Are you getting it here? If not, where can you get it?

The engineers who end up with the careers they want aren’t necessarily smarter or luckier. They’re just clearer. They know what they’re optimizing for, and they make moves that reflect it.

You’re going to have 10 jobs. Make sure some of them are on purpose.

If you’re thinking about your next move and want to make sure your resume tells the story of where you’re going (not just where you’ve been), the SWE Resume System walks through exactly how to frame your experience for the roles you’re targeting.