hot  /  reviews  /  video  /  blogs  /  forum

EA blows off layoff reports following BF3, SWTOR letdowns

Apr 16 // Jim Sterling
   @JimSterling

Electronic Arts is alleged to be cutting between 500 and 1,000 jobs due to Battlefield 3 and Star Wars: The Old Republic performing below expectations. EA has downplayed the reports, though it wouldn't deny that jobs have been lost. 

"There are no lay-offs as such, we always have projects growing and morphing," said the company. "At any given time there are new people coming in and others leaving. EA is growing and hiring and building teams to support the growing demand for digital games and services."

The layoffs were said to be a result of disappointment over Battlefield 3 and The Old Republic. While both games enjoyed good launches, it's believed they didn't do well enough considering the obscene amounts of money EA had put into marketing and licensing. If I'd paid to have Battlefield 3 plastered over everything in existence, I'd probably expect better as well. 

Of course, any folk who lost their jobs are probably blameless in that scenario, as they so often are.

EA denies lay-off reports [MCV]


 Reblog (or) Blog Reply




Jim Sterling, Former Reviews Editor
 Follow Blog + disclosure JimSterling Tips
Destructoid reviews editor, responsible for running and maintaining the cutting edge videogame critique that people ignore because all they want to see are the scores at the end. Also a regular f... more   |   staff directory

Get more destructoid:   We're indie-run, blogging for the love of it, and our site will always be free. Optionally, you can support us and get: (1) Faster pages from our cloud server (3) Wide(r)screen (3) No big ads on Dtoid, Japanator, Tomopop, or Flixist (4) Auto contest entries, and (5) Dibs on betas & downloads. Try it out

 Setup email comments

Unsavory comments? Please report harassment, spam, and hate speech to our moderators, and flag the user (we will ban users dishing bad karma). Can't see comments? Apps like Avast or browser extensions can cause it. You can fix it by adding *.disqus.com to your whitelists.
advertisement:




Back to Top