Or at least they do not have them long, as the good engineers will move on pretty soon. Some of them may even successfully found their own company!
I have seen this process several times now (fortunately always from the outside): Engineers start to get disrespected, and the most agile ones leave and find better jobs elsewhere. Then the good remaining ones raise more and more issues as there are not enough good engineers anymore and issues start to accumulate. Then these people get sacked or get strong suggestions to leave as they are "troublemakers". These also find better jobs elsewhere. Sometimes at a bit lower salary, but always with a lot more job-satisfaction. There may still be a few reasonable engineers left, for example some that are overpaid. (Typical gambit in the European banking industry: Overpay them, get them mortgages for houses, and suddenly they cannot easily leave because they would trouble to continue to pay their mortgages...) Then things get worse and worse, and eventually the average engineers figure out a way to leave as well. It is that or burn-out and engineers _are_ problem-solvers. And at that point, only those that are so bad that they really have no change of getting an acceptable job elsewhere remain. And eventually, things collapse.
Don't believe me? How do you think all the current data-breaches come to pass? Or a bit backwards in time: Why do you think Citibank took 6 weeks to analyze why you could switch account numbers in their online-banking and suddenly access accounts of other people? Or how did they miss this in the first place? Or why do many (most?) large IT projects still fail?
The only difference with large organizations or projects is that the process is a slower. Disrespecting engineers is a sure way to failure. Incidentally, in many classical hard engineering projects, you have engineers in charge, assisted by business people, not the other way round.
