Electronic Arts · Primly Community

Electronic Arts new grad roles: labels, bar, how to stand out

Primly Team · 0 replies

Breaking into Electronic Arts (EA) as a new grad often starts with knowing how entry-level roles are titled, what the early screens look for, and how to make your application feel “job-ready” instead of “class-project-only.” How new-grad openings tend to be labeled For companies at EA’s scale, entry-level roles are commonly posted under labels like “Entry-Level,” “Associate,” “Junior,” “Analyst,” “Coordinator,” or “Early Career.” Sometimes they appear as standard role titles (for example, QA Analyst or Business Analyst) with “0–2 years” requirements rather than a “New Grad” banner. When searching, use a few title variants plus the discipline keyword (QA, analytics, community, marketing). What the screening bar usually looks like At this level, screens typically focus on: Role fundamentals (can you do the core tasks on day one with guidance?) Signal of craft (clear thinking, structured communication, basic tooling) Domain fit (do you understand games and players enough to make good decisions?)

From our notes on EA role patterns: Business Analyst screens often emphasize strong SQL and case-style game analytics with solid understanding of game metrics and player experience. Community Manager screens can include community case studies, looking for comfort with difficult situations and knowledge of gaming communities. QA Analyst processes may include a testing assessment, valuing attention to detail and QA methodologies. Marketing Manager case work tends to reward understanding gamer culture and the importance of community. Three concrete ways new grads can stand out Ship a portfolio artifact that matches the role’s screen (SQL analysis write-up, QA test plan + bug report set, community escalation playbook, marketing brief with audience insights). Speak in game metrics and player outcomes, not just features. Tie your work to retention, engagement, sentiment, or quality. Show calm, structured judgment: clear assumptions, tradeoffs, and how you’d handle edge cases (toxic threads, ambiguous bugs, noisy data).

Where are you in your EA search right now: browsing roles, applying, interviewing, or building your portfolio first?