Pros: - Jack is a solid dude. - Good company values. - Good benefits. - Co-workers are generally friendly and helpful.

Cons: - Onboarding really, really sucks. - Nobody really knows anything, and people are just blindly following processes. - Write docs for days, weeks, or months, with no time actually spent writing code. - If you like technology and building things with code, you'll be stuck in a quagmire of documentation, reviews, complicated legacy code nobody dares touch, and robotic processes. - Nobody has figured out how to build team morale remotely, which is a problem given Square wants to become a fully remote company.

Pros: Overall, there was a good work-life balance.

Cons: There was boring tech and a lack of motivation from employees. You will probably get laid off.

Pros: As a developer specifically, [they have a] great engineering culture. They actually care about things like testing their code, which many startups only give lip service to. Still has a startup-like atmosphere for a pretty old company. Some nice fringe benefits: health/dental/vision 100% covered, lots of cheap-to-free food.

Cons: Low salaries for a public company. Equity compensation for me was equal to about 1 year's salary but vesting over 4 years. Even including the 25% premium, it’s still low for the SF Bay Area. Required engineers to be on-call, at least on my team, but did not properly compensate. I have never worked anywhere that required engineers to be on-call unless it was shortly after a launch. Maybe they would be expected to fix their code if it failed catastrophically, but not like this. Has only half a CEO. In an extremely low-margin, competitive business with no solid plan for turning a profit. It’s the worst-kept secret of both Square and Twitter. Everyone seems to know it except him and the respective boards. Jack needs to try with one, or he will fail with both in my opinion.