Taro Logo

Software Engineer Interview Experience

March 1, 2017
Negative ExperienceNo Offer

Process

Five stage interviews: two with recruiters and three with technical senior engineers and managers.

The first two were behavioral, with light technical questions and a culture fit assessment.

The third interview consisted of more behavioral questions, but also a little more in-depth technical questions and a panel.

The rest were more technical, but not what was expected.

All interviews went perfectly except the last one. I was asked a C question for a C++ position, which threw me off, but I remembered at the end of the interview.

I had a lot of experience in C++, but they only asked me two simple questions. I got one right and the other half right, the C.

It wasn't a fair assessment of my skills, but what are you going to do?

I think the last two interviews weren't good.

I got feedback from the recruiters, and it didn't make any sense. They said I had good experience with Action Script, and in fact, I don't.

I thought I would make the cut, but I don't know what happened.

Maybe some sort of mix-up, which was very disappointing.

But my impression was that the onsite interview would have been an intense, all-day C++ problem-solving session with game math, such as matrices, etc., typical stuff.

Questions

What’s the difference between new vs. malloc?

Was this helpful?

Interview Statistics

The following metrics were computed from 104 interview experiences for the Electronic Arts Software Engineer role.

Success Rate

40%
Pass Rate

Electronic Arts's interview process for their Software Engineer roles is fairly selective, failing a large portion of engineers who go through it.

Experience Rating

Positive57%
Neutral25%
Negative18%

Candidates reported having very good feelings for Electronic Arts's Software Engineer interview process.

Electronic Arts Work Experiences