This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-08-06
Channels
- # aleph (1)
- # announcements (2)
- # beginners (109)
- # calva (48)
- # cider (25)
- # clj-kondo (38)
- # cljdoc (13)
- # clojure (203)
- # clojure-europe (23)
- # clojure-gamedev (3)
- # clojure-nl (3)
- # clojure-uk (7)
- # conjure (2)
- # data-science (1)
- # datalog (2)
- # datomic (7)
- # deps-new (16)
- # depstar (2)
- # docker (2)
- # fulcro (67)
- # graalvm (58)
- # honeysql (16)
- # java (2)
- # jobs (2)
- # jobs-discuss (2)
- # kaocha (4)
- # lsp (82)
- # malli (23)
- # off-topic (35)
- # polylith (18)
- # practicalli (5)
- # releases (1)
- # remote-jobs (1)
- # shadow-cljs (15)
- # sql (17)
- # timbre (1)
- # tools-deps (24)
- # vim (20)
- # xtdb (9)
Building a proper interview process that suits your company's individual needs requires careful analysis, research, and constant adjustment and re-evaluation. Unfortunately most tech cultures don't incentivize this kind of work and you get startup VP's blindly copying what they're used to. If you're lucky they might take another look 8 months later
A company's hiring process, like everything else, should be subject to constant reflection, review, retrospection, and improvement. It's what Agile is supposed to mean, instead of that top-down, "why is your velocity so low?" garbage that most companies end up with. Edit to add: I agree with you completely; I'm just adding on top of your point.