Safe Jobs Don't Build Careers

Most engineers who stagnate didn’t make a bad decision. They made a series of safe ones.

I watched this pattern repeat itself across twelve years at Facebook. Two engineers, same skills, same starting point. One took a stretch assignment nobody wanted. The other stayed on the team where they were comfortable and well-regarded. Three years later, one was a staff engineer. The other was still doing great work — and going nowhere.

The difference wasn’t talent. It wasn’t even effort. It was appetite for discomfort.

The Safety Trap

Here’s what safe looks like in practice: you’re good at your job, your manager likes you, you get solid performance reviews, and nothing particularly bad ever happens. You also don’t grow much, because growth requires failure, and you can’t fail at things you already know how to do.

Safe engineers optimize for the next review cycle. They pick projects with clear scope and predictable outcomes. They avoid the messy cross-team work where accountability is murky and credit is hard to claim. They stay in domains where they’re already credible.

I get it. That’s rational behavior inside a system that rewards consistency. The problem is that the skills you build in safe environments don’t compound the way risky ones do.

The engineers who made it to staff at Facebook weren’t the ones who executed reliably on well-scoped projects. They were the ones who’d gone into situations with unclear requirements, organizational friction, and real consequences for failure — and figured it out anyway. That’s the experience that can’t be taught and doesn’t show up in someone who’s spent five years on the same well-functioning team.

What Risk Actually Looks Like in an Engineering Career

When most people hear “take risks,” they think: leave your stable job, join a startup, bet on equity that may never pay out. That’s one version. But career risk-taking in engineering is more textured than that.

The risks that actually build careers tend to look like this:

Owning something you might fail at. Not a project where someone more senior is the real decision-maker. A project where you’re accountable for the outcome, the scope is ambiguous, and there’s no one to catch you if you miss. The first few times you do this, it’s uncomfortable. After a few cycles, it becomes the environment where you do your best work.

Moving before you’re ready. Most engineers wait until they feel fully prepared before taking on a bigger role or a harder problem. By that point, they’ve usually waited too long. The learning happens in the gap between what you know and what the job requires. Closing that gap is the job.

Leaving before it’s obvious you should. This one is hard. When you’re comfortable, leaving feels irrational. Your network is there, your reputation is built, your work is valued. But comfort is a lagging indicator. If you’re not learning at a rate that matches your ambitions, you’re already behind — you just can’t see it yet.

Taking on work that will make someone else look good. Cross-functional projects, coordination work, the glue that holds complex systems together — this is some of the highest-leverage work available, and engineers systematically undervalue it because the credit is diffuse. The engineers who did this work at Facebook often ended up with the most interesting careers, because they understood how the whole system fit together.

When It’s Time to Leave Your Job

This comes up constantly in conversations with engineers I coach. They know something feels off, but they can’t name what it is.

A few patterns I’ve learned to recognize:

You’ve stopped being scared. Fear is a useful signal early in a role — it means you’re in unfamiliar territory, which is where growth happens. When nothing at work makes you nervous anymore, that’s not confidence. It’s stagnation dressed up as confidence.

Your biggest wins are behind you. If the most impressive thing on your resume is from two years ago and nothing since has come close, your current environment is probably not giving you material to work with. That’s a problem when you eventually go looking.

You’re optimizing for optics over outcomes. If you’ve started picking projects based on what looks good rather than what’s hard, that’s a sign the environment is rewarding the wrong things — or that you’ve stopped caring about the right ones.

You have no answer to “what are you learning?” When someone asks you that and you have to think for a while before coming up with something, that’s worth sitting with.

None of these mean you should quit tomorrow. But they’re worth taking seriously, because the longer you stay in an environment that’s not building your skills, the harder the eventual transition becomes.

The Compounding Effect of Discomfort

The engineers who had the most interesting careers at Facebook shared a pattern: they had taken on something they were genuinely not sure they could handle at each major stage of their development. Not one of them described those periods as comfortable. Most of them described those periods as the most valuable of their careers.

Discomfort compounds. The first hard thing teaches you skills. The second hard thing teaches you that you can do hard things. By the third or fourth, you’ve stopped asking whether you can handle something new and started asking whether it’s interesting enough to be worth your time.

That shift in orientation — from “can I do this?” to “is this worth doing?” — is roughly what separates a good engineer from a very good one.

Practical Framing for the Next Decision

If you’re thinking about a move — whether that’s a new role internally, a different company, or a meaningful shift in what you’re working on — here’s the question I’d ask: Will this be on my resume in five years as one of the things I’m most proud of, or will it blend into the background?

Not every job needs to be transformative. But a pattern of background-blending roles has a ceiling, and the ceiling tends to arrive before most engineers expect it.

The other question worth asking: What would I take on if I weren’t afraid of failing at it? The gap between that answer and your current situation tells you something useful.

If you’re trying to figure out how to position a career move in interviews — how to talk about the risks you’ve taken and the stakes involved without it sounding like spin — the SWE Interview System covers that in detail, including how to frame project ownership and cross-functional work in behavioral interviews at every level.