I can think of one real-world use-case, though I have never used this product. It's pretty common in larger companies to have legacy products with a couple of

I can think of one real-world use-case, though I have never used this product. It's pretty common in larger companies to have legacy products with a couple of very senior (usually overworked) people and a larger number of junior people. The juniors very often have little experience with the language, much less the frameworks, of these legacy systems. So PR's from junior devs are often very frustrating for senior devs (wrong language conventions, not how AWS is done, paradigm misunderstandings, inaccurate comments) -- and the perverse incentives resulting from that are pretty obvious. Bad code ships. If passing "code review as a service" were a requirement before the juniors could put up changes for seniors to review, in my experience that would be money well spent.