As an example, I could qualify for this role due to my experience with Groovy and thus Java by extension, but I wouldn't be interested in it because I wouldn't be satisfied in any position where I was restricted to pure Java.
Probably true of Scala/Groovy, but definitely not for JRuby or Clojure. Only ~32% of Clojure developers even know Java, according to the recent community survey.
writing Java, which I've never done and would probably be pretty bad at
Something tells me that you could still get a job doing it, it just might not be a job you particularly wanted :-)Seriously, though, clojure devs are a funny group. Clojure isn't anybody's first language at this point, and for the majority it's probably not even their third or fourth language, so they're already selecting for people who not only can, but choose to and enjoy learning new languages which are demonstrably deeper and have more details to learn than Java. Not only that, the language was specifically designed to be easy to learn.
What I've found trick with Java isn't the language, though - it's the ecosystem. Just trying to figure out which way is up in a Tomcat installation, for instance, is an absolute bear.
I take from that the guy writing it already realises the value of alternative JVM languages and is even a big fan of one, so why hold fast to pure Java? If you want to find good developers on the platform, maybe broaden your scope beyond the aspect of it you're having trouble with. I know plenty of people that use JVM languages and very few of them that wouldn't avoid using pure java if at all possible simultaneously.