This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-04-19
Channels
- # announcements (3)
- # aws (1)
- # beginners (25)
- # calva (6)
- # cider (55)
- # clara (13)
- # cljs-dev (3)
- # clojure (79)
- # clojure-europe (1)
- # clojure-nl (6)
- # clojure-spec (59)
- # clojure-uk (6)
- # clojurescript (97)
- # clojureverse-ops (2)
- # cursive (7)
- # data-science (4)
- # datomic (12)
- # emacs (8)
- # figwheel-main (19)
- # fulcro (67)
- # graalvm (3)
- # graphql (12)
- # jobs (4)
- # jobs-discuss (11)
- # lein-figwheel (5)
- # off-topic (50)
- # om (1)
- # other-languages (1)
- # planck (3)
- # quil (2)
- # re-frame (4)
- # reitit (5)
- # remote-jobs (5)
- # ring-swagger (2)
- # shadow-cljs (34)
- # spacemacs (8)
- # xtdb (1)
- # yada (4)
my job is hesitant to post a job posting because http://indeed.com will scrape it leading to 1000s of unqualified emails. anyone know how to get around this?
Write any contact information as a clojure expression, like (apply str (map (comp char dec int) "jogpAdpnqboz/dpn"))
Omit the contact details and have people DM you for the full posting?
Assuming you’d be willing to answer the DMs
FWIW I got my current position responding to someone who said “DM me for details”
I also did something similar on a different Slack, where I was on the receiving end of the DMs, got back a few responses in the first few days, then nothing after that. Of course, I have next to zero DM activity usually, so getting lost wasn’t a problem for me.
Some job postings require you to curl
your application to some API endpoint, with a secret that you must figure out first.
Till now I thought it was just nerdy humor but now I see why might one want such a thing...
woo. I once spent time working on that type of secret only to hear the position was no longer open. I guess that was the real secret.