The application process involved one telephonic code pairing round, followed by an onsite (virtual) interview.
The onsite interview consisted of:
A week later, the recruiter called and informed me, "There was nothing majorly negative feedback from the team, but you weren't quite there."
I've given many interviews and can almost always tell if I performed well. This time, I expected an offer based on my performance, but it went another way.
In retrospect, what did I do wrong?
In the first code pairing round, I completed three parts of the question: the first part was large, and the other two were smaller. In the second and third code pairing rounds, I only managed one part before I ran out of time.
In all three code pairing rounds, and in each part of the coding, they had their own test cases, all of which I passed. So, logic wasn't the problem; then what was?
I selected Golang as my programming language, and it's a bit more verbose than C# LINQ or Java lambdas, which consumed some of my time.
Therefore, I think to clear the coding rounds, one must complete at least three parts.
Even though you have the liberty to Google for syntax or other information, it eats up your precious time.
After spending seven hours in the process, I feel like I shouldn't have applied for the position. It has definitely hurt my confidence.
Other than the telephonic round, there were no data structure questions, which was surprising.
Telephonic:
Onsite:
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.