If you're big enough to roll your own software ecosystem -- which means you have thousands of developers working on hundreds of closely coupled projects in a si

If you're big enough to roll your own software ecosystem -- which means you have thousands of developers working on hundreds of closely coupled projects in a single code base -- and you need repeatable builds, then Bazel makes sense. Bazel isn't designed to make things easy. It isn't even designed to make things fast (though it is easy to add that on due to repeatable builds). Bazel is designed to prevent you from shooting yourself in the foot; providing strong controls on project dependencies, both dependencies of your project as well as other projects' dependence on your project. That means in 99% of companies the answer is no. You're better off with CMake or something thing like that.