A coder, as the name literally implies, is essentially a human compiler. We long ago moved to using machines to do the coding, so it's not really a thing people do anymore (certainly not as a profession). The term has stuck around in modern times as a pretentious way to say programmer, but means the same thing in that context.

We do seem to have kept a lot of the idea that there are more mechanical parts of most programming jobs than we seem to acknowledge, though? Typically called junior or entry level work.

Do we? Any time I have come across a "junior" programmer, the intent was for them to do the same work, just with recognition that they aren't (yet) very good at it and need more proficient programmers to help guide them.

It is not uncommon for the entry levels to be described much more in terms of "does specifically defined tasks." As you move up, you are expected to work off more and more ambiguous requests.

The "specifically defined tasks" are ultimately the same thing, though, just much smaller in scope. When you're not very good, so to speak, it's best to not cut off more than you can chew. When you're new and still learning it is typical to start with baby steps that (hopefully) see you eventually work your way up to bigger and grander things.

Sorta, they are fully specified tasks that are largely in need of mechanically implementing them. Much like the work a service technician will do at your house. Designing the system and building all of the parts would be engineering tasks. Putting the parts together would not.

Now, agreed in startup land junior members are responsible for design more than people ack.