The process began with a phone screen followed by a remote coding challenge. I felt I kind of botched that initial challenge, presenting a correct but overly complicated solution that I couldn't debug in time. I asked for a retry, which they granted, and I performed well on the second attempt.
The interview day was partly onsite, with the exception of two more remote coding challenges. These also went well, and I appreciated their generally well-structured approach, breaking the tasks into different, nicely paced parts. I valued their "pair programming" style during the interview, where they assisted with minor mistakes and helped me feel at ease. However, the extent of this support varied widely among the interviewers.
The remaining interviews included architecture whiteboarding and experience Q&A sessions.
Oddly, the company changed the position to a lead onsite role during my interview process without informing me. Ultimately, I did not receive an offer based on the leadership Q&A, despite excelling in the technical portions.
Dressed-up combinations/permutations question in a few stages.
The following metrics were computed from 2 interview experiences for the Block Senior Software Engineer role in Melbourne, Australia.
Block's interview process for their Senior Software Engineer roles in Melbourne, Australia is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Block's Senior Software Engineer interview process in Melbourne, Australia.