Taro Logo

Software Engineer Interview Experience

February 1, 2015
Negative ExperienceNo Offer

Process

I applied online and received an email from the first interviewer after two to three weeks. There were two rounds of technical interviews before the final decision.

The first interviewer was very nice and told me he was impressed. The interview included three algorithm and data structure questions, two questions about my resume projects, and one question about a course. Ironically, he suggested I not accept their offer if I had other choices.

The second interviewer, however, provided me with the most horrible interview experience. As a front-end developer, he believed it was very important to know Unix scripts and computer networks, even though I was interviewing for a machine learning position.

He kept asking me questions like which directory holds logs in Unix, the names of each layer of the OSI model, and the names of each stage in Agile. He asked 16 such questions in total within 45 minutes, in addition to two programming questions and one algorithm question. He asked me to write down scenarios and interrupted me when I wrote some pseudocode.

Neither of us are native speakers, so I suspect we had communication problems. He kept saying, "Just write it down," when I was trying to briefly describe an idea or walk him through code.

My recruiter never replied to emails, so I don't know if I received an offer. The process was just stuck, and I happily accepted an offer from another company.

Questions

The first interviewer was very nice, and we are still in touch. The interview included:

  • 3 algorithm and data structure questions
  • 2 questions about my projects on my resume
  • 1 question on a course

The second interviewer impressed me with the most horrible interview experience. As a front-end developer, he believed it was very important to know Unix scripts and computer networks, though I was supposed to interview for a machine learning position.

He kept asking me questions like which directory holds logs in Unix, the names of each layer of the OSI model, and the names of each stage in Agile. He asked 16 such questions in total within 45 minutes. Additionally, there were 2 programming questions and 1 algorithm question (he asked me to write down scenarios and interrupted me when I wrote some pseudocode...).

Was this helpful?

Interview Statistics

The following metrics were computed from 296 interview experiences for the Yahoo Software Engineer role in United States.

Success Rate

22%
Pass Rate

Yahoo's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.

Experience Rating

Positive43%
Neutral36%
Negative20%

Candidates reported having good feelings for Yahoo's Software Engineer interview process in United States.

Yahoo Work Experiences