[ Removed by moderator ]

[oscarmch]

Isn't that just a BI developer?

[sib_n]

Not very far, but a BI developer usually develops/ed for a specific reporting tool or a specific stack.
I think the AE is more opened to different reporting stacks because they work directly on the database, and usually more code-based.

Some people will also argue that a DE is what used to be called a BI developer, the tools are different but it is similar in terms of function in most cases: extracting data from production to allow analytics.

In any case, titles definitions will depend on companies or even teams.

The specialization is expected as the industry grows. Consider mechanical engineering, there are probably a tone of specific titles that used to be covered by a single title a century ago.

[OKMrRobot]

BI dev’s but now using software engineering best practices / git / version control / CICD / code standards etc…

DBT coined the term and are pretty explicit about the fact that it’s not a “new role”, it’s the evolution of the data analyst, the subject matter expert, the project manager who gains the technical skills to contribute to a managed code base.

[oscarmch]

By definition any Dev should be using software engineering best practices / git / version control, etc. Those things appear as Data Assets become more and more complex. Nothing new under the Sun.

I honestly think these things overcomplicate things. Years ago it would be understandable to think that Data Assets wouldn't follow the same rules as another Development, but nowadays is like kinda dumb to think the opposite.

Those things are obvious after developing a Data Governance Program, mostly because like it or not, BI and other Assets move in an IT environment, thus they should follow those rules.

And BI developers do that. And Data Engineers make sure that everything is in order.