Clojure/ClojureScript and Datomic engineer at Listoria, London or remote

Listora is seeking a Clojure/ClojureScript and Datomic engineer

Reply to Henry dot ec at Gmail dot com

London based start up with highly experienced (and awesome) distributed team of researchers, engineers and designers. Although the project is still in its infancy (very greenfield), we have a big vision of being the global leader in high-quality structured events data, which will help to drive the contextual and personalised event discovery experiences of the future.

We’re developing our platform along with applications that meet the needs (jobs/outcomes) of content data partners, event organisers, publishers and developers. It’s both a huge CS and product challenge and we need exceptional and ambitious people to solve the problems that we’ll come up against.

We’ve been developing our core platform with Clojure + Datomic/Cassandra and our applications with ClojureScript/Om. We have a very advanced stack that any passionate FP engineer would be excited about working on. We also regularly work in the open source community and are already releasing libraries.

In terms of product, we have an upfront investment in high quality research and concept evaluation taken from years of experience using both customer and outcome driven development methodologies. We are very open in what we do and have a toolset to build our products very closely with our customers. We don’t work to deadlines, but we do spend a lot of time thinking about the prioritisation of what we are and could be building.

We are looking for engineers to join our team that can hit the ground running. The right person will be self-motivated, conscientious, humble and a great communicator. We are looking for people with many years FP experience in senior, lead or architectural roles and are used to working in a start up environment with start up tooling.

We want to work with fantastic engineers and passionate people. This is one of the things that motivates us. We don’t mind where in the world you’re based or whether you want a permanent or contracting relationship.

If you’re the right fit with our team we will work hard to look after you – from giving you the flexibility to explore ideas and technologies for the job at hand to remuneration.

If you have any questions, we would love to hear from you.

Clojure/Clojurescript positions: DiligenceEngine, Toronto, Ontario, or remote

DiligenceEngine, a Toronto-based startup using machine learning to automate legal work, is hiring two Clojure/Clojurescript developers. They say:

We’re looking for a developer to work on our clojure/clojurescript/om web stack. Our team is small, pragmatic, and inquisitive; we love learning new technologies and balance adoption with good analysis. We prefer to hire near us, but also welcome remote work in a time zone within North America.

See the full job descriptions on the DiligenceEngine website.

Clojure Data Science/Software Engineer: HERE, Berlin

Job Description

We are searching for an outstanding Software Engineer with passion for Data Science to join our world-class Places Discovery team in Berlin.

The role

The Maps Search team builds our search and discovery capabilities. We are looking for a Data Scientist with the mindset of a problem solver. You know how data translates into product improvements and new features. You drive experiments. You automate data processing pipelines and create compelling visuals.

The ideal candidate will have exceptional coding skills, be a self-driven and systematic worker and share a deep love for creating software products. Join us! This position is full-time and based in Berlin (Mitte). The workplace is very international, the work language
is English.

More details here.

UIx expert, Clojure architect, remote/LA for movie startup

UIx expert, Clojure architect

You can be anywhere. We are located in Virginia Beach, but the company is likely to settle in Los Angeles. You would be coming in extremely early in the game.

Our startup will build a sort of wikipedia for movies, supporting medium form essays on movies and movie ideas. Differences from W:

— You annotate directly on the film using a unique space-time scrubber. Annotations include purely cinematic attributes.

— External content is interpreted and shown in-line, using a novel ‘outliner.’

— Everything is reactive functions, specified by users via drawing typed links.

— We support ‘situation theory’ (per Barwise and Devlin) using a categoric second sort. (Every user sees something different.)

— Something like OWL will be used for dynamic ontology graph creation, supporting ontological federation.

— We love movies, and use a novel sense of narrative dynamics in reasoning about film and in constructing essays.

— We’ll use Clojure for all the forward components and build a categoric, visual DSL. Some early work (now abandoned) was in Erlang.

— A second use (in a couple years) is multi-system biomedical research.

— We want to do something fun and significant. Maybe we will make someone rich. Maybe us, maybe not.

The project is inspired by work done for the intelligence community by folks that are now disgusted, and determined to repurpose what was invented.

Our current state is that many components are mocked up. Some LA heavyweights are involved. Some patents are granted, others pending. Funding is being sought. We think it better to work on prototype code than fake demos at this point, starting with the scrubber then outliner.

You would help design the overall architecture and code prototype bits. The position is expected to lead to being team leader for one of the components, and one responsibility will be to help build the team.

A downside is that we are inventing as we build. Some things will use simple good engineering principles; others will require new science and creative vision. Many of the UI conventions are experimental and will have to evolve as we go. You probably won’t be able to use an off the shelf framework/stack. It will be hard, hard, hard.

It is possible that a partner may emerge that wants native apps so we’ll have to pivot to include their stinky frameworks. We don’t yet know what the balance will be between contributing open source and keeping things proprietary, but we will do both.

Contact Ted Goranson at tedg then the at sign then alum.MIT then dot then edu.

We will initially send two academic papers: one for the biomedical community and the other on the scrubber for a forthcoming ACM UI conference.

Experienced Clojure/Datomic Engineer. New startup. Remote.

Experienced Clojure/Datomic Engineer

Anywhere in the world
Full time or contracting
Listora
New start up (3 months old) with highly experienced (and awesome) team of researchers, engineers and designers. Although the project is still hugely in its infancy (very greenfield), we have a big vision of being the global leader in structured events data, which will help to drive the event discovery experiences of the future.
In order to achieve this we’re developing a platform along with applications that meet the needs of event organisers, publishers and developers. It’s going to be a great challenge and we need exceptional and ambitious people to solve the problems that we’ll come up against.
We’re developing our core platform with Clojure and are also using Datomic – because they are the right tools for the problems that we’re solving. We have a very advanced stack that any passionate engineer would be excited about working on. We also regularly work in the open source community and are already releasing libraries.
We want to work with fantastic engineers and passionate people. This is one of the things that motivates us. We don’t mind where in the world you’re based, how many days a week you want to work or whether you want a permanent or contracting relationship.
In terms of product, we have an upfront investment in high quality and disciplined qual and quant research before we go into our prototyping phase. We are very open in what we do and have a toolset to build our products very closely with our customers. We have an advanced understanding of the behavioural needs of the market that we’re working in. We don’t work to deadlines, but we do spend a lot of time thinking about the prioritisation of what we are and could be building.
We are looking to add two engineers to our team that can hit the ground running. If you’re the right fit with our team we will work hard to look after you – from giving you the flexibility to explore ideas and technologies for the job at hand to remuneration.
If you have any questions, we would love to hear from you.

Clojure engineers, Staples Innovation Lab (Runa), San Mateo, CA

Runa is now Staples Innovation Lab. For the past 5+ years, Runa has been a visible member of the Clojure community, having built their entire e-commerce optimization stack on Clojure. We were recently acquired by Staples, the second largest internet retailer in the world.

We now have the resources to take the Clojure + Big Data + Machine Learning + Real Time Predictive Modeling engine to the next level. We’re looking for experienced engineers with knowledge of Clojure. More details at www.staplesinnovationlab.com

Clojure and Clojurians at Factual : Various Locations

Clojure and Clojurians at Factual

How We Use It

Factual began deploying Clojure to production in October of 2009. We used it cautiously and experimentally at first, confining ourselves to a narrow corner of our stack related to query interpretation.

As we experimented further with Clojure and applied it to more problems, we formed a very favorable impression of the overall language and related technologies. It’s true that Lisp is seen by many as a “weird” language, and to be sure, Clojure is not without its warts. On the other hand, if you’re looking for a fun and productive functional language that runs seamlessly on the JVM, Clojure brings massive value to the table.

SOME THINGS WE LIKE:

  • Significant developer productivity gains for certain use cases

  • Capitalizes on the superior power of Lisp

  • Everything Leo Polovets, Factual engineer, wrote in his answer on Quora: “Why would someone learn Clojure?”.

  • Often allows large reduction in code bloat vs. the equivalent Java solution. An unscientific survey of selected projects where we ported functionality suggests that we need 3X the code when working in Java.

SOME THINGS WE DON’T LIKE:

  • Not always super easy for non-Lispers to pick up

  • Some immaturity around things like tooling, stack traces, and the library ecosystem

  • May not be as performant as Java if you really, really need fast code

Aaron Crow, one of Factual’s early Clojure advocates, has a nuanced take on the matter:

“Please don’t make me write any more Java.”

Before long, we discovered Cascalog, a Clojure-based query language that runs on top of Hadoop. For certain use cases, we found Cascalog to be a huge win over the alternatives, especially when considering clarity of code and developer productivity. Since Cascalog queries provide a higher level of abstraction than pure Java-based MapReduce jobs, there may be concessions made to performance, but the code is also much easier to understand and maintain.

Chun Kok, author of “Clojure on Hadoop: A New Hope“, is philosophical about the trade-offs:

“Why not use Hive?”

Evan Gamble, our most seasoned Lisp veteran, applies Clojure to solve some of Factual’s more challenging Machine Learning problems. He explains his love of Clojure thusly:

“It’s still not as good as Common Lisp.”

Zach Tellman, creator of Aleph, is currently helping us build an engineering team in Factual’s Palo Alto office. Zach describes his seasoned, measured approach to using Clojure to conquer Factual’s complex engineering challenges:

“Yeah, I can hack that together this weekend.”

Of course, like every tool, Clojure is not a silver bullet and we don’t treat it as such. Our broader goal is to have a wide variety of tools in our toolbox, and carefully choose the best tool for each job. Boris Shimanovsky, Factual’s Director of Engineering, clarifies the subtlety here:

“Have you shipped yet?”

Fortunately for those of us who love us some parentheses (and who doesn’t (right?)), Clojure is often chosen as the right tool for a project. We’re now using Clojure and related tech throughout our stack, including:

  • Drake, our open-sourced “Make for data” tool

  • Various Machine Learning solutions

  • An internal API server on top of our entity data

  • An internal task management and resource queueing system

  • Ad hoc querying of data housed in HBase

We’ve also fielded Clojure-based libraries for using Factual’s public API:

We’re becoming more confident in when and where it’s most appropriate to apply Clojure as a solution, and we’re excited about the possibilities and potential gains. Boris elucidates:

“Sometimes, the Lisp weenies are right.”

Read More

Work with Us

If you’re an engineer and interested in helping Factual with hard stuff, check out our current openings.