Reelevant is a SaaS that allows marketing teams to generate on-demand marketing contents (mostly inside their email) while taking into account all of their data available for each individual user.
To do that we have 4 different products:
Datahub that connects to their data (databases, API, 3rd party etc) and synchronize them inside Reelevant
Contents that allows them to design template of what they will show to their users
Workflows that, for a given user that requests marketing content, fetch data depending on the marketer configuration and display exactly what they want
Statistics that aggregate all results and performances in terms of display/clicks
Each marketing content is computed in real-time which is the hardest constraint of our product, everything from the database to the content rendering needs to happen in less than 1 second.
Job
We are looking for someone to join our small (but mighty) team of 2 engineers (both 42 Paris) to continue building and improving the core of our products and our infrastructure. Mission includes:
Continuously refactor/improve our backend’s code to meet scale demand
Implement new features
Continuously improve our infrastructure setup
Stack
Almost all of our stack is in Typescript and we use React 18 for the frontend side.
We refactored the content rendering part in Rust in 2023, which used a library for the typescript backend.
Heavy usage of Apache Pinot (a specific database designed for huge datasets)
Our own infrastructure deployed with Ansible on OVH (almost no cloud here)
We are not looking especially for people with experience with our stack (since it’s really specific), you can learn on the go as we did. However, we want to find somebody that aligns with our values:
Excellence: means that no matter how difficult or long a project is, you’ve literally given it everything you’ve got.
Grit: effort count twice
Autonomy: look for answers even if that means reading code in a language that you don’t know
Ambition: what we do is hard so aim high to still be excellent
Some examples would be our content engine that initially used a WebAssembly build of a lib which isn’t performant enough so we got a level deeper and rewrote it in Rust (without any prior experience with Rust) with binding to the lib c++ code.
Or that our database (Pinot) didn’t work as intended so we forked it to update it for our use case (in Java).
We migrated from GCP managed environment to OVH where we rent our bare metal servers and manage everything ourselves.
Rencontrez Maxence, Solution Engineer
Rencontrez Valentin, Directeur technique
Ces entreprises recrutent aussi au poste de “Développement de logiciels et de sites Web”.