AppLovin is performing very well relative to its competitors. It's good to be on a winning team.
The headquarters office in Palo Alto is very nice. Some of the best corporate food I've ever had.
They hate time-wasting group meetings. This was one of my favorite aspects of AppLovin culture.
Things tend to move fast. Stuff gets done.
The stock has gone bonkers in recent months. So that's been great for those who were able to participate. But of course there's no guarantee that will continue.
Lots of layoffs and firings, creating a constant atmosphere of fear.
Disdain for any "soft skills" to an almost absurd extent. Performance management was amateur hour and laughably bad. For example, my boss got an important promotion. I didn't hear about it from anyone in the company, not even a Slack message. I found out about it when LinkedIn notified me. Another example: I was given significant additional responsibilities and then, a few weeks later, I was unceremoniously terminated. Very mixed messages.
Specializations (engineering, sales, product management) seemed very "siloed" with bad communication and low trust. I understand an engineering organization should emphasize technical skills.
Release processes seemed awfully casual for a company of AppLovin's size, with lots of rollbacks, hotfixes, and patch releases. There seemed to be a disdain for process. Some of that can be healthy, but you need some structure when operating at AppLovin's scale.
Multiple reports of toxic culture from various parts of the company. My experience backs this up.
AppLovin isn't a startup anymore. You need a real performance review system. It doesn't have to be hugely cumbersome and take a lot of time, but it should be clear, concise, and set expectations.
You can get away with treating engineers badly during times like these when there are a lot of layoffs. But if things change, people might be more willing to leave.
The interview process begins with a behavioral round with HR. Following that, you'll complete a take-home assessment using Unity and C#. If you pass the take-home assessment, there are four more interview rounds: 1. A technical interview with oth
45 minutes HR, followed by 1 tech interview. I did not pass the first tech interview and was rejected directly afterwards. HR mentioned that there would have been 3 more rounds afterwards.
I got in through a recruiter at my university. I had a behavioral interview with them that was quite pleasant, but then I had a technical round with a poor experience. It seemed like the interviewer didn't want to be there either during the technic
The interview process begins with a behavioral round with HR. Following that, you'll complete a take-home assessment using Unity and C#. If you pass the take-home assessment, there are four more interview rounds: 1. A technical interview with oth
45 minutes HR, followed by 1 tech interview. I did not pass the first tech interview and was rejected directly afterwards. HR mentioned that there would have been 3 more rounds afterwards.
I got in through a recruiter at my university. I had a behavioral interview with them that was quite pleasant, but then I had a technical round with a poor experience. It seemed like the interviewer didn't want to be there either during the technic