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.
Phone screen and then a full day of interviews. There were: * 3 pair programming challenges * A system design review * A prior experience interview There was also an onsite lunch with a person from the company.
Phone screen, followed by a full day (~7 hour) onsite with a lunch break included. This mostly involved pair coding on a computer and some panel interviews, where interviewers talked with me and asked questions about topics related to the function I
The interview process includes a tech recruiter phone call, followed by three programming interviews, and then a system design interview. This is followed by meetings with team leads. The company is very transparent about the interview process from
Phone screen and then a full day of interviews. There were: * 3 pair programming challenges * A system design review * A prior experience interview There was also an onsite lunch with a person from the company.
Phone screen, followed by a full day (~7 hour) onsite with a lunch break included. This mostly involved pair coding on a computer and some panel interviews, where interviewers talked with me and asked questions about topics related to the function I
The interview process includes a tech recruiter phone call, followed by three programming interviews, and then a system design interview. This is followed by meetings with team leads. The company is very transparent about the interview process from