This hierarchy hasn't been relevant for at least 40 years. There are software developers in their 30s who have literally never seen a punchcard in person. Coder doesn't mean the same thing it used to mean.
It hasn't been relevant for at least 40 years for most people in this industry. My first job was in an organization with exactly these people, except that "operators" (of which I was one at when I started as a teenager about twenty years ago) had several component levels of hierarchy within it. Sysop, Print Op, and at the very bottom of the ladder, the Tape Op, whose job is to be the robot arm that our organization refused to pay for (no shit). Now, I'm still in contact with a couple of people that I used to work with, and one of whom still works there (though now he is a programmer upstairs). That hierarchy does still exist. We did, however, have a card-punching machine. You fed cards into the hopper, and a computer did the punching. So we didn't have a keypunch operator. But I still have a stack of cards somewhere in my house. I'll have to ask if they still use that equipment.
An analyst took business requirements and wrote specifications.
A programmer took those specifications and created flowcharts of the program logic.
A coder took the flowcharts and translated them into code on a coding form.
A keypunch operator punched the code onto cards, line by line, card by card.
So "coder" was a rather low status job, just one rung above being a typist.