This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-07-07
Channels
- # bangalore-clj (3)
- # beginners (103)
- # boot (13)
- # cider (16)
- # cljs-dev (192)
- # cljsrn (44)
- # clojure (147)
- # clojure-dev (1)
- # clojure-italy (79)
- # clojure-norway (1)
- # clojure-russia (9)
- # clojure-spec (4)
- # clojure-uk (34)
- # clojurescript (65)
- # core-async (1)
- # core-logic (2)
- # core-typed (5)
- # cursive (1)
- # datascript (9)
- # datomic (26)
- # emacs (8)
- # garden (1)
- # hoplon (11)
- # humor (1)
- # jobs (1)
- # jobs-discuss (8)
- # jobs-rus (3)
- # leiningen (1)
- # luminus (1)
- # lumo (1)
- # mount (6)
- # off-topic (16)
- # om (10)
- # om-next (1)
- # onyx (10)
- # parinfer (10)
- # pedestal (25)
- # re-frame (27)
- # reagent (3)
- # rum (47)
- # uncomplicate (1)
- # unrepl (34)
- # untangled (120)
- # vim (58)
anyone else get the feeling that there's a much higher than typical number of full-stack stuff in clojure jobs?
here's my guess on that: lots of places using clojure have smaller teams, and possibly smaller budgets, and therefore are more likely to want someone who can work across the stack rather than specialize on the back or front end
and/or
people who are seeking out clojure specifically are likely to already be more versatile so it makes more sense to hire them to do more
We're unusual in being a small company with separate small front-end and small back-end teams, so I agree with @jrotenberg here.
my guess, based on recently trying to hire, is that anyone looking for a full stack/front end/back end person specific to clojure is happy to see clojure experience in any one of those capacities on a resume