It pays well. There is still some cool tech around.
Some of the worst management in the game. Leadership has become completely obsessed with AI instead of building real products. The project code quality has rotted away completely. Increasingly, nobody knows how anything works.
Questions you ask anyone will often prompt a response generated by Claude, because there's less and less domain knowledge on the teams themselves. Management is using the number of PRs as the primary engineering performance metric, so the engineering team is churning out absolutely anything they can get merged to boost their personal performance metrics.
The engineering team feels driven entirely by the fear of being in the bottom ranks of management's AI-generated dashboards. You can't take a vacation without it hurting your output performance metrics, either, in my experience. Notable engineering leadership has left, leaving an uninspired talent base generating as much code as possible to save their jobs. This environment is simply no longer capable of inspiring the creativity and problem-solving it once had.
Stop creating poisoned incentives for the product and engineering teams by measuring metrics like code quantity and enforcing AI usage.
The interview process began with a recruiter phone screen, followed by a technical phone interview. Unfortunately, the interviewer was from a different team and seemed unaware of the role's requirements, which was discouraging. Additionally, the inte
Applied online. The first step was completing a coding challenge on HackerRank. Next was a one-hour phone screen. The interviewer seemed genuinely interested in my past projects. We spent the first 10 minutes talking about current and past projects.
My first contact was with a recruiter. He was a bit disorganized, missing our first phone call due to meeting schedules – a sign of how busy things are at Square. After some chitchat, he scheduled a Skype interview with an engineer. The Skype interv
The interview process began with a recruiter phone screen, followed by a technical phone interview. Unfortunately, the interviewer was from a different team and seemed unaware of the role's requirements, which was discouraging. Additionally, the inte
Applied online. The first step was completing a coding challenge on HackerRank. Next was a one-hour phone screen. The interviewer seemed genuinely interested in my past projects. We spent the first 10 minutes talking about current and past projects.
My first contact was with a recruiter. He was a bit disorganized, missing our first phone call due to meeting schedules – a sign of how busy things are at Square. After some chitchat, he scheduled a Skype interview with an engineer. The Skype interv