The best data engineers move for ownership and a manager who can describe the strategy. A 10% bump alone rarely does it.
Only 24% of developers told Stack Overflow they’re happy at work in 2025. When a senior data engineer actually leaves, the reason they give me is usually a version of the same thing: no real mandate. Authority to fix what keeps breaking, a domain that’s theirs, a manager who can name the direction.
What the missing mandate looks like day to day:
- They fix everything, with no authority to change the thing that keeps breaking.
- Their manager can’t say in two sentences what the data team is for.
- Every week is firefighting, with no room to build.
- “Ownership” on the org chart, overridden in every real decision.
I’ve watched strong engineers take a lateral move, sometimes a small pay cut, to get a real mandate: a domain they own end to end and the authority to fix root causes instead of patching symptoms.
So when a senior role sits open for three months, the instinct is to raise the band. Sometimes that’s right. More often the band is fine and the role is vague. “Come fix our mess” loses to “own this domain end to end” at the same pay, every time.
Before you raise the offer again, get specific about the mandate:
- What does this person own end to end that nobody will override?
- Who sets the strategy they execute against, and can they state it in two sentences?
- How much of the first 90 days is firefighting versus building?
Pay still has to be honest. Senior DEs know the market, and a lowball wastes everyone’s six weeks. Once the band is real, the mandate is what closes the candidate.
Can you describe the ownership your open data role gets in one sentence?