My process was a little weird, since I was redirected from another process that also took place with Electronic Arts (for a .NET Software Engineer - Full Stack role that didn't turn out).
Regarding the ASE role, since I had already been contacted in an initial call with RRHH for the previous process, I didn't have that step and directly had an initial talk with the Technical Director and two members of the team. A couple of days later, I was contacted again in order to have a technical interview the next week, with the same members of the team.
The technical test went pretty well, so that same afternoon they sent me an email asking if I had other offers on the table.
In another couple of days, I had a short talk with RRHH during which they made me an offer. At the end of that same week, I had a Zoom meeting where we reviewed the offer details, and as a final (and a little stressful) stage, they asked me to submit five references from people who had worked with me in the past, as a final requirement to be able to sign the offer and proceed with the hiring process.
In the initial interview, they asked me behavioral questions (what would I do if asked to work overtime, or if a superior told me that the code I was trying to submit wasn't good enough), and also scarce technical questions (what is a stack overflow, the difference between a virtual and an abstract class, and the main difference between C++ and C#).
The technical interview consisted of fixing localization bugs present in code they shared at that moment.
The following metrics were computed from 5 interview experiences for the Electronic Arts Associate Software Engineer role.
Electronic Arts's interview process for their Associate Software Engineer roles is on the easier side as most engineers get an offer after going through it.
Candidates reported having very good feelings for Electronic Arts's Associate Software Engineer interview process.