Producing lots of mediocre results that look good is the only way to succeed at EA. Just like their games
Producing lots of mediocre results that look good is the only way to succeed at EA. Just like their games
Easy to produce work good enough to keep your job.
Lack of promotion opportunities Resistant to effective change Superficial adherence to core values Excessive politics Rampant mediocrity Too many managers, few leaders
Focus on productivity. Understand value that cannot be measured. Seek the problems in plain sight and resolve them. Value passion for excellence over passion for games. Minimize waste and politics.
Was this helpful?
Electronic Arts Interview Questions
Electronic Arts Interview Experiences
Software Engineer
1. HR initial contact: Job presentation, salary, etc. 2. Manager meeting: Global team, architecture organization. 3. Online test: C++: LeetCode-like. 4. Team meeting: Formal and additional technical exercises. 5. HR offer during meeting.
Software Engineer
1. Phone call with HR 2. Wait for a week 3. Get response that put into pool 4. Follow up within the next few days 5. Still not get response 6. Maybe rejected
Software Engineer
Initially, I received a phone call for a background check and skill sets, shortly followed by an interview schedule. The interview was completely technical, related to CS concepts, and I had to code on a shared document. The interview lasted for 45 m
Software Engineer
October 1, 20221. HR initial contact: Job presentation, salary, etc. 2. Manager meeting: Global team, architecture organization. 3. Online test: C++: LeetCode-like. 4. Team meeting: Formal and additional technical exercises. 5. HR offer during meeting.
Software Engineer
October 3, 20241. Phone call with HR 2. Wait for a week 3. Get response that put into pool 4. Follow up within the next few days 5. Still not get response 6. Maybe rejected
Software Engineer
June 1, 2016Initially, I received a phone call for a background check and skill sets, shortly followed by an interview schedule. The interview was completely technical, related to CS concepts, and I had to code on a shared document. The interview lasted for 45 m
