Yeah, I've seen a lot of companies have postings for the two roles. Usually that means "we don't do devops at all, but we expect our ops staff to know how to code."

It's a fine job to take if you know that's what you're in for, and you're not planning on advocating for actual devops.

Typically that implies there's a team JUST writing inter-department tooling platforms: someone who's dedicated to making sure "devops" doesn't block everyone.

I would agree to some degree... but I would think that the "devops" engineer is simply the one to spearhead unifying dev and ops - the devops architect per say.