[lumost]

Specific language expertise rarely matters. I intentionally avoid discussing specific technologies used to achieve results/goals/services unless it's highly relevant (e.g. creating a RESTful web service etc.)

It's good to have your technologies listed, and be honest if your doing something out of your comfort zone... but there really isn't a technology out there that can't be picked up in 1-3 months.

[Edd314159]

> Specific language expertise rarely matters.

+1 to this. Especially at the 16-years-experience level. Maybe earlier in someone's career where their primary focus is how to fit in and ship stuff without getting stuck all the time. But at ~staff level, your thinking and your contributions become a lot more language-agnostic (not entirely, but mostly)

[roguas]

I would not say that clojure/haskell/elixir can be picked up in 1-3 months in most environments. I do agree that you should highlight broader engineering experience and keep langs/techs as merely a proof of some competence in those.

If the job mentions the technology and most clojure/haskell/elixir dev jobs do then well unless they state "looking for experienced person willing to learn" in description I would not bother them. (at least with my complete lack of experience in tech). Similarly as I would not apply to "weird-tech-i-merely-heard consultant". Also think there should be consistency on the job titles/descriptions on the side of job posters.