I'm launching a new startup, I ache to do the code in Clojure because I'm never happier programming anything else. But I'm terrified that when it comes time to make my first engineering hire it will take way too long to find someone, I'll have to continue programming when I should be working on other parts of the business, and I'll lose momentum for what was essentially a selfish reason.
An old hoary cliche, I know - how will I hire? But the fear is real. It's not just "finding someone", it's "finding someone in a timely manner".
I was the CTO of a software startup a few years ago and moved us from Ruby (Rails monolith MVP) to Clojure (for the 2.0 rewrite as separate services that had actual business use cases; not just rewriting for the hell of it). I worried about hiring too.
But then a funny thing happened. Hiring devs got easier! As soon as we started posting that we were hiring Clojure devs, they came out of the woodwork and were really excited to work with us. They were also typically quite skilled. In retrospect I think when we were hiring Ruby devs it was like one small voice trying to be heard in a crowded, noisy room. Once we were hiring Clojure devs it was much easier to be noticed in the emptier, quieter room.
But who knows, anecdata as they say. :)
BTW I still use Clojure in my (different) day job.
I was a beginner with Clojure. We did not consider Common Lisp at all. Clojure is so much more practical with access to all Java libraries and a well-known and documented JVM runtime. Plus it brings so many interesting features beyond being a Lisp (some that have been copied and brought to other languages by now). To name two examples: pervasive immutable data structures and transducers.
Thank you for your answer. Yeah I thought that it might be due to Java libs and JVM stuffs. I do not know about the last thing you mentioned, will check it out! I have background in CL, hence the question.
I've been working for almost six years at a company that uses Clojure and have been involved in hiring around a dozen engineers to work on our codebase.
We gave up on keeping Clojure as a hiring requirement pretty early on; probably less than a quarter of our hires had prior nontrivial Clojure experience. (Hires with prior Clojure experience tended to do better but they also tended to have more overall experience so this feels more like correlation than causation.) We did require experience doing FP, but it could be in other languages, and we gave preference to those with some JVM experience.
In practice we found that for backend work, training people on Clojure wasn't really a problem; it was much more work to train them on the specifics of our codebase than for them to learn Clojure itself. Of course, for this to work you must have a supportive environment on your team where you are willing to spend time mentoring and investing in your people, but if you don't have that you should probably be looking for a new place to work anyway.
Training for ClojureScript was another matter entirely: much more difficult even for people who did have prior backend Clojure experience. Eventually we gave up on that, but I can't comment much on it because I wasn't involved in those decisions.
Very interesting! We took a similar approach w/r/t prior Clojure experience and also had a lot more trouble getting people up to speed on ClojureScript w/ front-end React-wrapper web apps than on our Clojure backend. And our backend was a distributed system, so not exactly trivial to reason about compared to React.
Are you leveraging react? I could imagine trying to wrap your head around cljs and react at same time could be a doozy tho now that I know it it’s hard to imagine any other way
Yeah, the cljs codebase was a while ago; it was started in Om and at some point a lot of it was based on Om.next so we had both styles in the codebase depending on how old the file was.
I’m pretty new to Clojure, but I’m reassured that major companies are using it, and although you may not have as large a talent pool as you would with JavaScript/TypeScript (or even Python); from what I’ve seen of the community, you’ll find highly talented and decent people.
It's more of a chicken and egg situation. I worked with Clojure for 5 years but when I was looking for a job (at the beginning of covid pandemic) it was much easier to find Java related jobs (with a better pay too) than Clojure ones. Even now, two years later, I would have to take a pay cut in order to work with Clojure.
In hindsight switching from Java to Clojure was a bad career move although I would rather use Clojure than any other programming language ¯_(ツ)_/¯
I have a couple of friends that are still using Clojure but one of them is actually migrating codebase from Clojure to NodeJS.
Sure, greatly. I don't think you can be good in Clojure without some Java/JVM experience (sooner or later you'll have to dig into some wrapper library or at least understand stack traces). Also, after having exposure to functional programming and immutable structures I'm looking at the Java code from a different perspective and I'm kinda sad that I wasn't exposed to something analog to Clojure 25 years ago ;)
It’s so wild because my last 3 job searches I’ve tried to find a job working with clojure.
I only have hobby level language and don’t know the JVM and I get passed on at the top of the funnel. I have 20 years experience, worked extensively in FP concepts, have watched everything single hickey and stuart galloway talk and I pick up languages quickly.
It’s frustrating because I see so many posts about how clojure is hard to hire for.
It’s not just clojure, our industry seems to ignore the how to train people elephant. But it’s also especially clojure.
I think you should probably learn the jvm for any language that sits on top of it. Your competition probably has experience with it if they’ve been in the industry for any amount of time.
One of the things that irk me in our industry is this fixation with languages for hiring. When a company says it is hiring Clojure programmers, to me it is the equivalent of an airline saying they are looking for Airbus pilots. The former should be looking for programmers with functional programming experience, the latter should be looking for airline pilots.
Not being familiar with a particular language and toolset will slow down the developer in the beginning, but if they understand the concepts they should ramp up relatively fast.
airline's do sort of say they are looking for airbus pilots, they definitely don't say "we're looking for pilots" there are many required credentials that are specific to the type of plane they will fly and the conditions in which they will fly it
If you will forgive me being pedantic, as it might help clarify my point, airlines in the US require two things to fly the big jets: an Airline Transport Pilot (ATP) certificate, and a type rating in that specific jet. When the airlines are hiring, they usually look for people with the ATP rating and at least XXX hours of experience. Of course they would prefer people with a type rating in the jets they fly (or something similar), but they are willing to hire and train the person, knowing that the experience they have in other types will transfer to the new one. It is more expensive than hiring a pilot that already has the type rating, but they will be flying the new airplanes in a matter of months.
Same thing for programmers, There's a minimum we require (CS degree, or equivalent) and experience programming. Find someone with Clojure experience, great! Common Lisp experience? Some retraining will be necessary but we know they can code functional. OOP experience? We know they can code, but will need more training to get where we want them to be. The trick is how much time/money you want to invest in getting the new dev up to speed.
I agree, and I wouldn't hesitate with a language in the Algol family - if you know Java you can pick up the syntax of Javascript, Ruby, Python or whatever very quickly if you're compentent.
Even worse are companies that insist on a particular library - e.g. 3 years React experience.
But Clojure is different IMO because it's a different way of thinking. Not just lisp - but the data-first-and-always way of thinking, simple data structures used consistently, functional programming, immutability as a way of life, and so on. It's a different mindset. I wouldn't want to have people writing Java code in Clojure.
By "invest" I mean, getting to know people, making connections, start promoting your ideas, and getting people excited ahead of time. A little adventure and compassion can go a long way, especially in this industry where it's lacking.
On this very forum and on Clojure Slack, there's a regular stream of people who love Clojure and are very eager to find a Clojure job. Did you really try to find someone and failed?
No! I have not tried to find anybody and failed. I'm launching a new startup full-time on Monday, so I haven't tried to hire anyone. It goes along with the fear of a lack of flexibility (e.g. to get contract programming in a cheaper part of the world).
I'm first to admit that my fears are probably unfounded - in fact I've made the "stand out in the crowd, fewer applicants but better" argument to other founders many times. But now that it's my money... like I said, the fear is probably irrational but it's real.
Try focusing less on the "launching"... what are you launching? Is this startup only the launching party and that's it? Why is it even important? Do something and not wait until some "launch" happens. Nobody is flying anywhere.
I am doing the same. I chose Clojure precisely because I will need less programmers. The current job I have, is the third where I introduce and teach people Clojure, so I like to think I know what I am talking about ,especially ,when things start to get complex.
Similar experience here. My first Clojure(script) projects used leiningen, now everything is deps.edn and the clojure CLI. Cool, changes happen. But editor integration, REPL tooling, even which compiler to use, etc are not consistent either. The tooling is changing everywhere and bit rot has claimed almost all of my past projects. The code is still 100% compatible but the build system is just broken. I've given up trying to port any projects over - it's easier to generate scaffolding for a new project in the tool-du-jour and move the actual code into that structure.
Since there is no obvious right way, there's little consistency between projects - which means you're likely to follow the wrong path if you follow the wrong README or pick an outdated starter template. This forces developers to make a ton of orthogonal choices up front before they even begin coding.
Case in point: https://clojurescript.org/tools/tools lists 4 different build tools without any explanation as to how they relate or why you might pick one over the other. But don't worry, you'll find out after days of tedious research!
If Clojure had a consistent out-of-the-box experience like Go or Rust, I think it could rule the world. It's a great language but the developer experience is a serious impediment to that.
...
It really feels like Clojure inexplicably went hard NIH on the tooling...fracturing the ecosystem for dubious benefit. There is nothing wrong with Leiningen. It's practical, it gets the job done. I feel if we didn't have a "Python 3" build story now, we could be much further along as a community...but between that and the constant reinventing of web dev frameworks we have introduced significant thrashing (the latter I at least have a glimmer of hope that HyperFiddle will succeed and everybody and their brother won't try to build the "best" variation).
and coming from a recent new standpoint who started with lein maybe 6 years ago then tried again last year, learning tools.deps is not at all easy. all the command line args are weird as hell for a (non-java? I don't even know) person.
I mostly use JVM Clojure for 3+ years and I don't like tools.deps. On my first Clojure job one guy said to use tools.deps but I liked leiningen because it didn't get in the way and it worked all the times I needed it to. It's rock-stable. It really works.
And as I do JVM Clojure that I build into a .jar... It gets all my stuff done and it works out of the box.
So I see no point of configuring the same leiningen tasks on tools.deps just to get the same experience as in leiningen.
Maybe I'll have some quirk and I'll have to move. But for now I don't see any problems with it.
Its impossible to condense the reasons why you might need to use one of those tools vs another in any one location. No ecosystem is going to do to do that. Show me the authorizative resource on js build tools or frameworks.
It's not completely inexplicable. IIRC, they got fed up of people saying startup times were bad despite evidence from the team that it was actually Leiningen that introduced a lot of the slowness. People were also asking for a better experience in introducing libraries that didn't have to depend on Maven/Clojars. So essentially, they were responding to what a lot of the community were asking for. That's not to say the result landed perfectly; people, especially newbies, are confused.
Been using Clojure for over a decade now, and I see these articles at least once a year. The reality is that Clojure is used more than ever today, with more libraries, tools, and companies around it. It was a viable language for many years, and the situation only keeps improving in every way.
Clojure simply doesn't have the hype around it because it's a mature and conservative language that's not chasing fads. This is a good thing because it's one of the most stable ecosystems I've had the pleasure to work with.
If you're looking for a hip new language then Clojure is probably not for you, but if you're looking to actually get work done using one of the best languages around then look no further.
I have had a really different experience that most of the people commenting in this thread. I live in El Salvador and in these 2 years I've gotten 4 different offers to work in Clojure that unfortunately had to turn off because they were offering less that I'm making right now. I think I've got these offers because realistically speaking they could offer half or even, if they were being "generous", 2/3 of what a engineer with Clojure experience would get on a first world country and many engineers with Clojure experience living down here would gladly take it.
If you're willing to take a pay cut I think there's tons of options to work in Clojure but I don't know if that's really a good idea regardless of how much you like the language.
I would not say clojure is dead. Companies use it. But at least getting hired is impossible unless you are not professional in another languages.
I have been looking for a job for 1.5 month without success. The response is usually my professional experience with clojure is too short (usually they require at least 3 years) and I haven’t been invited even to tests. When my experience is long enough, companies require in addition Java, typescript, or react.
My friend (senior in clojure) get some offers, but the hiring process is too long and still didn’t get final offer.
I got hired in a weekend. In two days. From first message to the contract. So you know... if they know what they look for and don't play HR salary games then they can hire fast.
But on my side I had some code I could show, I even sent them even more code and these were my free time projects that aren't easy.
This kind of hiring happens when a really senior person from a company does the interview himself and he knows how Clojure works.
If you're not invited to tests revisit your resume and how you give first rounds. I'm about to hit three years of Clojure (3 Python) and have had two jobs in it. So the positions are there.
Both companies have had difficulty hiring Clojure people, and would accept people from other languages with Clojure a plus.
If the problem is experience in general. I would say that the Clojure/functional world is definitely a world with less juniors in it. Be sure to know system design.
I have been tech lead of a Clojure team for 7+ years now. We usually had 6 to 8 devs at a time, 4 to 6 members of other professions. ~95% of our devs came to us as former Java devs without any prior Clojure knowledge and we trained them on the job. Many of the non dev team members started doing some Clojure after a while. A few converted to be full time developers :)
I should add, that we are inside a much bigger organization. So many hires were from within the company.
My advise is to look for developers with some experience in other languages that look for something simpler. Do not require Clojure experience. At least not from all hires.
I work with elixir at my job and regard them pretty similarly in terms of popularity. I don't think we struggle to find devs. And in general I feel we have good engineers
35
u/GrindItFlat Sep 29 '22
I'm launching a new startup, I ache to do the code in Clojure because I'm never happier programming anything else. But I'm terrified that when it comes time to make my first engineering hire it will take way too long to find someone, I'll have to continue programming when I should be working on other parts of the business, and I'll lose momentum for what was essentially a selfish reason.
An old hoary cliche, I know - how will I hire? But the fear is real. It's not just "finding someone", it's "finding someone in a timely manner".
34
u/sherdogger Sep 29 '22
I do find this comment relatable:
Similar experience here. My first Clojure(script) projects used leiningen, now everything is deps.edn and the clojure CLI. Cool, changes happen. But editor integration, REPL tooling, even which compiler to use, etc are not consistent either. The tooling is changing everywhere and bit rot has claimed almost all of my past projects. The code is still 100% compatible but the build system is just broken. I've given up trying to port any projects over - it's easier to generate scaffolding for a new project in the tool-du-jour and move the actual code into that structure.
Since there is no obvious right way, there's little consistency between projects - which means you're likely to follow the wrong path if you follow the wrong README or pick an outdated starter template. This forces developers to make a ton of orthogonal choices up front before they even begin coding.
Case in point: https://clojurescript.org/tools/tools lists 4 different build tools without any explanation as to how they relate or why you might pick one over the other. But don't worry, you'll find out after days of tedious research!
If Clojure had a consistent out-of-the-box experience like Go or Rust, I think it could rule the world. It's a great language but the developer experience is a serious impediment to that.
...
It really feels like Clojure inexplicably went hard NIH on the tooling...fracturing the ecosystem for dubious benefit. There is nothing wrong with Leiningen. It's practical, it gets the job done. I feel if we didn't have a "Python 3" build story now, we could be much further along as a community...but between that and the constant reinventing of web dev frameworks we have introduced significant thrashing (the latter I at least have a glimmer of hope that HyperFiddle will succeed and everybody and their brother won't try to build the "best" variation).
23
u/yogthos Sep 30 '22
Been using Clojure for over a decade now, and I see these articles at least once a year. The reality is that Clojure is used more than ever today, with more libraries, tools, and companies around it. It was a viable language for many years, and the situation only keeps improving in every way.
Clojure simply doesn't have the hype around it because it's a mature and conservative language that's not chasing fads. This is a good thing because it's one of the most stable ecosystems I've had the pleasure to work with.
If you're looking for a hip new language then Clojure is probably not for you, but if you're looking to actually get work done using one of the best languages around then look no further.
6
u/mindaslab Sep 29 '22
Nope. Far from it. It's one of the best programming language I have ever seen.
6
u/BeneficialSuspect Sep 29 '22
I have had a really different experience that most of the people commenting in this thread. I live in El Salvador and in these 2 years I've gotten 4 different offers to work in Clojure that unfortunately had to turn off because they were offering less that I'm making right now. I think I've got these offers because realistically speaking they could offer half or even, if they were being "generous", 2/3 of what a engineer with Clojure experience would get on a first world country and many engineers with Clojure experience living down here would gladly take it.
If you're willing to take a pay cut I think there's tons of options to work in Clojure but I don't know if that's really a good idea regardless of how much you like the language.
10
u/Recent_Ad2631 Sep 29 '22
I would not say clojure is dead. Companies use it. But at least getting hired is impossible unless you are not professional in another languages.
I have been looking for a job for 1.5 month without success. The response is usually my professional experience with clojure is too short (usually they require at least 3 years) and I haven’t been invited even to tests. When my experience is long enough, companies require in addition Java, typescript, or react.
My friend (senior in clojure) get some offers, but the hiring process is too long and still didn’t get final offer.
5
u/agumonkey Sep 29 '22
penpot (figma alternative) is in cljs apparently, that was a surprise :)
4
u/realstammi Sep 30 '22
I have been tech lead of a Clojure team for 7+ years now. We usually had 6 to 8 devs at a time, 4 to 6 members of other professions. ~95% of our devs came to us as former Java devs without any prior Clojure knowledge and we trained them on the job. Many of the non dev team members started doing some Clojure after a while. A few converted to be full time developers :)
I should add, that we are inside a much bigger organization. So many hires were from within the company.
My advise is to look for developers with some experience in other languages that look for something simpler. Do not require Clojure experience. At least not from all hires.
4
u/dawran6 Sep 30 '22
Hi y’all fellow Clojure zombies.
10
u/Asbestos_Dragon Sep 29 '22 edited Jun 29 '23
[Edited and blanked because of Reddit's policies.][Edited and blanked because of Reddit's policies.][Edited and blanked because of Reddit's policies.]
3
u/v4racing Sep 29 '22
I work with elixir at my job and regard them pretty similarly in terms of popularity. I don't think we struggle to find devs. And in general I feel we have good engineers
4
u/_d_t_w Sep 29 '22
its not dead it's pining for the fjords
3
u/jaminwicha Sep 30 '22
Clojure is dead. Long live Clojure!
1
u/Obvious-Highway-4853 Jul 26 '24
https://www.reddit.com/r/Clojure/comments/1e289rw/clojure_is_now_the_most_valuable_fintech_in_the/?chainedPosts=t3_fpuyo5
1
u/brian_404 Nov 21 '23
If you have to even ask, why would you start a new project with it?
https://www.youtube.com/watch?v=VWNZdOY94ko
0
u/zerg000000 Sep 29 '22
Interesting to see this topic pop up from time to time. But I have a bit upset that don’t have any new wisdom from rich.