Customers want features as fast and as cheap as possible. I derive joy from solid test suites that avoid me getting paged while on call and team processes that don't allow config changes on Friday so pages don't happen on the weekend.
Very few craftspeople derive their joy from the customer experience. An electrician isn't happy because their work allows me to watch TV. A carpenter isn't happy because a new set of stairs lets me get to the basement faster. They're happy because of their perception of the quality of their work. This goes away when the visible or fun parts are no longer "their work"
If all they see is code, they will get satisfaction from tidy code, not user happiness. One good thing about AI is it elevates product engineers because they more directly bridge the customer-product-code divide.
Quite a few don't, no.
Different people derive enjoyment in different things and some of the best engineers do not find satisfaction in "delivering better customer experience" but in working with, and improving, cool technology. Its up to management to find areas of the business where they can deploy these people in a way that dove-tails with business success.
Its also the case that only working on projects that "deliver customer value", and having to justify every single endeavor through that lense, is how you end up in a local maxima in your tech stack, get mired in technical debt, and then get lapped by your competitors who have the foresight to work on foundational technology that enables future velocity.
To be frank, its endlessly frustrating that your median Hacker News poster doesn't get this, and instead prefer to brow-beat people about how they're caring about the wrong things.