One thing I have noticed in technical environments is that people often wait until they are completely burnt out before building career options.
They tolerate:
vague tickets
mandatory overtime
changing job duties
forced responsibilities
weak raises
micromanagement
promotions that add work but not pay
They keep hoping the company will eventually recognize their value.
Then one bad week pushes them over the edge.
Now they’re updating a résumé, studying for interviews, and judging job offers while exhausted and desperate to leave.
That’s too late to start building leverage.
Seek Leverage, Not Just Promotions
Promotions are fine when they serve your goals.
But a promotion is not automatically progress.
Sometimes it means:
more responsibility without more pay
doing the job before receiving the title
becoming the permanent owner of unwanted work
losing flexibility
accepting stress because management knows you have no alternatives
You do not have to climb the ladder in the exact way your employer designed it.
Your career does not need to revolve around becoming more useful to one company while becoming more dependent on it.
The better goal is leverage.
Leverage means you have enough skills, proof, money, and outside options to make decisions based on your needs.
The Mental Model
Build leverage in four areas:
Portable skills
Skills that still matter when the vendor, employer, or environment changes.
Proof
Real examples showing what you configured, investigated, improved, or explained.
Outside options
Recruiter conversations, interviews, professional relationships, and awareness of what other employers need.
Financial breathing room
Enough savings or outside income that every workplace demand does not feel like a threat.
You do not need all four to be perfect.
But the fewer you have, the more control one employer has over your decisions.
Burnout Removes Your Ability to Choose Well
When you’re burnt out, you stop asking:
“Does this next role fit my life?”
You start asking:
“How fast can I get out?”
That’s how engineers leave one bad environment and enter another one with:
a higher salary
worse hours
a longer commute
more on-call work
less flexibility
the same broken management habits
More money can be worth it.
A harder environment can be worth it.
Being onsite can be worth it.
But only when the tradeoff meets your needs.
Flexibility, Opportunity, and Pay
A useful way to judge a job is through three areas:
Flexibility
Opportunity
Pay
Aim for a role that satisfies at least two.
The best choice is not always the job with the highest salary.
Consider a network engineer earning $70,000 while supporting a small local school system.
After interviewing, they receive two offers.
Offer One
$100,000
mostly remote
onsite for meetings or when needed
network support role at a local university
Offer Two
$120,000
onsite Monday through Friday
network engineer at a large global bank
larger environment with more complex technology
Some people will automatically choose the bank.
It pays more.
The company is larger.
The title may sound stronger.
But the right answer depends on what the engineer needs.
Compare the Actual Tradeoffs
The university role pays $30,000 more than the current job.
It may also provide:
less commuting
fewer hours lost in traffic
lower transportation costs
more time at home
familiar educational-networking needs
enough space to build other skills or income
It may satisfy all three:
flexibility
opportunity
pay
The bank role pays $50,000 more.
It may provide:
exposure to global infrastructure
more complex routing and security
stronger enterprise experience
access to new platforms
better future earning potential
But it gives up flexibility.
That may still be the better choice for someone who wants a harder technical challenge and doesn’t mind being onsite.
The point isn’t that one offer is better.
The point is that the employer does not get to define what “better” means for you.
The Highest Salary Can Still Be the Worse Deal
Salary’s easy to compare because it’s a number.
Flexibility is harder to measure.
So is stress.
So is time.
A $20,000 salary increase can shrink quickly after accounting for:
fuel
parking
vehicle wear
meals
childcare
unpaid commuting time
reduced family time
less energy for studying or side income
That does not mean remote work is always better, it just means you should compare the whole job and not just the number at the top of the offer.
Portable Skills Create Better Choices
You gain leverage when your experience makes sense outside your current company.
Imagine you currently support Palo Alto firewalls.
You may know how to:
review traffic logs
validate security-policy matches
trace sessions
check routing
troubleshoot NAT
support production changes
explain failures to other teams
Those are not just Palo Alto skills.
They include:
traffic-path analysis
policy reasoning
change validation
fault isolation
technical communication
Fortinet may present them differently.
Cloud firewalls may use different labels.
Another employer may have different processes.
The decisions underneath the tools still transfer.
Certification Knowledge Helps, but It Is Not Enough
Cert material can teach:
protocol behavior
commands
definitions
design rules
vendor features
edge cases
That knowledge matters.
But it can leave engineers knowing the words without being able to explain their real contribution.
You may understand BGP attributes but freeze when asked:
“Tell me about a routing problem you handled.”
You may know firewall rule order but struggle to explain:
“How did you prove which rule matched?”
You may know IPsec phases but not know how to describe where a real tunnel failed.
Portable skill means connecting technical knowledge to:
the problem
the evidence
your role
your decision
the result
That’s what creates options.
Stop Describing Your Work Through Internal Labels
Weak:
“I support our branch template.”
Better:
“I validate VLANs, routing, VPN connectivity, firewall policy, monitoring, testing, and rollback readiness during branch deployments.”
Weak:
“I manage access requests.”
Better:
“I clarify traffic requirements, review routing and NAT dependencies, validate policy scope, coordinate testing, and document results.”
Weak:
“I worked a major outage.”
Better:
“I measured impact, traced the traffic path, gathered logs, identified the likely failure boundary, and provided clear updates during a production incident.”
Your internal process may not travel but the judgment underneath it does.
Build Proof Before You Need It
Do NOT wait until an interview to remember what you have done for the last three years.
Keep a private record.
Don’t copy confidential information.
For every useful project, ticket, or incident, record:
the problem
what was expected
what you checked
what you personally owned
what you only supported
which evidence mattered
what changed
which skill transfers
Example:
“After a firewall migration, a branch could reach the internet but not a hosted application. I confirmed local routing, reviewed the matching security policy, checked NAT behavior, and helped identify a missing return route in the hosted environment.”
Portable skills:
end-to-end traffic analysis
firewall troubleshooting
return-path reasoning
cross-team communication
evidence-based escalation
That’s immensely more useful than saying:
“Supported a firewall migration.”
Do Not Confuse Dependability With Surrender
You should still perform well.
You should still learn.
You should still help the team.
You should still pursue promotions when they make sense.
Leverage isn’t an excuse to become lazy, difficult, or unreliable so if that’s the advice you’re looking for, look elsewhere.
In fact, dependable employees with portable skills often have the most leverage.
They are valuable where they are.
They are also valuable somewhere else.
That changes the conversation.
An employer is more likely to consider:
a raise
a promotion
schedule flexibility
better duties
stronger development opportunities
when losing you is a real possibility.
Not because you issued a threat but because you built options.
What to Look for in Daily Work
In configs
Ask:
What behavior does this create?
Which part is vendor-specific?
Which part would matter on another platform?
In tickets
Ask:
What details were missing?
What did I clarify?
Which technical decision did I make?
In incidents
Ask:
What evidence narrowed the problem?
Which assumption wasted time?
What would I check first next time?
In meetings
Ask:
What result is actually needed?
Which risk matters?
Who owns validation?
What could I explain more clearly?
In change windows
Ask:
What had to be tested?
What proved success?
Where did rollback begin?
Which part did I personally own?
That’s how daily work becomes career leverage.
Questions to Ask Yourself
Which skills would still matter at another employer?
Could I explain my value without internal company language?
What problems can I solve?
What have I only observed?
What have I supported?
What have I owned?
Which job duties am I accepting only because I feel trapped?
Would a promotion improve my pay, flexibility, or opportunity?
Which two of those three matter most right now?
Would I still accept this role if the title sounded less impressive?
What would make leaving feel like a decision instead of an emergency?
These questions help you judge work based on your life.
Not somebody else’s career ladder.
Build Options Quietly
You don’t need to announce that you are preparing to leave, in fact please don’t.
You can quietly:
update your résumé
document project examples
practice technical explanations
respond to recruiters
interview frequently
reconnect with former coworkers
learn an adjacent platform
build savings
create another income stream
compare job offers using flexibility, opportunity, and pay
You can stay.
You can leave.
You can use an outside offer to better understand your market value.
The point is that you have choices.
The Point
Do not wait until the job has completely cooked you.
Build leverage before burnout makes every decision urgent.
Learn portable skills.
Keep proof.
Know what the market needs.
Build financial breathing room where possible.
Judge new roles through:
flexibility
opportunity
pay
You don’t need to chase every promotion.
You don’t need to take the highest offer.
You don’t need to grow only in the way your employer prefers.
You just need enough leverage to choose the work that meets your needs.
Your employer can own the equipment, licenses, and internal processes.
It should never own your future.
- NEP