Rippling

• Fair compensation
• Some teams are better than others

Oh boy. The main issue is that any processes that teams try to build get sabotaged by upper management, which decides to escalate an unplanned feature out of nowhere.

That feature is being rushed, and the CEO asks "are we there yet" every day, putting so much pressure that teams just give up on any and all code quality.

This inadvertently breaks other things, which makes the CEO angry, and now the team is under fire for breaking things and is rushed to fix them ASAP. The cycle described above repeats itself every sprint.

Some teams are literally trying to finish their Q2 tasks in Q4 because of constant injection of work out of nowhere.

Then the code quality. Jesus Christ.

With the process described above, you can probably imagine what a tangled mess this all produces.

And then every initiative to refactor and fix it is killed in its infancy because, again, out of nowhere, you get a P0 priority feature that clients apparently need yesterday.

Literally, any technology gets approved, because when a team comes to you with a "CEO needs this feature yesterday, for it we need to use XXX, do you approve?" - the answer is always yes, because there's no time to even think about investigating anything else.

Anyway, if you are one of those people that "strive in a chaotic environment" - this place is for you. You will get complete chaos everywhere, every day.

Think about new features in advance. Do not expect the teams to bend backward every time you decide that something is super important.