Why Your Best Engineer Avoids The Data Layer

Watch who picks up the data tickets at a 40-person company. It tells you who owns data.

It’s usually whoever joined last, or the person who once said they liked SQL.

From the senior’s side, the math is simple. Data work has no owner or roadmap. Once they touch it, they inherit every bug and a stream of interrupts. The career path is unclear too, because nobody above them owns data either.

So they avoid it, politely. And your least experienced engineer ends up making architecture decisions nobody reviews.

What changes it is mostly boring. Name an owner, protect their planning time and review data changes like product code. And make the work visible upward: a data fix that saved finance two days a month belongs in the same update as a feature launch.

You can do all of it with the team you have, once someone says out loud that data work counts as real engineering here.

Who ends up with the data tickets on your team, and did they choose it? More on who owns what: https://thomasnys.com/data-team-ownership/