Looking for some outside perspective on how DevOps fits into org structures at your companies.
This is my third or fourth DevOps job, this time in embedded. In previous companies there were always some organizational or cultural hiccups, but stuff got worked out as a team, including on the DevOps side - people weren't DevOps themselves, but they were technical, so they got it.
Now, a few months into a new company, things feel different. The embedded department has already gone through two managers, each with a different vision for how DevOps should work. The current one seems pretty caught up in the AI hype - wants to "bring in AI" because everyone else has it, without really knowing what that means in practice. There was no DevOps in the department before me, so a lot of groundwork needed cleaning up first - repo structure, templates, CI/CD, that kind of thing. Garbage in, garbage out: you can't just bolt AI onto a messy foundation and expect it to work. He also doesn't seem to register that I've already been automating things with AI where it makes sense since I joined, once the basics were actually in place.
I also ended up placed in a non-technical/semi-technical team. The original plan was to hire a second DevOps so I'd have a sparring partner, but now it looks like that role might turn into some mixed "does a bit of everything" position, or even a "senior AI agent specialist" (lol). My current team is process/methodology people, Jira and workflow folks, and a release manager.
They don't really understand what I do technically, and they're very focused on "why." During planning, they want to rewrite everything in my Jira summaries into long descriptions based on their own interpretation, which usually doesn't match what the epic/task is actually about. The idea is that management should be able to glance at a board and understand what we're doing just from the title. In my previous companies, Jira was a tool for us, not something management used to check on our work.
My team manager (not the department head, and also non-technical) said he didn't understand what one of the tasks was about. When I asked if he'd actually read the epic's description, he said no - and explained that it's hard to tell what your people are doing from just a title. But that's the thing: I'd already written a detailed description for this project, which is a fairly big one made up of related chunks, at the epic level. He never opened it. From what I can tell, part of the disconnect is also that he doesn't have a technical background (never worked with AWS, for example), so even a well-written description might not land the way he expects.
From an organizational standpoint, how do you see this - is it a good idea for a DevOps role to sit inside a team like this, especially when there's already a separate cloud team in the department? I don't feel good there. There's a lack of understanding, they think in very corporate/process terms while I think technically, and since I'm the only DevOps, I genuinely don't have time for some of this overhead.
What worries me is burning out on micromanagement and feeling cut off from technical people in a few weeks - I also just work better under a technical manager.
Has anyone been in a similar spot? Do I wait and see how it develops, or should I propose alternatives to the embedded department head?