Block is exciting in that it's constantly trying to drive innovation. Most folks are kind, generous, and empathetic. The products are usually a good market fit. And if you like working in AI, the work here is pretty interesting.
Sometimes the search for innovation gets in the way of doing good, solid work. Not every project needs to be about AI, and we probably don't need to actually monitor folks' AI usage.
Due to layoffs, movement within the company is difficult. Many teams are "stacked" with senior & staff level engineers, so even getting a promotion is difficult, both because of the opportunities and because of budget constraints.
Hold your middle managers to a higher standard; getting rid of the Pulse survey was a mistake.
There's little opportunity to give constructive, anonymous feedback to managers, and retaliation is a thing (even if you want to pretend it's not).
3 rounds of technical interviews; some were closer to LC mediums, and others were more class implementation focused. Follow-ups were also pretty standard and asked about time/space complexity. For my internship cycle, you had to pass all 3 techs (a p
Pretty standard; basic, easy-to-medium LeetCode-style questions. There were three rounds of 45-minute technical interviews. Follow-ups regarded time and space complexity, but they were not too difficult. Standard LeetCode preparation should be eno
There were three pair interviews with engineers from Block. Each round was pretty much the same difficulty. I think they were more focused on how you communicated about what you wrote, along with a correct implementation.
3 rounds of technical interviews; some were closer to LC mediums, and others were more class implementation focused. Follow-ups were also pretty standard and asked about time/space complexity. For my internship cycle, you had to pass all 3 techs (a p
Pretty standard; basic, easy-to-medium LeetCode-style questions. There were three rounds of 45-minute technical interviews. Follow-ups regarded time and space complexity, but they were not too difficult. Standard LeetCode preparation should be eno
There were three pair interviews with engineers from Block. Each round was pretty much the same difficulty. I think they were more focused on how you communicated about what you wrote, along with a correct implementation.