For this months T-SQL Tuesday contribution I want to share why I think database job titles are in the eye of the beholder. At least to an extent.
Before I go any further, I want to thank Josephine Bush who hosts this months T-SQL Tuesday which got me thinking about things.
Josephine invites us all to talk about what all the database job titles actually mean. Which got also got me thinking about other things, so I added them to this post as well.
You can read the original invitation by clicking on this link for the T-SQL Tuesday 165 invitation or on the image below.
I fully expect that some people think that various duties are missing from some of the roles listed in the invitation. Which leads me to the next section.
Why job titles are in the eye of the beholder
I think having job titles along with a generic description are great. Because it gives employers a baseline to create their job descriptions and potential employees a good idea about job expectations.
However, I can guarantee that if you ask ten database managers to write a job specification for a database administrator the results will all be different. Due to a combination of business needs and their own interpretations of the role.
For example, some will expect shift support. Others will want knowledge of an additional programming language or CI/CD. Some will want a focus on the database engine whereas others will want good knowledge about the entire range SQL Server features.
In reality, we have our own biases about what these job roles should include as well. For a variety of reasons including our current skill sets. Plus, the fact that we are all different and we all think differently.
Which is why I fully expect some differences in this months T-SQL Tuesday contributions.
Of course, there is always going to be some common ground. For example, a database administrator should perform common tasks on databases.
Anyway, these are the main reasons why I believe that to an extent job titles are in the eye of the beholder. From both an employer and an employee perspective.
Current database job titles
Josephine does a fantastic job of breaking down some of the job titles in the invitation. I think it breaks down the common duties involved with these roles brilliantly.
In reality, the number of database job titles are increasing these days. Due to various reasons.
For instance, because enterprises are larger and are looking to work in a more DevOps related way there are other database job titles appearing to cater for them. Including ones for product owner and scrum master roles.
I know this for a fact because I was a product owner myself for a great team of individuals. Which led to various posts including how to make the most out of Microsoft Teams. In fact, that role is the main reason I became so deeply involved with Azure DevOps.
Plus, more senior titles and variations of the titles on Josephine’s list. Such as senior data integration architect. Which was a great job title that I once held, even though it was a bit of a struggle for those who had to read it on event badges.
I suspect more job titles will appear once Microsoft Fabric becomes GA (Generally Available). Due to the fact that I know there is already some speculation relating to this.
Anyway, I look forward to seeing what other titles appear thanks to this months invitation. Plus, the discussions surrounding them.
Now, I know at times people are in conflict due to issues relating to their current job titles. If this applies to you I highly recommend watching a session by Rob Farley (l/t) called ‘Your career in movies‘.
I hope my T-SQL Tuesday contribution this month makes for an interesting read.
Because I wanted to get my point across about database job titles being in the eye of the beholder, as well as providing my own thoughts about the list of job titles as well.
Of course, if you have any comments or queries relating to this post feel free to reach out to me.