Taro Logo

Senior Software Engineer Interview Experience - Raleigh, North Carolina

February 1, 2020
Negative ExperienceNo Offer

Process

Initial phone interview with technical recruiter was very professional.

Follow-up video call, lasting about an hour with the hiring manager, was also very positive. They put the project in a positive light and discussed technical challenges.

Initial two interviews were relatively quick. It took about 3 weeks after that to set up interviews via video chat with their team.

Was given a schedule and an HR contact.

First interview was pretty standard, a mix of technical and informal discussion of experience. It lasted 45 minutes.

Second interview was different. I asked a question that followed on from something in the first interview. The interviewer spoke for about 40 minutes straight.

Third interviewer was just flat-out strange and unprofessional. Was a nice guy, but sat about 2" from the webcam. I could just see his eyes and nose; occasionally, I could see his mouth.

I asked him some questions about their project, and he told me that they only had one customer, that they didn't really have any use cases, and that they were being asked to refactor their solution in a way that would break it.

About halfway through this interview, I felt that joining this team wouldn't be a good idea as there was no commercial value to the project.

It was supposed to be a C development job, but the interviewer was asking about an odd Makefile he had created, with no C programming questions and nothing about the solution itself.

The third interview was odd. The interviewer gave off a pretty creepy vibe. He looked like he was sitting on his sofa in a robe and underwear. He asked a couple of questions. The interview was supposed to be about 45 minutes long. About 10 minutes in, I asked a question about customers. He dodged it and then told me that a fifth interviewer (not on the schedule) wanted to speak with me. He dropped off the interview, and the fifth interviewer didn't appear.

I waited about 25 minutes, then contacted their HR people.

About 15 minutes after that, they told me the last interviewer (not on the schedule) had a conflict (despite the fact that they interrupted the interview I was in to accommodate their schedule).

I spent the 40 minutes I was waiting to review their upstream commits to the kernel and threads on the kernel mailing list. I determined that this wasn't a project for me.

After being told by the HR person that the last interviewer could no longer make it, I dropped off the call.

I notified the HR person that I was no longer interested in the position based on the interview and the lack of customers.

Questions

They asked me about blocking and non-blocking locking methods.

Was this helpful?

Interview Statistics

The following metrics were computed from 5 interview experiences for the Red Hat Senior Software Engineer role in Raleigh, North Carolina.

Success Rate

20%
Pass Rate

Red Hat's interview process for their Senior Software Engineer roles in Raleigh, North Carolina is very selective, failing most engineers who go through it.

Experience Rating

Positive20%
Neutral40%
Negative40%

Candidates reported having negative feelings for Red Hat's Senior Software Engineer interview process in Raleigh, North Carolina.

Red Hat Work Experiences