People are always very nice, friendly, and helpful. As an engineer, I have a great work-life balance.
When it comes to delivering on new features, Square's tooling is a bit esoteric but usually gets the job done with minimal waiting. When it doesn't, the nice, friendly, and helpful people I just mentioned will unblock you really fast.
C-Suite leadership makes bizarre decisions (e.g., renaming to Block) that somehow promise to make them a lot of money, but don't contribute towards better products for users (e.g., Jack's obsession with crypto).
There's a mixture of new and pleasant technology, and old legacy stuff that has to continue to be supported. This would not be so bad, except there is a surprising amount of resistance if you decide not to build new things with the old legacy technology.
"Software architecture" isn't a priority for Block's microservices. So, while everything works and individual services have unit tests, creating usable APIs for cross-team boundaries is usually an afterthought that makes it a pain to ever make new connections.
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