Java is unproductive when you are a startup with one developer, but it works rather well at Google. Each change has to be manually code reviewed before submission anyway, so you aren't saving much time by using Python instead of Java. Agreeing on one language means that it's easy to switch teams; if you did Haskell and another team used OCaml, it would be hard to switch. If you both use Java, though, the barrier to moving is smaller and that means you can switch projects without losing productivity. And that's a good thing.
(Remember: Java at Google is not the same as Java at Bank of America. The toolchain is better, the libraries are better, the culture is better, and the codebase is better. There's really very little I hate about Google-style Java, and that's after hating Java with a passion for about 10 years.)
That's 1. A trivial number, if not a trivial system.
Google is developing Go precisely to improve engineer productivity, so this claim is rather suspect.