Estée Lauder · Primly Community

Estée Lauder coding interview and online assessment, format and difficulty breakdown

hardware_hugo · 5 replies

so i finally finished this process and can report back. did the coding portion twice: the initial OA and then live coding in two separate rounds during the virtual onsite. here is literally everything i remember.

Online assessment (HackerRank, 90 minutes, 2 problems):

problem 1: string manipulation. something like counting valid substrings with certain character constraints. medium difficulty, maybe medium-easy. i finished it in about 25 minutes.

problem 2: this one was harder. a graph problem, BFS/DFS, finding shortest paths with weighted edges. i got a working solution but not optimal. the test cases were strict enough that partial credit mattered.

if you're aiming to pass the OA: medium LeetCode comfort is the bar. solve 50-60 mediums spread across arrays, strings, graphs, and dynamic programming and you'll be fine.

Live coding (CoderPad, during phone screen and onsite):

phone screen was one problem, standard medium, two-pointer approach, the interviewer was helpful when i got stuck. he asked me to walk through my thinking before coding, which made it feel less like a graded test and more like pair programming.

onsite coding rounds: two separate 45-minute sessions. problems were similar difficulty to the OA. one had a follow-up where he asked me to optimize my first solution from O(n^2) to O(n log n). that part got a little tense. the other round had a debugging exercise where they gave me broken code and asked me to find the issues. that was actually kind of fun, different from pure leetcode grinding.

what i noticed: they do not use the word 'optimize' in the same way FAANG does. they care that your solution works and that you can explain it. the debugging round especially felt like it was testing real-job skills more than pure algo knowledge.

overall: if you've been grinding for big tech and striking out, ELC could be a solid place to actually land. the bar is real but the process felt human.

5 replies

bootcamp_bri

the debugging round sounds like a relief honestly. i always feel like i'm at a disadvantage on pure algo questions vs. people who studied CS. but debugging is something i can actually do from real work.

newgrad_neil

did you have to use a specific language or could you pick? i'm most comfortable in python but some companies force java.

jp_newgrad

free choice on both OA and live rounds. i used python throughout with no issues. they seemed indifferent to language as long as you could reason through it.

market_realist

week 31 here and ELC just came up in my pipeline. this is useful context. is the HackerRank OA timed from the moment you open it or do they give you a window to start it?

jp_newgrad

they gave me a 5-day window to start it and then the 90-minute timer begins when you open the test. plenty of flexibility to pick a good time.