I have advocated to at least try bazel (or even buck), but the higher-ranking devs all say that it's too much "organizational knowledge risk", i.e. if I force something unfamiliar onto the team and they only shakily know how to work with it with my help and then I leave, they're screwed. Therefore, it usually boils down to trusty old crusty tools.
They're not wrong though; if you want to introduce a new tool - especially one as large and complicated as Bazel - you need to also take ownership of training and hiring not just yourself (assuming you're not already a Bazel expert) but all your current and future colleagues yourself. The management has to make a cost / benefit analysis and it's not in Bazel's favor.
Bazel is a tool by and for Google scale companies, which 99% of tech companies aren't. Make and co are good enough for most use cases.
Crabs in a bucket.