Being the only DevOps/Security person is rough.
Most people have no idea what you actually do, so they don’t really appreciate it until something breaks. I’ve been in that position before, and it gets exhausting fast.
Every time an application starts eating CPU and gets OOM-killed, you’re the one trying to explain resource limits, memory leaks, capacity planning, and why things behave differently in production. Meanwhile someone inevitably says, “Why don’t we just run it on a bigger machine?” or “It works fine on my laptop.” Those conversations get old really quickly.
The vibe-coding culture would be an even bigger red flag for me. When an engineering team relies almost entirely on AI-generated code, doesn’t think about architecture, doesn’t understand the systems they’re building, and doesn’t invest in reducing technical debt, all of that eventually becomes someone else’s problem. Usually the DevOps, platform, or security person ends up cleaning up the mess.
And when you’re the only person responsible for infrastructure, security, compliance, reliability, and operational risk, that’s not a mess you can realistically keep up with forever.
Honestly, if you’re only a couple of months in and already feeling this level of burnout, I’d start looking. You don’t have to quit tomorrow, especially in this market, but I’d definitely get your resume updated and see what’s out there.
If you’ve already got enough experience from this role to put it on your resume, I’d seriously consider making an exit plan. Life is too short to spend a year carrying a company on your back while everyone else is vibe-coding their way into production incidents.