This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-09-17
Channels
- # announcements (2)
- # aws (7)
- # beginners (46)
- # cider (15)
- # clj-kondo (24)
- # cljs-dev (3)
- # clojure (46)
- # clojure-dev (34)
- # clojure-europe (7)
- # clojure-italy (7)
- # clojure-nl (10)
- # clojure-norway (15)
- # clojure-spec (5)
- # clojure-uk (42)
- # clojuredesign-podcast (1)
- # clojurescript (79)
- # clr (3)
- # core-async (1)
- # cursive (45)
- # data-science (1)
- # datomic (4)
- # fulcro (17)
- # funcool (14)
- # gorilla (2)
- # graphql (30)
- # jackdaw (5)
- # jobs-discuss (8)
- # joker (4)
- # lein-figwheel (1)
- # off-topic (48)
- # pedestal (26)
- # re-frame (36)
- # reagent (18)
- # reitit (6)
- # remote-jobs (4)
- # shadow-cljs (115)
- # tools-deps (62)
- # vim (12)
@davd33 @seancorfield I think also that if you have "senior engineer" type experience in other languages, or even just professional experiences in multiple other languages, you'd have a much better chance. I cut my Clojure teeth working for CircleCI, and was fully remote from day 1. That's not how Circle works any more, but I suspect that's more about rapid growth and needing to hire faster and more reliably than anything else. I think it might still be OK for an early stage startup job where there's an appetite to cultivate good people, or a large corp where they can afford to absorb the inefficiency.
Oh, and also experience working remote in your previous jobs, which it looks like you have
@seancorfield @j0ni Thank you for your advice!
If you can do the interview work in Clojure (and the interview itself is a good work test rather than being brain teasers)
And if either the company or you are senior enough that the additional onramping won’t be too challenging