Judging by the list of things they've tried to fix to assuage player complaints, I feel it's safe to say, they do listen to feedback.
Time and effort are finite resources on a project. A project needs a way to streamline their processes in order to achieve all their features. The game has alot more to deal with, than just jobs. It doesn't help matters when they're feedback is thrown around willy nilly from just anyone, without proper requirements, needing to spend time filtering out the noise and find the root cause of an issue.
Tank and Healer anxiety is a very real thing. So much so, that many players who might gravitate toward those roles can avoid playing them for fear of being called out and labeled. The homogenisation and simplification of those jobs serves more than just balancing. It also ensures that more players will play those roles, reducing queue times in the Duty Finder for everyone else. If the jobs were more complicated, a DPS' queue time might be even higher than it is now. It's one of those consequences that the community brings on itself.
They do listen to feedback and they do try and keep the playerbase happy. But the playerbase is never happy. Fixing a problem the one group complained about, makes another group angry who saw no problem with it before. SE tried to make jobs unique, which caused job imbalances. People complained that they were being excluded, so they balanced the jobs while streamlining the process. Now another group complains that everything is too streamlined.
If the FFXIV community wants something specific, all the groups need to reach a consensus. And that's not going to be some magical problem fix, it's going to be finding a middle ground that SE can implement and that the playerbase as a whole can agree that this is the best we're going to get and accept it.
There's a clip way back when of Jeff Kaplan discussing Overwatch meta. When one meta comp that made the community angry was fixed by the team, only for another meta comp to immediately take its place, and the community started complaining about the new one. He just exclaims, exasperated, "What the hell do you people want?"
Maybe it's time we decided what we want and then structure it in such a way that SE can turn it into a well defined feature requirement that they can implement? Instead of one group shouting over another into the aether and the one that screams loudest gets to have their moment of glory?