L'Oréal · Primly Community

L'Oréal software engineer interview process, full loop: what actually happened

remote_swe_42 · 4 replies

Went through L'Oréal's full software engineer interview process earlier this year for a role on their CDO (Chief Digital Officer) org. Sharing the breakdown because there's basically nothing on this online and I wasted a week trying to find info.

Total timeline: applied end of January, offer in hand March 3. About 5.5 weeks, which is faster than I expected from a large CPG.

Round 1: Recruiter screen (30 min) Standard background questions. Why L'Oréal. Comp expectations. They do ask early so have a number ready. Recruiter was well-prepared and clearly knew the tech org.

Round 2: Technical phone screen (1 hour) With a senior engineer. One medium-difficulty coding problem on a shared editor (HackerRank-style, but live not async). Mine was a string manipulation/sliding window problem. Nothing wild. Also about 20 min of system design-lite: "walk me through how you'd build a product recommendation feature."

Round 3: Technical onsite (3.5 hours, done over two days remote) Two coding interviews. One was a graph traversal, one was more OOP design-heavy (model a shopping cart, then extend it) One system design: design a scalable image transformation service for beauty product photos One behavioral panel with two interviewers

Round 4: Hiring manager conversation (45 min) More of a vibe check and org context. They describe the team, you ask questions, they're basically sold if you got here.

Difficulty felt like mid-tier tech company, not FAANG. Leetcode medium comfortable should cover the coding. System design was more product-flavored than infra-heavy, which makes sense given it's CPG not a cloud infra company.

Happy to answer questions about any specific round.

4 replies

pivot_pat

This is so helpful, thank you. Did they ask anything specific about CPG or beauty industry experience, or was it mostly generic software skills? I have zero CPG background and I'm worried that's a dealbreaker.

qa_quinn

Genuinely not an issue for the engineering role. They care that you can build things. One interviewer mentioned they hire heavily from tech companies specifically because they want product/engineering best practices brought in. The CPG knowledge you'll pick up on the job. Don't overthink it.

visa_vik

Did they ask about visa status during the recruiter screen? I'm on an H1B and trying to figure out if it's worth applying before I know they'll sponsor.

staff_steph

The product-flavored system design makes sense. Most CPG companies don't need you to design Kafka clusters, they need you to think about how products actually get built and shipped. If you can do the FAANG circuit, this is going to feel pretty reasonable.