Fork me on GitHub
#jobs-discuss
<
2019-04-19
>
dpsutton13:04:50

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?

solf17:04:40

Write any contact information as a clojure expression, like (apply str (map (comp char dec int) "jogpAdpnqboz/dpn"))

manutter5113:04:05

Omit the contact details and have people DM you for the full posting?

manutter5113:04:59

Assuming you’d be willing to answer the DMs

manutter5113:04:16

FWIW I got my current position responding to someone who said “DM me for details”

dpsutton13:04:50

slack dms are a bad vehicle. very easy for them to get lost in history

dpsutton13:04:54

but that's nice

manutter5113:04:34

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.

vemv13:04:37

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...

😆 8
Eric Ervin01:04:47

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.

😅 16
drone13:04:05

That was also my experience when posting an opening here and the FP slack. Received a few DMs over first few days. And did end up finding someone!