Pros: Fully remote and confident they will not revert that policy. Nice social events and free snacks in the office.

Cons: On-call is absolutely horrible. In your on-call week, you will get pages at 2-3 AM and at midnight, and you're expected to ASAP get up and fix it. This wouldn't be too bad if the code wasn't a horrible mess, and incidents and pages happen at least 4 times a day (mostly at midnight or outside work hours). The compensation for pages is just that any time worked outside hours, you can redeem back in work hours, i.e., one hour outside work, one hour back in work. This is NOT equivalent and is a terrible deal compared to other companies in the industry that give generous compensation for on-call (and they probably rarely have midnight pages, if at all, from what I've researched). There is no technical growth. It is simple fixing the code and rarely product features. It feels more like a support engineer role than a software engineer role. Salary is not market standard. Stock doesn't rise, so no point in RSU; better to just get far more money. In the UK, there are fewer other jobs with skills that Yelp uses. No career progression. Don't fall for their promises of their leveling framework; it is simply to keep paying you less for as long as they can. Terrible business practices. Ask any person who opens a business at Yelp; very, very bad PR, and I don't see this company surviving the next few years.

Pros: Considerate and diverse culture. Projects can be interesting depending on the teams. It’s a good company to deliver impact as a full stack engineer.

Cons: The product is less used outside of the US, so if you’re not in the US, there might be a disconnect you could feel with the users.

Pros: Yelp has set up best practices and an engineering culture. No blame policy.

Cons: Conservative approach to product design Systems and methods are always in flux (how to use product management tools, seating arrangements, etc.).