Real, anonymous reports from people who interviewed for Software Engineer at Yahoo, newest first and distilled into what to expect across the loop.
My process started with an HR discussion that was supposed to happen within a few days, but nothing happened when it was scheduled. After waiting about two weeks, I was asked for another quick screening round scheduled very late, and I joined while working across time zones.
I started with a recruiter screening call, then I moved into a hiring manager interview where the focus was a mix of background and alignment with the role. After that, the process pivoted into a frontend-style technical assessment where I had to work through a problem in a CoderPad-style environment. I remember the vibe being structured and pretty normal—no weird surprises in the format, just a clear progression from conversation to coding.
The interview process typically begins with a recruiter screening, followed by a mix of technical and behavioral interviews, often culminating in multiple rounds that can include coding assessments and system design discussions. Candidates noted a range of experiences from structured and smooth to chaotic and poorly coordinated.
Candidates faced a variety of technical evaluations, including coding challenges, DSA problems, and system design questions, with some processes emphasizing practical problem-solving and others focusing on theoretical knowledge. The technical rounds often required clear communication of thought processes.
Behavioral interviews were a significant component, assessing candidates' collaboration skills and cultural fit within teams, often through situational questions and discussions about past experiences. The tone and engagement level of interviewers varied, impacting candidates' perceptions of the process.
Many candidates reported issues with communication throughout the process, including delays in scheduling, lack of timely feedback, and unclear next steps, which contributed to a frustrating experience despite the interviews themselves being well-structured.
Some candidates encountered take-home technical exercises that varied in complexity and format, with experiences ranging from straightforward bug fixes to multi-question problem sets. The reliance on these assessments made the process feel high-stakes, especially when follow-up communication was lacking.
The overall difficulty of the interviews was noted as high, with some candidates feeling intense pressure due to the breadth of topics covered and the high expectations set by interviewers. This pressure often affected candidates' performance and their overall experience.