This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-06-01
Channels
- # babashka (30)
- # beginners (80)
- # calva (21)
- # chlorine-clover (2)
- # cider (22)
- # clj-kondo (65)
- # cljfx (2)
- # cljs-dev (3)
- # cljsrn (3)
- # clojure (37)
- # clojure-europe (27)
- # clojure-italy (3)
- # clojure-nl (2)
- # clojure-taiwan (1)
- # clojure-uk (21)
- # clojurescript (13)
- # conjure (23)
- # core-typed (1)
- # cursive (16)
- # datahike (1)
- # datomic (6)
- # docs (2)
- # emacs (5)
- # figwheel-main (1)
- # fulcro (12)
- # helix (11)
- # jobs (2)
- # jobs-discuss (2)
- # leiningen (1)
- # lsp (34)
- # luminus (1)
- # malli (19)
- # microservices (1)
- # nrepl (1)
- # off-topic (25)
- # pathom (6)
- # polylith (47)
- # practicalli (5)
- # re-frame (8)
- # reagent (1)
- # reitit (1)
- # releases (2)
- # remote-jobs (2)
- # reveal (1)
- # sci (1)
- # shadow-cljs (11)
- # sql (8)
- # tools-deps (9)
- # xtdb (16)
^ We always have candidates interview with members of the team. Almost as important as assessing a technical 'fit', is allowing people to interact with their (future) team and both coming away feeling like it would be a good 'fit' team-culture-wise.
This "meet the team" practice is definitely the standard, and quite a mistake. Part of a manager's job is knowing whom to hire. The manager should be building a technical team, not a social club. Meanwhile, throwing a candidate to a pack of typical socially unskilled engineers is a disaster; they just look for themselves, so the gene pool is quickly corrupted by the in-breeding and lack of diversity. I started in IT forty years ago. We all just worked together. We called it a "job". We made our friends off the field.