This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-09-14
Channels
- # announcements (40)
- # aws (9)
- # babashka (21)
- # beginners (75)
- # calva (56)
- # chlorine-clover (1)
- # cider (12)
- # circleci (1)
- # clj-kondo (7)
- # cljsrn (13)
- # clojars (3)
- # clojure (171)
- # clojure-dev (11)
- # clojure-europe (64)
- # clojure-nl (11)
- # clojure-spec (6)
- # clojure-uk (9)
- # clojurescript (31)
- # conjure (1)
- # cursive (7)
- # datascript (7)
- # datomic (9)
- # emacs (4)
- # fulcro (65)
- # introduce-yourself (1)
- # jobs-discuss (7)
- # kaocha (7)
- # lsp (39)
- # missionary (5)
- # off-topic (54)
- # pathom (10)
- # re-frame (6)
- # shadow-cljs (110)
- # tools-deps (41)
There has been a lot of discussion here on how interviews aren't an effective way of determining if someone will be a good dev on your team. I wrote up my thoughts, feedback is welcome: https://medium.com/codex/how-to-interview-software-developers-87239ca494ab
cc @UQP60F2B1 that’s pretty similar to what we’re doing, but still interesting read.
Surprisingly, in over 4 years of searching for Clojure jobs, I've only ever been asked to live code once. The approach you describe, also once. Usually it's take-home tests.
In this sense the best approach I have seen in the Clojure land is the way Nubank approaches the problem. They give a take home exercise, but a really simple one, without any trap, it’s pretty simple and something that is related to what they do day-to-day, and along with it, they also require a System Design interview, and that is it. Sad to still see a lot of companies demanding full working complex software to be made at home or also obligating people to think at loud in live code exercises
Hey that's a neat idea. One company I interviewed at had a "take home test" that you could skirt if you sent in a public github repo to talk about. Seems reasonable.