While I agree with most of the sentiment, it should be noted most companies don’t ‘hyper-focus’ specialization like that.

There are always going to be interacting systems and having knowledge of other systems only helps your job performance.

When scoping for a client, there are many legal concerns at play. The scope, handed from the client, cannot be too specific technically. The concern is, if the systems change(due to firm changes, etc...) or one part of the implemented functionality is turned off (typically a free, or exit fee cost) certain technical verbiage would require contract arbitration and renegotiation.

Maintaince fees are different.

Most firms are paid significantly for the software produced, if they employees are not paid a proportionate amount, that’s the firms problem not the client.

Unreasonable internal scopes are different then client scopes. You just emphasized you worked in a client facing business, I thought it was an interesting topic to discuss.