jobs-discuss

2024-01-24T15:20:19.599899Z

Is there an appropriate channel to post a job posting that is not a Clojure job? This is a tech lead position working with graph databases and Java at Southwest Airlines

bherrmann 2024-01-26T02:08:02.098349Z

Thanks for all the Ops for making this a saner place.

2
➕ 2
Kirill Chernyshov 2024-01-24T15:23:19.386549Z

there is recently created #jobs-non-clojure but it is not very popular

1
Martynas Maciulevičius 2024-01-24T16:17:14.206969Z

I think it's the best bet for you. Because if you'll post into Clojure job channels your post will be deleted. I created the channel 3 days ago and I didn't advertise it anywhere at all. And currently there are 17 people in the channel already. So don't think that if it's small it's meaningless. It's very fresh. And somebody will be the first to post their job there. https://clojurians.slack.com/archives/C05006WDW/p1705825980034179?thread_ts=1705783973.962399&cid=C05006WDW

2024-01-24T17:24:25.849289Z

there's always #off-topic as well

Martynas Maciulevičius 2024-01-24T17:47:51.336839Z

25 people. People are watching.

marciol 2024-01-24T18:41:03.440999Z

Yes, as the Clojure jobs are getting increasingly rare, makes total sense to have this channel.

seancorfield 2024-01-24T19:06:49.727919Z

The general sense of the admin team is that we don't want to encourage non-Clojure jobs being posted anywhere here because we are concerned that recruiters (and less reputable agencies and individuals) will start posting arbitrary jobs and we won't be able to realistically enforce a rule that determines who can and who can't post non-Clojure jobs.

💯 1
👀 1
marciol 2024-01-24T19:07:14.865229Z

makes sense

seancorfield 2024-01-24T19:08:45.921659Z

(we had a long discussion about the recent non-Clojure post -- that the OP later deleted -- because we felt it was reasonable for "members in good standing" to post non-Clojure jobs if it relates to where they are working and has the potential to create "critical mass" to get Clojure into a company... but that is very vague and hand-wavy and impossible to police... hence the concern)

👍 1
seancorfield 2024-01-24T19:10:39.349359Z

I've joined #jobs-non-clojure to make sure we have admin-eyes on it -- but it won't help people if it either remains a very small channel nor if it becomes inundated with recruiters/spam.

👍 5
seancorfield 2024-01-24T19:13:00.742089Z

(FWIW, behind the scenes we have a constant problem with both clueless recruiters and various drive-by "full-stack" agency types offering random work engagements that we delete -- and deactivate the account -- so y'all probably don't even see them appear since someone in the global admin team has deleted it within minutes of it appearing!)

5
Martynas Maciulevičius 2024-01-24T19:58:57.688719Z

Why not delete the channel then? Or at least write something where people wouldn't write to recruiters themselves.

➕ 1
seancorfield 2024-01-24T20:26:30.531939Z

Not sure what you mean by the second part but, for the first question: we don't randomly delete channels unless they have actually become a problem -- and we don't (currently) restrict who can create public channels, nor place any restrictions on channel names or topics (beyond the Code of Conduct, of course).

seancorfield 2024-01-24T20:28:01.954899Z

FWIW, this welcome message is sent to every new person who joins https://github.com/clojurians/community-development/blob/master/welcome-message.md but bad actors ignore the rules anyway...