Clojurians
#jobs
<
2016-03-05
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

hiredman00:03:49

(I say that, because I am going through the list of companies that use clojure listed on the clojure website, trying to get another remote clojure job)

rmuslimov00:03:07

- xkcd in your daily-read list

rmuslimov00:03:31

that was one of desired skills in job description above, nevermind

bridget14:03:13

I have to agree with hiredman. I've been privy to a number of senior Clojure devs' job searches over the past few months, and every single one of them was looking for remote positions only. If you are looking to hire senior Clojure people and having trouble, I'd say it would be worth the trouble to invest in building a remote team. My $.02.

alandipert14:03:17

I'd be curious to know how senior remote devs mentor juniors

alandipert14:03:02

or hear stories about having successfully graduated a junior to a senior on a remote team... i've never seen it done in my own experience, but my experience is narrow

borkdude14:03:33

yeah, it seems difficult to me

donaldball15:03:27

Lots of pairing initially, giving them lead on small, well-specified projects on which they can make mistakes and iterate on ‘em

lmergen17:03:55

yes, i am starting to regret my move as CTO to promote Clojure

lmergen17:03:05

it's almost impossible to get local Clojure devs

lmergen17:03:42

i have a 6 person team, of which we need one more senior clojure backend programmer... and nobody appears to be willing to relocate and/or in the area

lmergen17:03:59

but yes, we are using what's being called "teamboosting"

lmergen17:03:16

so we hire very senior experts to become "part of the team" for a week or so

lmergen17:03:47

that works out pretty well, but it's always a gamble -- it must require the remote engineer to be very communicative

borkdude18:03:26

@lmergen: what area are you in

lmergen18:03:57

video distribution platform + analytics

lmergen18:03:41

so anyway, i've shifted my focus on getting people that have some affinity with FP in general trained in clojure

lmergen18:03:57

and we can do that by using "teamboosting" with seniors who help out a few hours a week

borkdude18:03:13

@lmergen: cool, are you coming to Dutch Clojure Day?

lmergen18:03:21

when is that?!

lmergen18:03:39

i should bring the whole fucking dev team haha

lmergen18:03:53

oh damn, i'm definitely gonna be there

borkdude18:03:08

sold out I'm afraid

lmergen18:03:18

looks like i have to send someone an offer they cannot refuse to get there

borkdude18:03:27

or become a sponsor

lmergen18:03:13

even the wait list is full... lol

borkdude18:03:32

@lmergen: you can always come to the Clojure meetup in Amsterdam or organize one

lmergen18:03:32

well at least that tells me there's a lot of traction of clojure around here

borkdude18:03:34

at your company

lmergen18:03:50

i take it you're from here also?

lmergen18:03:02

good to know

lmergen18:03:35

and you work fulltime at a regular job, or do something different ?

borkdude18:03:59

I just started a job and a quit a job where I used Clojure, crazy enough :stuck_out_tongue:

borkdude18:03:27

yeah, a bit... I still have to figure out how much I will miss clojure :wink:

lmergen18:03:49

well, if you miss it too much, and would enjoy working at a startup... give me a call :simple_smile:

borkdude18:03:03

but one of the things was, I was only one of two people at the company who did it. I wasn't really part of a team

lmergen18:03:27

so now they have a clojure code base and just lost half of their dev team... hmm :simple_smile:

hiredman18:03:17

@alandipert: so I just spent five years working for a company where the devs were all remote, and as others have mentioned initial hires spent a while pairing, and then we had a very strong code review practice

borkdude18:03:34

@lmergen: I did my best to train people before I left

borkdude18:03:36

:simple_smile:

borkdude18:03:13

@lmergen: you could post a message to the clojure meetup mailing list for a job of course

hiredman18:03:54

generally, when I interview, the reasoning I get for requiring people to be onsite is something like "we are trying to build a close knit team", which is crazy to me, I am still in touch with most of the team members from that job that was 100% remote. we have almost an alumni thing going on

borkdude18:03:34

@hiredman: it is more difficult when it's mixed remote and on site probably. The people who are remote miss a lot that way. When everybody is remote, it's easier, because all communication happens online

lmergen21:03:41

hiredman: well, as an employer, i see the benefits of working remote

lmergen21:03:57

but i do like to have everyone in the office at least once a week

lmergen21:03:02

as in, together

lmergen21:03:03

drink beer

lmergen21:03:34

oh sorry @dottedmag i didn't see your msg

yogidevbear21:03:19

On the topic of remote teams, I watched this talk by Floyd Marinescu. Found it quite interesting. https://www.youtube.com/watch?v=i71bbQqdy0M&amp;list=PLJNI511LYmA48dKjzQUSIgVz13Zg9NXZC&amp;index=5

yogidevbear21:03:39

Worth viewing the entire talk

lmergen23:03:09

thats a great talk!!