ODDITY is a a tech company that builds brands from the ground up specifically for online audiences - no legacy retail baggage, basically trying to shake up an industry that's been stuck in the mall-store model forever. The company serves approximately 68 million users through its AI-powered online platform, they dig into user data to figure out what people actually want, then build products around that. ODDITY owns the brands IL MAKIAGE, SpoiledChild, and METHODIQ. The company is headquartered in New York and also has a research and development center in Tel Aviv, Israel, and a biotechnology laboratory in Boston.
As a Team Lead and JavaScript Developer at ODDITY, I focused on building web solutions and backend services. I worked with Node.js, JavaScript/TypeScript, and Angular (versions 9 through 14), even dabbling in Web Components. My role involved supporting digital consumer products and business operations from a technical standpoint.
A big part of my job was taking requirements from the Product Owner and turning them into new features. This meant doing the technical analysis, figuring out the best way to build it, creating prototypes, and seeing if it was even possible to build.
I also spent a lot of time developing and maintaining the backend services and frontend apps that handled user data. This involved processing, transforming, and calculating data according to the business rules and any analytical algorithms we had. Part of that was creating and maintaining the logic for transforming data so it could be used by APIs and other systems.
When things went wrong in production, I was the one digging in to find the root cause and fix the issues, whether they were in the backend or the frontend. I also managed the releases for quite a few projects – eight backend ones, including some serverless stuff, and one frontend project. The goal was always to make sure the deployments were smooth and coordinated.
I also developed and maintained algorithms specifically for transforming and preparing user data into the formats needed for later steps and integration.
Leading a small, cross-functional team was also on my plate. This included developers, QA engineers, and project managers. I made sure everyone was on the same page about what we were working on and in what order.
Collaboration was key. I worked with different engineering and business teams to connect solutions across various products, systems, and data flows. To make sure we weren't wasting time on ideas that wouldn't pan out, I created quick prototypes to test their feasibility and value before diving into full development.
On top of all that, I did code reviews, helped new team members get up to speed, coordinated project development, and contributed to designing the overall software architecture and technical approaches.
This kind of work directly relates to ad tech. Developing data-driven digital products, handling user data, working with algorithms, integrating APIs, building analytical systems, and automating processes are all things ad tech platforms deal with constantly. I also gained a good understanding of how user behavior and data are turned into insights that can be acted upon. This is super relevant for things like audience targeting, tracking conversions, analyzing ad campaigns, attribution, and creating automated ad solutions.