Your most senior Qlik developer is probably not developing.

Not because they lack motivation. Not because the backlog is empty. Because they have become the unofficial gatekeeper of everything that moves between environments. The person everyone asks before they click Publish.

This is the Senior Dev Tax. And most Qlik teams pay it every single week without realizing it.

What a typical week actually looks like

Think about what your senior developer actually did last week. Not what their job title says. What they actually spent their hours on.

Monday morning: someone pings on Teams. “Hey, is it safe to publish? I have changes in the Sales Dashboard.” The senior dev stops what they are doing. Checks with two other people. Waits for confirmation. Gives the green light. Easy forty minutes gone. Sometimes four hours if there is a conflict.

Tuesday: the Revenue report shows wrong numbers. Was it the data load? An expression change? A filter someone added last Friday? Nobody knows. The senior dev opens two versions of the app side by side and starts comparing objects manually. Sheet by sheet. Measure by measure. Two hours later the root cause surfaces: someone changed a Set Analysis expression in one master measure and it cascaded to 14 charts.

Wednesday: someone publishes to production. Except they pick the wrong stream. Users are calling. Everyone drops everything. The senior dev finds a backup QVF from last week on a shared drive, imports it, re-publishes. The backup is six days old. Six days of work — gone. “We will redo it,” the team says. Everyone nods. Nobody talks about it again.

Thursday: the senior dev finally sits down to do actual development work. The thing they were hired for. Data modeling, performance tuning, building something new. By 11 AM there are two more Slack messages about deployment coordination.

Friday: what day is the best for the release?

This is the tax

This is their week. Every week.

These developers were hired for their brains. For architecture decisions and complex data models. For the kind of work that moves the business forward. Instead they have become human version control systems. Living deployment logs. The people everyone asks before they click Publish.

The irony is hard to miss: the most capable person on the team spends the least amount of time on capability work.

Why nobody complains

The worst part is that most senior developers have accepted it. They do not complain. They do not escalate. They just absorb the coordination overhead because someone has to.

And because it is invisible work — no tickets, no story points, no sprint board column for “answered Teams messages about deployment safety” — nobody measures the cost.

But the cost is real. Every hour spent on deployment coordination is an hour not spent on the data model refactor that would cut reload times in half. Or the new dashboard the CFO has been waiting for since Q1. Or the migration to Qlik Cloud that keeps getting pushed to next quarter.

Sound familiar?

If you read this and recognized your own Tuesday, you are not alone. This is the default workflow for most Qlik teams with more than three or four developers. It is not a process failure. It is the absence of process — filled by the most experienced person on the team, simply because they know where everything is.

The Senior Dev Tax is what happens when a team grows but its tooling does not grow with it.

#DevelopersLifesMatter

This is the first post in the #DevelopersLifesMatter series — stories about the invisible work that Qlik developers do every day. Follow DatalabsUa for more.

Next in the series: Your Qlik Team Inherited IT Incentives. That Is the Whole Problem.