Since we’re generally sitting on top of a giant pile of semi-understood abstraction that doesn’t have a real mathematical model and is often defined by matching legacy behavior (aka precedent), “Software Lawyer” could be a better name.
We are "Framework and API plumbers" by and large, taking existing packages and just hooking them into each other.
We belong with the lawyers, who are working in an entirely human constructed framework but have somehow fucked it up so bad that it has loopholes and undefined/unexpected behavior.
And there's no possible way not to have some leaky abstractions with this in front of us.
But it is less funny if we go with code-plumber, the goal here is to justify trying to steal the protected job title.