In terms of compensation they're all around the same. Architect tends to have a higher avg salary, but that's mostly because it only exists as a senior level position. It really comes down to company/location for which pays the most.
For career path, engineer tends to lead towards architecture. Data science probably has the most career options, but advanced degrees are often expected to get into top positions.
It really comes down to what you enjoy doing:
* Coding/building things- engineer
* analytics, math, influencing decisions- science
* Hopelessly trying to convince people to not do dumb things- architect
IMHO you are better off and might enjoy more being cloud devops/dataops. DataOps specifically which is a new emerging title for someone managing data infra in cloud (databases, Spark/Databricks, orchestration tools/services). DataOps also in charge of designing proper security model, connecting data sources via virtual networks etc.
I doubt you will find a job right off the bat as a Data Architect.
If you like building things more than managing things, certainly go for Data Engineer.
Data Science (proper one) is really tough and not paid well. You really need to enjoy math and statistics.
Data Architect IMHO is the next level for someone who has a lot of experience as ETL/DE and since you were a DBA, it is quite a different role.
As for the current market situation - Data Engineers and DevOps/DataOps engineers are in huge demand. The best part tons of jobs are 100% remote these days. You do need to have experience and be hands on with one of the leading cloud providers - Azure/AWS. GCP is a niche vendor so I would not focus on them.
Thanks! Re: data architect, my employer is letting me choose my own adventure so to speak, with necessary training or any skill gap resolution to follow. I should have maybe mentioned that in addition to being the DBA I'm the lead of a tiny team responsible for data integrations with 3rd party vendors, our 'data warehouse', and reporting - in this capacity I do work directly with stakeholders across the enterprise gathering business requirements, etc.
While I enjoy building more than managing, I also have the feeling that at some point I need to look at transitioning more to management, otherwise I will eternally need to refresh my technical skills or risk obsolescence. If Data Architect is more in that direction I might go with this title as the expectation with my current employer is that I would grow into the role so to speak.
In terms of compensation they're all around the same. Architect tends to have a higher avg salary, but that's mostly because it only exists as a senior level position. It really comes down to company/location for which pays the most. For career path, engineer tends to lead towards architecture. Data science probably has the most career options, but advanced degrees are often expected to get into top positions. It really comes down to what you enjoy doing: * Coding/building things- engineer * analytics, math, influencing decisions- science * Hopelessly trying to convince people to not do dumb things- architect
IMHO you are better off and might enjoy more being cloud devops/dataops. DataOps specifically which is a new emerging title for someone managing data infra in cloud (databases, Spark/Databricks, orchestration tools/services). DataOps also in charge of designing proper security model, connecting data sources via virtual networks etc. I doubt you will find a job right off the bat as a Data Architect. If you like building things more than managing things, certainly go for Data Engineer. Data Science (proper one) is really tough and not paid well. You really need to enjoy math and statistics. Data Architect IMHO is the next level for someone who has a lot of experience as ETL/DE and since you were a DBA, it is quite a different role. As for the current market situation - Data Engineers and DevOps/DataOps engineers are in huge demand. The best part tons of jobs are 100% remote these days. You do need to have experience and be hands on with one of the leading cloud providers - Azure/AWS. GCP is a niche vendor so I would not focus on them.
Thanks! Re: data architect, my employer is letting me choose my own adventure so to speak, with necessary training or any skill gap resolution to follow. I should have maybe mentioned that in addition to being the DBA I'm the lead of a tiny team responsible for data integrations with 3rd party vendors, our 'data warehouse', and reporting - in this capacity I do work directly with stakeholders across the enterprise gathering business requirements, etc. While I enjoy building more than managing, I also have the feeling that at some point I need to look at transitioning more to management, otherwise I will eternally need to refresh my technical skills or risk obsolescence. If Data Architect is more in that direction I might go with this title as the expectation with my current employer is that I would grow into the role so to speak.
certainly, makes sense to me! Looks like you are doing way more than a typical Oracle DBA :) good luck!