God this happens all the time. Software written by people that don't use the software themselves. It has happened to me so many times, I come across a piece of software with weird bugs or interactions that would be immediately fixed if the developer just spends 5 minutes using the software like an end user would. Dogfood all the things!
My experience is completely contrary: developers typically do care deeply about such things. The problem is rather that very commonly managers actively disallow these poor developers to apply their diligence to the software that they develop.
I really have a strong feeling that you want to participate in the ugly vendetta against software developers that has been going on for decades ("Replace all software developers"; current season: "Replace them with AI").
Don't do that. Rather fight the people who are really responsible (who are often (project) managers or Scrum masters).
Paranoia?
There are a lot of devs who don't really like what they develope so don't spend any time dogfooding it. Has nothing to do with devs who are blocked by management.
That said I have also encountered lazy engineers who are totally fine with implementing obviously broken software, those are a perfect match for the egotistical product manager.
... I saw last week that they just had their (latest) 25% headcount reduction, followed by their (latest) "executive offsite retreat" to pat each other on the back and figure out what they'll do between now and the next one.
This is like the argument "developers should use the software that they write" (dogfooding).
Let me give one example: the previous person who designed and developed the previous version of the software which I now work on really could use "his" program insanely well. The problem was rather that he was basically the only person who really did understand it sufficiently well to not to be triggered by problems other users had. Yes, a huge part of my job is over the years to turn this piece of software into something that is understandable by other people, too,. :-)
In my experience with large regulated systems, the engineers writing the software don't have the expertise to even know what the correct specifications should be in most cases, and especially in edge cases. Software engineers are not experts in customs and immigration legal requirements and would be relying on heavily on guidance from experts in those fields to determine the proper rules to apply.
In my experience with bugs like this, it is usually scenarios that all parties involved in the design did not consider... especially when implementation is rushed due to tight deadlines.
Other stakeholders typically don't apply such caution.
Business software is work processes that has been turned into code.
Whether such a person has such a permission in the system or whether the permission system of the software can actually model this is a work process that has been turned into code.