Agreed, after decades writing scala, go, rust and python and building high throughput analysis systems, I'm now not allowed to touch any of our infrastructure, or write any airflow jobs because our teams got partitioned into data engineering and data analysts, and I was given the analyst team.
30 min livebug fix and review for me on a job I specced out? Ticket to another team to review and schedule for next sprint and thus 2 weeks of metadata likely lost or malformed.
These setups look great (but full of invisible friction) when things are going well but shit the bed as soon as you come across the simplest of human errors that needs a solution.
This sounds more like a culture problem than a title problem though. Are you saying you can't even open PRs with a pipeline proposal? Your data engineering team is playing emperor and wants to protect their kingdom at all cost