3 ms·
Smarkets | Full Time | ONSITE (London, UK; also Downtown LA, California) We're a modern betting exchange, going technology first to enable proper price competi
by bostik 8y ago
Smarkets | Full Time | ONSITE (London, UK; also Downtown LA, California)
We're a modern betting exchange, going technology first to enable proper price competition in a field of fat commissions. Join a small, agile, and fast-growing team, in our beautiful office in St. Katharine Docks. If our US location tickles your fancy, you get to help setting up a brand new office too.
Smarkets develops a reliable, low-latency, highly concurrent betting exchange based on trading exchange designs. We're also building a fast, modern web interface to allow for a smoother experience. Servicing our users is top priority.
The Smarkets platform is written predominantly in Python, Erlang (being replaced with C++) and Javascript for React, relying heavily on asynchronous programming techniques. The tech stack sports Kafka, Postgres and increasingly Kubernetes. We use REST where we can. Life at Smarkets circles around people, version control, configuration management and automation. We can - and do - deploy to production several times a day.
Our entire production is in AWS. In fact, Smarkets was the first gambling operator under the Maltese regulator to get permission to run everything in the cloud. We push the envelope where needed and educate auditors when necessary.
We are looking for engineering talent in the following roles:
* [Senior] Front-end Engineer - React; London & LA
* Data Engineer; London
* Infrastructure Engineer; London
* Senior Security Engineer; London
* Quantitative Developer; London
* Low-Latency C++ Engineer; London
* Generalist Software Engineer; London & LA
* [Senior] Mobile Developer; LA
If you like the idea of flat structure and practical engineering approach, see our jobs at https://smarkets.com/careers https://smarkets.com/careers .
- elechi 8y agoMay I ask why the move from Erlang to C++?
- paulgrant999 8y agoSeconded. :)
- bostik 8y agoSomeone else asked this maybe a year ago. I've been prodding our exchange team to write a proper post about it but they have been ... busy. The move is also still in progress. But a short version is pretty simple: lack of available talent, unsuitable memory model, performance. Erlang's shared-nothing model is great for concurrency; it does not work well when dealing with data structures that are subject to invasive operations. (Limit order book sees very rapid modifications.) I'll have to nudge our exchange team again about the writeup. Maybe we'll have it at some point.