Stop Letting Your Job Decide Whether You Feel Good About Yourself

Here’s an uncomfortable one:

A lot of technical people build their whole identity around being useful at work.

You know the platform.

You fix the issue.

You answer the question.

You are the person people call when things get weird.

That can feel great.

Until you don’t know something.

Then suddenly one awkward design call feels like a personal failure.

One bad manager ruins your entire week.

One rough performance review has you questioning your whole career.

One failed change makes you feel like you have been faking it the entire time.

That’s too much damn power for a job to have.

Network engineering gives you endless ways to measure yourself.

Certs.

Projects.

Incidents.

Promotions.

Tickets closed.

Technologies learned.

Platforms mastered.

And the industry is very good at making you feel like there is always one more thing you should know.

You finally understand BGP?

Cool.

Now learn EVPN.

Got comfortable with Cisco?

Better learn Juniper.

Know firewalls?

What about cloud?

Automation?

Python?

APIs?

SD-WAN?

There’s always another scoreboard.

Certification material can help. It gives structure and can absolutely make you better.

But it’s incomplete as a measure of your actual capability.

A cert can tell you whether you knew the expected answer.

Real work asks whether you can think through:

You can be good at this job and still get confused.

That’s normal in technical work.

It doesn’t need to become an identity crisis.

Your job should be one source of meaning, not the headquarters.

You should have other places where your life matters.

Family.

Friends.

Hobbies.

Fitness.

Creative work.

Travel.

Faith.

Community.

Whatever actually matters to you.

The goal is not “work-life balance” in the corporate-poster sense.

The goal is simpler:

Your entire emotional state should not depend on how useful you felt in a meeting today.

You’re on a troubleshooting bridge.

Someone asks:

“Why did this route disappear?”

You don’t know yet.

Now you have two choices.

Choice one:

Panic internally because you think a real network engineer should already know.

Start throwing out guesses.

Hide behind terms.

Say too much.

Hope nobody asks a follow-up.

Choice two:

Say:

“I don’t know yet. I want to confirm whether it was withdrawn, filtered, or lost because of next-hop reachability before I call it.”

That’s a better technical answer.

But it’s easier to give when your self-worth isn’t hanging off the answer.

That’s the part people skip.

Fake confidence isn’t often a knowledge problem.

Sometimes it’s an identity problem.

You’re trying so hard to look competent because being seen as competent feels like the whole game.

You get really good at work.

Now what?

More responsibility.

More tickets.

More escalations.

More people asking you questions.

Maybe more money.

Maybe not.

If technical competence is your main source of meaning, you can end up chasing increasingly difficult work just to keep feeling valuable.

That gets exhausting fast.

And here’s the ugly part:

Some workplaces love this.

The person who needs to feel indispensable is easy to overload.

They’ll keep taking the hard ticket.

Keep answering after hours.

Keep rescuing bad planning.

Keep proving themselves.

Keep accepting bullshit because being “the reliable one” became part of who they are.

That’s not leverage.

That’s dependency with good technical skills.

Ask yourself:

That last one matters.

When work gets under your skin, ask:

Those questions can clear out a ton of noise.

Pick something outside networking.

Then resist the urge to turn it into another damn optimization project.

You don’t need:

Just do something because you like it.

Build furniture.

Play a sport.

Make music.

Take photos.

Work on a car.

Read history.

Cook.

Spend more time with your family.

Go somewhere.

Create something.

Be bad at it for a while.

That can actually be healthy.

You spend enough of your professional life being measured.

Not everything needs a KPI.

Being technically competent matters.

You should understand the work.

You should communicate clearly.

You should build skills that travel.

But if technical competence becomes your main source of identity, the job gets way too much emotional leverage over you.

Then every bad manager matters more.

Every missed answer hurts more.

Every rough project follows you home.

Every career setback feels personal.

Build a life that still feels like yours even when work is messy.

That’s not quitting ambition.

That’s making sure your employer doesn’t accidentally become the owner of your entire emotional system.

This week, do one thing that has absolutely nothing to do with becoming a better network engineer.

And DON’T put it on LinkedIn.

Until next time.

— NEP