This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-07-14
Channels
- # aleph (3)
- # announcements (1)
- # babashka (36)
- # babashka-sci-dev (4)
- # beginners (62)
- # biff (2)
- # calva (13)
- # cider (4)
- # clj-kondo (6)
- # cljdoc (17)
- # clojure (142)
- # clojure-dev (6)
- # clojure-europe (62)
- # clojurescript (20)
- # core-async (26)
- # cursive (18)
- # data-oriented-programming (9)
- # data-science (1)
- # datahike (18)
- # events (4)
- # fulcro (4)
- # graalvm (2)
- # hyperfiddle (15)
- # interop (1)
- # jobs-discuss (8)
- # leiningen (2)
- # lsp (91)
- # malli (1)
- # missionary (11)
- # nbb (65)
- # off-topic (50)
- # practicalli (2)
- # programming-beginners (4)
- # re-frame (18)
- # remote-jobs (1)
- # shadow-cljs (53)
- # spacemacs (1)
- # specter (2)
- # sql (17)
- # tools-build (63)
- # web-security (1)
- # xtdb (15)
Need some insight here. I want to start applying for jobs writing Clojure and would like to know if I should. To give it some context: I am self-taught and I've been coding for a year now. Learned Clojure, Golang, Rust, Lua, Typescript, Python, some Haskell and Ruby, enough Bash (it's Bash :man-shrugging::skin-tone-2:), a little OCaml, a pinch C, also some less known languages. Did some machine learning, wrote quite a few compiler parts (scanners, parsers and lexers), did lots of data wrangling and web scraping, wrote a few basic web apps with Reagent, React, WASM. I know my way around Linux and love a CLI, also use docker, although not frequently. Have some understanding of web servers, clients, msgpack and LSPs. I've done some concurrency but not much. Also worked with some data serialization languages like TOML, YAML, EDN, but no query languages. Non IT-related, I've got a degree in Economics. Am I ready to apply for a Clojure(Script) job?
There are companies that hire people that want to use Clojure but have no experience at all. https://jobs-blog.braveclojure.com/2022/03/24/long-term-clojure-benefits.html#these-clojure-companies-hire-people-without-clojure-experience
Thanks, I'll look into that right now.
Like anything, it's not a yes/no question. It's not for employers either - for them many CVs look quite alright. For example while at Cisco I got to eye a few CVs and my thoughts were 'they're all great' and didn't want to say yes/no to anyone in particular π¬
I believe that everything counts, and the more things that you have to 'count', the better!
Some quick examples: Java, concurrency (the JCIP book is amazing, you can see holding it in a talk), having some OSS projects and contributions, authoring blog posts. And so on.
No employer ever says "oh he doesn't have blog posts, guess it's a deal breaker" but, it's stuff that holistically (subconsciously?) does matter. In the end, it's about conveying certain feelings - enthusiasm, professionalism, etc. Many people really want/need to be excited for candidate - facts are just a proxy for those feelings.
We live in a competitive world. Even more so in the Clojure ecosystem, which is relatively small and full of amazing, experienced people.
It took me a while to feel at ease here, I had to work my way quite hard in the beginning. Nowadays I definitely can navigate much more comfortably. You might want to think of this as a one-off big investment.
Hope it helps!

Should be fine to apply. As others have said, clojure experience is not always required. Having something to say about why you want to work specifically with Clojure may be useful. I'd recommend trimming down your list of languages. Maybe you are super competent in all of these, but someone hiring might read it as "every programming language I've ever touched" which calls into question other assertions in your application. Best of luck with your applications π
@U45T93RA6 thanks for the tips. I'll keep those in mind and I guess it's time to start a blog then. @UE7LPTG1L very nice insight there, I'll make sure to have enough output to sustain any claims I make in job applications.
thank you all for the insights, it's been of much help. βΊοΈ