This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-01-25
Channels
- # aatree (3)
- # admin-announcements (14)
- # aws (2)
- # beginners (23)
- # boot (58)
- # braid-chat (15)
- # cider (8)
- # clara (5)
- # cljs-dev (1)
- # cljsrn (38)
- # clojure (82)
- # clojure-china (2)
- # clojure-czech (16)
- # clojure-dev (11)
- # clojure-finland (1)
- # clojure-ireland (6)
- # clojure-japan (3)
- # clojure-portugal (1)
- # clojure-russia (152)
- # clojure-sg (7)
- # clojurebridge (3)
- # clojurescript (86)
- # code-reviews (3)
- # core-matrix (4)
- # cursive (25)
- # data-science (1)
- # datascript (2)
- # datavis (98)
- # datomic (21)
- # dirac (97)
- # emacs (1)
- # hoplon (1)
- # jobs (2)
- # ldnclj (21)
- # off-topic (3)
- # om (204)
- # pedestal (3)
- # proton (12)
- # reagent (125)
- # ring-swagger (9)
- # slackpocalypse (1)
- # spacemacs (1)
- # vim (1)
- # yada (19)
Hi everyone. My company Yummly is looking to add another Clojure developer to our team. Focus will be mostly on the backend/API. Tech stack is very interesting and we have opportunities to try new things: - Clojure 1.8 - Core.async - Some internal tools are implemented in OM - We are fully automated and our DevOps code written all in Clojure. We run on AWS (EC2, DynamoDB, Elasicache, CloudFormation, etc) - We’ve been using Docker and CoreOS for couple of years in prod - We are always concerned about scaling but we do move fast - Integration points beside regular datastores and caches are Solr, recommendation engine and other analytics products.