Food is pretty good.
There are definitely some very talented engineers.
In several ways, engineering practices are top-notch.
Work/life balance is good.
Office politics are extremely pervasive at Square. I've known coworkers fired over personal disagreements. If you don't drink the Kool-Aid, you're gone.
Management refuses to admit mistakes. The communications team seems to focus on placating employees, not telling an inspiring narrative to the rest of the world.
Generally, projects move at a glacial pace unless management happens to fancy your project this quarter. The next quarter, your headcount could be gone. I saw projects take two years that should have taken 3-6 months.
Compensation is unimpressive. I think there's more of an effort recently to improve it, but for many employees, like myself, it's too little too late.
For as many great engineers as there are, there are equally as many really poor engineers. Square grew far too quickly, and its talent suffered as a result. In general, engineering makes little investment in the future. Technical debt is extremely high with no plan on how to pay it down.
Admit your mistakes. Accept feedback, own it, and honestly work to improve. You don't need to be infallible, but if you refuse to recognize your mistakes, you'll alienate all of your employees.
I applied online, and the recruiter contacted me a little afterward for a quick phone screen. I then had the technical phone screen the following week, which was surprisingly pretty manageable – a really basic question. The interviewer was actually
Onsite interview. The workstation wasn't set up, and we spent 10-15 minutes trying to find and set up a new one. We then switched back to the original one when it didn't work. This was problematic because I was only 5 minutes from finishing my code a
I applied through a recruiter, who was extremely responsive and professional. A quick phone screen was followed by a technical Skype interview, then an onsite interview. The onsite interview consisted of: * Three pair programming interviews * On
I applied online, and the recruiter contacted me a little afterward for a quick phone screen. I then had the technical phone screen the following week, which was surprisingly pretty manageable – a really basic question. The interviewer was actually
Onsite interview. The workstation wasn't set up, and we spent 10-15 minutes trying to find and set up a new one. We then switched back to the original one when it didn't work. This was problematic because I was only 5 minutes from finishing my code a
I applied through a recruiter, who was extremely responsive and professional. A quick phone screen was followed by a technical Skype interview, then an onsite interview. The onsite interview consisted of: * Three pair programming interviews * On