This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-01-15
Channels
- # aws-lambda (3)
- # beginners (17)
- # boot (65)
- # cider (3)
- # cljs-dev (7)
- # cljsrn (82)
- # clojure (82)
- # clojure-italy (1)
- # clojure-russia (25)
- # clojure-spec (56)
- # clojure-uk (5)
- # clojurescript (52)
- # css (2)
- # datomic (6)
- # emacs (1)
- # hoplon (9)
- # jobs-discuss (5)
- # leiningen (8)
- # mount (2)
- # nginx (1)
- # off-topic (2)
- # om (1)
- # om-next (9)
- # perun (13)
- # portland-or (1)
- # re-frame (13)
- # reagent (20)
- # remote-jobs (2)
- # ring (5)
- # spacemacs (1)
- # specter (10)
- # untangled (5)
- # yada (6)
@dottedmag I agree with you on principle, but most of the time geographical limitations for remotes (EU/US only) are due to limiting bureaucratic effort: accounting for all the possible cases could get very messy very soon!
(Source: I worked remotely for 4+y, for EU amd US)
@nilrecurring I'm referring to "super remote-friendly", which is kind of a misnomer if "remote" means "remote within a country".
Is US very different from other countries in this regard? I work for a company which is truly remote-friendly (but alas not Clojure-friendly) and the amount of paperwork needed to hire someone locally vs. from abroad (as a full-time contractor) is similar.
I agree for contractors, paperwork is similar, but for employees is definitely more complicated