I&#x27;m very much a Clojure enthusiast and run the local Clojure user group.<p>But, as a non-engineer, I don&#x27;t think it really affects you enough to factor into the equation.<p><i>1) Will Clojure provide a competitive advantage in terms of cost savings and productivity?</i><p>Maybe. If they&#x27;re experienced at Clojure and are good engineers to begin with. But its not likely enough to base your decision on.<p>(I argue and hope that it <i>does</i> provide productivity advantages for a variety of reasons, but I wouldn&#x27;t be confident enough of this to base your decision on)<p><i>2) Will Clojure provide a hiring advantage because engineers are excited to work with it?</i><p>Maybe. Are there excited Clojure enthusiasts in your area who want to work on it? In my own experience, this may very well be true - I interact with a lot of enthusiastic programmers hoping for a job using Clojure in the user group. But, again, I&#x27;m not sure this is proven enough to base your decision on. Again, in my experience, the global Clojure community is exceptionally skilled and talented and have good sensibilities about what makes good, understandable, solid code and all Clojure developers I have spoken to are very happy writing Clojure. So if you can tap into these people, then that is definitely a positive for the company, but I&#x27;m not sure it will make or break the company.<p>Bottom-line is that Clojure is unlikely to be a top 3 contributing cause for success or failure, so, as a non-engineer who doesn&#x27;t get any personal satisfaction from the language, I don&#x27;t think it should be a major factor in your decision.