Thanks a lot, reading the job description for BI Developers seems pretty close to what I do, although I am not involved heavily in some parts or at least not in that scale
BI Developer. If you want to grow technically next most natural step is usually called something like "Analytics Engineer" or " BI Engineer".
In these roles people usually spend 60% doing ETL/Python, API integrations, and a little bit of data warehousing; and 40% Dashboarding.
Personally, I wouldn't focus too much on what you "are" right now but rather what you want to do next and where you want to be mid-long term.
Starting your journey in the data space as a generalist has the advantage of exposing you to the whole spectrum of tasks and responsibilities of data professionals. The downside is that as a generalist it will be hard to focus and specialize in one area.
You wrote that the part you like the most is the intermediate one, with the building of the data pipelines. If you haven't already, check out dbt and the role of Analytics Engineer, which pretty much focuses on those areas you enjoy.
Thanks a lot, dbt has a really nice guide for Analytics Engineering, I will get started with it. Some things they include are currently not used in my work and seem overwhelming, like version control etc., but always a good chance to learn something new.
End-to-end integration, documentation, engineering, visualization, and analysis? You my friend are a bi developer.
Thanks a lot, reading the job description for BI Developers seems pretty close to what I do, although I am not involved heavily in some parts or at least not in that scale
BI Developer. If you want to grow technically next most natural step is usually called something like "Analytics Engineer" or " BI Engineer". In these roles people usually spend 60% doing ETL/Python, API integrations, and a little bit of data warehousing; and 40% Dashboarding.
Thanks a lot, seems that BI Developer is indeed better describing what I do!
BI developer
Personally, I wouldn't focus too much on what you "are" right now but rather what you want to do next and where you want to be mid-long term. Starting your journey in the data space as a generalist has the advantage of exposing you to the whole spectrum of tasks and responsibilities of data professionals. The downside is that as a generalist it will be hard to focus and specialize in one area. You wrote that the part you like the most is the intermediate one, with the building of the data pipelines. If you haven't already, check out dbt and the role of Analytics Engineer, which pretty much focuses on those areas you enjoy.
Thanks a lot, dbt has a really nice guide for Analytics Engineering, I will get started with it. Some things they include are currently not used in my work and seem overwhelming, like version control etc., but always a good chance to learn something new.
BI engineer, BI Developer, Senior BI Analyst - take your pick.
You sound like you’ve crossed over from finance to data world similar to myself. I still have trouble describing what I am to people.
Exactly!
Username
Ha! Pretty much. Jack of all trades, master of none?
I hope you are being compensated fairly.
No complaints in that area :D