The Invisible Work That Comes with Being the Senior Engineer

Moving up in engineering is usually sold as progress.

More money.

More influence.

More interesting work.

More control.

Sometimes that’s exactly what happens.

But seniority can come with another side that’s discussed much less:

more meetings, more interruptions, and a quiet expectation that unfinished work follows you home.

The senior engineer gets invited because the project might need technical judgment.

Then another meeting needs the same thing.

Then another.

Design calls.

Incident reviews.

Project updates.

Vendor meetings.

Change planning.

Escalations.

Calls where the engineer may barely speak but still needs to be present because someone might ask a question.

Eventually a strange thing happens.

The person expected to solve the technical work can spend a large part of the day talking about the technical work.

Then the actual work is still waiting.

This is where the invisible expectation starts.

The calendar was full from 9 to 4.

The configuration still needs reviewing.

The change plan still needs finishing.

The issue still needs troubleshooting.

The documentation still needs writing.

Nobody necessarily says:

“Take this home tonight.”

The expectation can be quieter than that.

The deadline didn’t move.

The meeting load didn’t shrink.

The work still belongs to you.

So the day stretches.

That’s not automatically a bad employer or senior role.

Some projects genuinely need senior engineers in the room.

Some incidents require extra hours.

Deadlines occasionally demand flexibility.

The problem is when exceptional effort quietly becomes the operating model.

There is a difference between being valuable and becoming a dependency.

If every technical decision needs one engineer present, that may feel flattering at first.

It can also mean:

The engineer becomes important enough to invite everywhere and too busy to do the work everyone invited them for.

That’s not leverage.

That’s a bottleneck with a job title.

A stronger version of seniority is not:

“Nothing moves unless this person is here.”

It’s:

“This person helps the team make better decisions, and the team can still operate when they are unavailable.”

That usually requires some intentional work.

Document recurring decisions.

Build templates.

Delegate work that doesn’t require senior judgment.

Push back on meetings that only need status.

Ask whether attendance is actually required.

Create systems that let other engineers handle more without waiting for one person.

And pay attention to whether a role consistently requires personal time just to keep up with normal workload.

That last one matters.

An occasional late night is part of plenty of technical careers.

A job designed around regular unpaid catch-up time is a different thing.

Career growth should not be measured only by title or salary.

Ask what happens to:

Sometimes a senior position is worth the trade.

Sometimes it’s not.

And sometimes the best career move is not another level up the same ladder.

It may be a different company, a more specialized role, an individual-contributor path with better boundaries, or simply an environment that doesn’t confuse seniority with permanent availability.

Look at a normal week.

Not the job description.

The actual week.

How much time goes to meetings?

How much goes to focused work?

How often does unfinished work spill past the normal day?

How often are you included because your judgment is needed versus because inviting you became habit?

If the role keeps requiring more hours just to meet normal expectations, treat that as information.

Being trusted is valuable.

Being needed everywhere isn’t automatically the same thing.

A good senior role should benefit from your judgment without requiring ownership of every hour you have.

Until next time.

— NEP