Fork me on GitHub

Looking at this, Clojure is paying big bucks. But when looking at job postings here and on LinkedIn, the advertised salaries are similar to Java. What am I missing?


One possible factor is that not all jobs are advertised. Another factor is that those that are advertised might specify lower compensation than the actual one (e.g. because the employee/contractor was able to negotiate). Yet another factor is that a lot of jobs don't specify compensation. It's basically missing data - you don't know the distribution of such jobs when it comes to Clojure vs Java, you don't know the salary ranges, so you can't judge at all.


Questionnaires are also invariably skewed. Hard to say how exactly, but the results 100% do not represent the reality.


The survey results match my anecdotal experience. But of course anecdotes aren’t worth much, so I tend to take the survey results at least a bit more seriously than anecdotal experience. I agree with @U2FRKM4TW also, that the salary distribution of job postings and the salary distribution of Clojure employees could be quite different.


Averages. There are probably 100,000s of thousands of very low-level Junior Java jobs out there that you're not even seeing. They drag average and median down.

☝️ 1

Why is Clojure paying big bucks in the first place?


Is that due to a) they produce more (High ROI) or b) they are hard to find (scarce resource; hence costly)?


Or any other reason


Keep in mind that we're talking about averages (or medians, doesn't matter much in this case) and not "everybody swims in money". With that being said, Clojure developers are usually senior ones. And those get paid more than junior or middle ones.


so the "usual" seniority is the reason of high paid jobs. That would be true for any old language then


so its not a) or b) ? (just talking generally)


I don't see how those two are related. Seniority isn't that strongly correlated with age. And it's definitely not a causative relationship - being old doesn't make someone a senior developer automatically. Also, on an anecdotal level of evidence, it seems to me that a decent amount of old and obscure languages get "fresh blood" by hiring students. E.g. plenty of institutes, at least in Russia, use FORTRAN. Plenty of old financial institutions hire university graduates and use COBOL internally. And so on.


"being old doesn't make someone a senior developer automatically." <-- absolutely you are correct. I meant skill seniority. usually comes with time but not always...


Right, that's why I said I don't see how a language being old is a factor here. :)


@U2FRKM4TW I assume that the language was assumed to be returning more on investment. return: productivity investment: time


thus making devs precious but its a long debate


Clojure is an old language? Isn't it from 2008 or something? 😄


I don't think that point was made in this thread at all. The initial thesis was basically "if senior developers are paid more, then working with an old language would pay more", with which I disagreed.


> so the "usual" seniority is the reason of high paid jobs. That would be true for any old language then


Yes, the second statement doesn't talk about Clojure at all. Just about "any old languages". Not sure what point you're trying to make.


I’ve heard it to be attributed to Clojure developers being fairly experienced

👍 2

I like to explain why clj's doing well is that it's filled with old grumpy programmers who see the same problems rich talks about, so it's fairly top heavy on the experience curve

👨‍🦯 1