L'Oréal · Primly Community

L'Oréal coding interview and online assessment: format, difficulty, and what I got asked

sre_sol · 4 replies

Applied for a software engineer role at L'Oréal (Paris-based team, but interviews were fully remote). Here's the coding side of things because I couldn't find anything specific before I started.

The online assessment (OA)

Delivered via HackerRank. 90 minutes, 2 coding problems. I did this back in February 2026. Problem 1: array manipulation, medium difficulty. Think sliding window or two-pointer. Nothing harder than Leetcode medium. Problem 2: OOP-flavored. Build a class hierarchy for something like a product catalog with inheritance. Less about algorithm cleverness, more about code structure and cleanliness.

Scoring seemed to weight correctness over efficiency. I had a suboptimal solution on the first problem but it passed all test cases and I still moved forward.

The live coding round in the onsite

This was the one I was more nervous about. One interviewer, shared coding environment (not HackerRank, more like a collaborative doc or CodePair equivalent). 50-60 minutes.

The problem I got: given a large catalog of cosmetics products with attributes (brand, category, price, ingredients), design and implement a filtering and sorting system. Start simple, then extend.

So it wasn't a traditional "reverse a linked list" interview. It was more like a software design exercise with code. I wrote actual classes, asked about requirements, made tradeoffs.

Level of difficulty

Honestly: comfortable Leetcode medium, plus solid OOP fundamentals. If you've been grinding Leetcode hard problems for FAANG, this will feel easy. If you're coming from a non-CS background with less algorithm drilling, do practice the standard data structures.

What they seemed to care about: can you write clean code, communicate your thought process, and handle extensions to the problem? Less about whether you can solve a graph problem in 12 minutes.

4 replies

hardware_hugo

90 minutes for 2 problems on HackerRank sounds totally reasonable. Did you have to use a specific language or was it open choice?

de_derek

Open choice. I used Python. The live coding round I also used Python and the interviewer was clearly comfortable reviewing it. I'd guess Java and JavaScript are also fine. Probably not something obscure.

sec_sasha

The OOP-flavored OA problem is interesting. I've seen that format more at enterprise software companies. Usually a signal they want engineers who think about maintainability, not just "did the output match." Good prep: practice designing small systems cleanly, not just algorithm puzzles.

careerveteran

The extending-the-problem pattern in live coding is a hiring signal I really like. Shows how someone handles scope creep, which is essentially the job. If you can't add a feature to your own code without breaking everything, that tells me a lot.