I noted another interesting point when reading about power and professions: The most prestigious positions within an ecosystem of professions are usually the ones that deal with other professionals rather than with the public : It is far more efficient (your collaborators know how to act “professionally”) and allows to maintain a self image of how the profession should work like (as less of the messy outside world seeps in.
Look at an issue tracker of an open source project where devs work for devs, and most issues seem to be about technology, solving programming problems, improving code; all nice tasks to work on (even for a lay-dev like me they make sense or would make sense if I would read the code more deeply). However, on many somewhat successful end user directed projects the issue tracker is full of, well end-user stuff like feature requests, issues that are not always reproducible, glitches due to systems being too new or too old… all thing that are not the “core” of development work and thus are probably not great to work on, similar to these “can you fix X, no time, not budget, maybe test with joe from the other team”-requests in UX.