I wrote my own competitor at
http://gihub.com/paulhoule/pidove/
which looks lispy because it uses static imports for everything. I started on a fluent syntax version but wound up working on another project. The odd thing is that I wound up studying the streams API in enough detail that I got over many of the complaints I had about it. If I was going to put more work into pidove it would be developing it to make the most of the Collections API so if you, say, map a list, it returns a list that lets you get(7) to only map that item.
They are great for libraries with well defined and slowly evolving interfaces. But unless you're doing open-source, you will rarely work on those.
Write tests. Not too many. Mostly integration.
Perhaps this turns into another round of clarifying what the discussion participants deem "unit" vs "integration".
Edit: my experience is mostly between seed - series B startups. If you're Google, then of course you're going to have a ton of internal libraries. But I'd put it in the same category as open source.
So far I'm still seeing complex class hierarchies with deep inheritance, dependency injection and unit tests produced by ex-Java developers for something that can be solved with a couple of simple methods in Python.
I noticed that complexity makes Java folks proud. Conversely, simplicity makes Python folks proud.
Seeing Java on a resume is not yet a reason not to hire for me. But it's a signal that indicates greater risks.