We built something a bit novel that is focused on composable integration testing in Clojure. We've used this for many years and found it quite useful for keeping a large testing codebase sane.
Amperity is hiring a variety of technical roles: Engineering Manager, Applied Data Scientist (Lead), Senior Software Engineer.
Interesting problems: - Ingesting and cleaning massive amounts of data daily and blending it with real-time events - Automatically stitching data together across disparate systems by training machine-learning models to build a probabilistic knowledge graph - Taking research algorithms and productionizing them for high-scale usage - Allowing users to perform complex, real-time queries across an aggregated view of their data - Publishing query result data to a diverse set of systems for client usage.
For a full listing of positions, see https://amperity.com/careers/ -- apply there or reach out to me directly with questions. [my hackernews userid] at amperity dot com.
Engineers! Amperity is hiring SDE's across all levels.
Interesting problems:
- Ingesting and cleaning large amounts of data daily and blending it with real-time events
- Automatically stitching data together across disparate systems by training machine-learning models to build a probabilistic knowledge graph
- Taking research algorithms and productionizing them for high-scale usage
- Allowing users to perform complex, real-time queries across an aggregated view of their data
- Publishing query result data to a diverse set of systems for client usage
Tech stack:
- Clojure/Clojurescript
- Aurora/Mesos
- Accumulo/Hadoop
- Spark
- Kafka
- SaltStack/Terraform
- Riemann/InfluxDB/Grafana
For a full listing of positions, see https://amperity.com/careers/ -- apply there or reach out to me directly with questions. My email prefix matches my HN handle.
That has always annoyed me as well, though in fairness the two times they caught a discrepancy at the exit it was in my favor (forgot an item at the checkout in one case, double charged in the other).
Amperity | Seattle, WA | ONSITE & REMOTE | Full-time
Amperity is a startup company founded in January 2016 to tackle the problem of customer data unification at scale.
We are hiring experienced engineers to write Clojure (and ClojureScript for the front end inclined) in Seattle, WA. Remote is an option as well for the right candidate.
This is an early stage opportunity at an ambitious, well funded startup company. Full stack Clojure, not "a bit of Clojure on the side". You'll write Clojure all day, solve difficult problems at very large scale, and get paid.
Background in large scale data processing, distributed systems, and machine learning are all major bonuses. Other elements of the stack include Mesos, Apache Aurora, Finagle, Spark, Kafka, Accumulo, Onyx, SaltStack, and Riemann.
For a full listing of positions, see http://jobs.amperity.com -- apply there or reach out to me directly with questions. My email prefix matches my HN handle.
I applied at Amperity, went in and did a day of interviews. After that I was told they decided to go with another candidate. Now I see them still hiring everywhere. Was it the polite brush off? Are they actually hiring? Would they get annoyed if I applied again?
I emailed Derek to ask what is going on, and his response indicated that they are not actually hiring, and just checking to see if any one in a million candidates reply to their job postings.
So I give interviewing with Amperity an F and suggest anyone who can interview elsewhere do so and skip them.
(Also, "remote for the right candidate" really means "no remote")
Overview: https://eng.amperity.com/posts/2019/04/greenlight GitHub: https://github.com/amperity/greenlight