Taro Logo

Full Stack Engineer Interview Experience

April 1, 2020
Positive ExperienceNo Offer

Process

The interview process included:

  • A short phone screen with the recruiter.
  • A technical phone interview with an engineer.
  • Three one-hour interviews with three additional engineers.

The recruiter conducted a couple of "prep" interviews to inform me about what to expect. I received a rejection two days later, so they move quickly.

Questions

The technical phone screen consisted of generic programming questions, such as:

  • What is a closure?
  • What is an abstract class?
  • When would you use an interface?
  • When would you use a state management framework like Redux?

He also asked generic questions about my background.

Return an array of all palindrome permutations of a given string.

Given a binary tree "main" and another binary tree "sub," determine if "sub" is a sub-tree of "main."

Write a JS function to fade out an alert. How would you hide that alert on future page loads?

Various JavaScript trivia questions:

  • Understand how the event loop works.
  • "What order will these console.log statements print?"
  • Understand how objects are assigned/copied.
  • "If a = {c: 1}, and b = a, what will a == b evaluate to?"
  • "If an object is copied using the spread operator, and one of the values is an object, how is that copied?"
  • Convert a time stamp difference into a human-readable format (e.g., "now," "a few seconds ago," "a few days ago").

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the AppLovin Full Stack Engineer role in United States.

Success Rate

0%
Pass Rate

AppLovin's interview process for their Full Stack Engineer roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive100%
Neutral0%
Negative0%

Candidates reported having very good feelings for AppLovin's Full Stack Engineer interview process in United States.

AppLovin Work Experiences