just went through a process audit with a major financial company. they were vetting our setup to connect and grab info from them for use in a product. The auditor flipped out when he learned that "developers" would potentially have access to our live production database (not theirs mind you - our own).
"This is unacceptable, developers can write code and could exfiltrate data".
"Umm... someone needs to be doing database updates, backups, restores, etc. Who do you suggest do that?" (bear in mind there's only 3 tech people on our team, and only 6 people total involved in the company's business).
"Typically a DBA or a manager would do that work. It would need to be someone who couldn't write any code to exfiltrate data".
We just sat on the call for another minute or so. I asked him to detail out the process by which someone who should be incapable of 'exfiltrating code' should also be the person who has access to manage the structure of a production database. We got nothing back except a checklist of stuff that we'd 'failed' with no remediation suggestions.
So... apparently some large companies do not consider DBAs as "developers" for certain checklists.
It really depends on your definition. I can script and make programs, and do some OOP in several languages, but I wouldn't call myself a "developer". I'm more of a devops engineer with a database emphasis if anything. I know some other DBA's who have developed really cool things like Orchestrator who others might call them a developer but I don't think that is most DBA's primary focus. Albeit, this varies pretty greatly between companies.
I get blasted for network engineering work non-stop. Only 6 month contract though, and usually in some technology that is 1) brand new, or 2) obscure as hell