The problem is most engineers don't understand the "job". They see the job as a strictly technical problem looking for the best technical solution. They don't

The problem is most engineers don't understand the "job". They see the job as a strictly technical problem looking for the best technical solution. They don't look up and see how that problem fits into the larger organization. They think things like "I can make a microservice that encodes PDFs 10x faster by using Rust" and give an estimate based on that, never thinking about how we're going to need to hire 2 more Rust devs to keep that running, and we could have delivered twice as quickly if I had used our default Python stack and now our "10x faster" doesn't matter because that feature is old news. Microservices are such an unfortunate concept because they attract the people least suited to use them: If your team can't handle a monolith, you shouldn't even be looking up what a microservice is.