My technical phone screen with an engineer was as far as I got. It's intended to be a "pair programming" session, but I'll just say it didn't feel very collaborative.
The first layer of the interview was an LC easy/medium style problem. Once I got a working solution for that, the engineer added a second layer of complexity.
I described my approach, but he seemed resistant to it. He did not clearly articulate what the problem was, so I couldn't tell if he actually saw a flaw or was testing my ability to defend my decisions.
Either way, his pushback threw me off, and maybe that was enough for a rejection.
I tried to explore his reasons more to see if I should consider a different approach (trying to be collaborative), but perhaps this came off as indecisive.
I did not get any feedback on what I should do differently, and I couldn't think of anything on my own, so I decided to go with my idea. I ran out of time implementing it.
LC easy/medium, not too difficult.
The following metrics were computed from 158 interview experiences for the Block Software Engineer role in United States.
Block's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having good feelings for Block's Software Engineer interview process in United States.