I've been a DBA for all but 3 years of my professional life. 2 years when I was starting and an interviewer literally schooled me about JOINs, and 1 year now since I'm masquerading as the self-proclaimed Chief Data Officer of our startup. So what does the change of title indicate? Firstly, it indicates that the old guard has to move on. That the state-of-the-art for data storage is a heterogenous mix of relational, non-relational, cloud-run, file-based systems. In short, the "DB" part of the DBA title is going to be a lot more fluid than a middle-aged DBA deep in their comfort zone would like to be.Secondly, it indicates that the "A" part of the DBA title is redundant. Cloud-based DB services can do all the admin stuff like replication, automated and encore backup, point-in-time recovery, clone, failover etc better, more efficiently, and reliably. Thirdly, for the last couple of years I've found myself working on a number of disparate data storage systems. Bigquery had to be used for a project. Datastudio for another. Had a reunion with my old friend MySQL. Google Cloud Dataflow was employed for automated ETL from a csv exported from MySQL to a Bigquery warehouse. A project needed cloud-based storage, Google sheets gave me everything I required and Appsheet gave me the interface. So this is more and more about Data and less and less about Database. The structure is there, but the boundaries are fuzzier. Until last year, since 2004, I was maintaining the database of our financial suite. Part of my job was to develop and maintain DB scripts for the apps and look after the DB. Hobbies: Audiobooks. Woodwork. Narration, Writing. Not in that particular order.