The initial call with the recruiter was straightforward, asking typical questions. Nothing special stood out.
Strangely, it took about two weeks to set up the coding assessment. However, the interviewer for the coding assessment was possibly the worst I've ever encountered. He was extremely rude and gruff, and didn't seem to want to be there at all. He had a very condescending attitude when I asked questions, making the experience quite unpleasant.
The assessment itself involved sharing a document. He wrote technical questions, and I typed out my responses. For some reason, instead of a coding sandbox, he had me write code directly in this document. The question was a decent medium-difficulty LeetCode problem.
Unsurprisingly, I received a rejection letter soon after. The interviewer was supposedly going to be my manager. In hindsight, I probably dodged a bullet with this one.
A handful of technical questions and situations to write out a response to.
Write a sorting algorithm.
The following metrics were computed from 296 interview experiences for the Yahoo Software Engineer role in United States.
Yahoo'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 Yahoo's Software Engineer interview process in United States.