AppLovin·Software Engineer·Technical Phone Screen
- Design a job scheduler, structured as a variant of the LRU (Least Recently Used) cache problem.
“LRU is something I'd seen before but the job scheduler spin on it threw me a bit.”
Large Enterprises
Screna has 12 AppLovin interview write-ups. The most reported round is the technical phone screen (8).
12 interview notes · updated Jul 2026
“LRU is something I'd seen before but the job scheduler spin on it threw me a bit.”
“I ran through the usual stuff: resampling, adjusting class weights, threshold tuning, picking the right metrics.”
“This one is deceptively wide.”
“This one took me a minute to internalize.”
“Classic video storage question but I still fumbled the sequencing a bit.”
“This one stung a bit.”
“Got through the core solution fine.”
“My first instinct was to just do the standard recursive validation with a low/high range per node, which is right, but I kept wanting to return a boolean and had to mentally reset.”
“The base problem wasn't too bad but the no-extra-space constraint is what got me.”
“My first instinct was to just return a boolean and I had to stop myself.”