The tech team at Lucky cart is made up of Backend, Frontend, Full Stack engineers as well as DevOps and QA Engineers. Our goal is to create innovative solutions to improve the shopping experience of millions of buyers. We define a quarterly roadmap in line with Lucky Cart's OKRs and seek to continuously improve our users' satisfaction. Performance is at the heart of our team and we strive for continuous individual and collective improvement.
Technologies and tools
MERN Stack ⚙️
We mainly use React on the front end, NodeJS and express on the back end, with MongoDB as our database. We use a lot of TypeScript, but we also have a big legacy in pure JS.
We process 10,000,000 shopper events per day in real time to personalise their shopping experiences.
Google Cloud Platform ⚙️
We use the full power of GCP (BigTable, BigQuery, PubSub, CloudRun, Kubernetes Engine) to build a stable and scalable architecture with 99.99% availability.
Organization and methodologies
We are organised into 3 impact teams, each composed of a Product Manager, developers (Backend, Frontend and Full Stack), a DevOps, a QA Engineer and led by an Engineering Manager. These impact teams have measurable objectives taken directly from Lucky Cart's OKRs. Each team works in an agile methodology, with the desire to deliver value to customers quickly and to improve continuously. We use Jira as a ticketing tool and BitBucket as CI/CD.
Projects and tech challenges
The Lucky cart product is separated into two parts:
A platform to manage in a few clicks hundreds of campaigns in parallel on several e- commerce sites and applications, to track shoppers, distribute earnings and analyze campaign performance.
An engine that transforms millions of shopper events (browsing, clicks, shopping cart, payment, ...) into personalized interaction (display of banners, product recommendations, triggering of a game), all in real time. Lucky cart's main challenges are the volume of data processed, in terms of both the number of requests and the volume of data, with strong security issues.
Step 1: Technical test and debrief with two developers
Step 2: Interview with Vincent our CTO
Step 3: Interview with Bouzhiane, Co-founder COO
Step 4: Meeting with Romain our CEO