Start with the work
The application rules also differ by region. Riot's student-program page separates the United States, Sydney, EMEA and Latin America. EA's FAQ gives specific conditions for U.S. and Canadian internships, while Activision publishes different program lengths across regions. A global careers page does not establish a global eligibility rule.
Decide which work you want someone to review
Use the actual job description to choose the evidence that should appear first. The table is an application framework, not a list of departments guaranteed to be hiring today.
| Direction | Strong evidence to foreground | What it does not establish by itself |
|---|---|---|
| Game design | A small playable experience and an explanation of design decisions | That enjoying a genre makes you ready to balance a commercial game |
| Engineering | An implementation, tests and a technical decision you can explain | That a finished group game proves which code you wrote |
| Art or animation | A focused portfolio with contribution breakdowns | That every attractive image fits the advertised discipline |
| Production | A project plan, resolved dependency or coordination example | That participating in a game jam means you managed the whole team |
| Research, analytics or player communication | Evidence appropriate to the task and audience | That a high competitive rank substitutes for research or communication skill |
Pick a primary direction and tailor the application accordingly. A portfolio that tries to demonstrate every discipline can leave a reviewer unsure which job you want.
Game design applicants should explain a player decision
A useful small project makes one interaction understandable. What does the player see, choose and learn? Which part of the experience did you revise after watching someone else play?
Describe the intended behavior and the evidence you collected. If testers repeatedly misunderstood an objective, explain what you changed and what you observed afterward. A limited playtest can inform a design revision without proving that the game would retain a large audience.
Make the project easy to inspect. Provide a short description, clear controls and an accessible demonstration where permitted. A reviewer should not need a long setup process simply to understand the idea. State which assets, tools and contributions came from other people.
Do not hide unfinished work behind a large fictional production story. A small, coherent project with a considered revision is more useful than an ambitious concept with no evidence that anyone can play it.
Engineers should separate gameplay from other technical work
Read whether the role concerns gameplay, tools, infrastructure, data, platform services or another problem. A game company can need technical work that is not visible directly on the screen.
Choose a project explanation that fits. Discuss the input, expected behavior, failure you found and the method used to check the result. If performance matters, define what you measured rather than presenting an unexplained benchmark.
A group project needs a contribution breakdown. Explain the part you implemented, the interfaces with other work and how you handled a change. You can acknowledge libraries and collaborators without weakening the application; that information helps a reviewer understand your judgment.
Keep your claims proportional. A prototype is not a live game service with millions of users. The ability to explain why a small system works is a credible starting point for an internship.
Production work needs evidence of coordination
A production-oriented applicant should show how they helped people deliver work under constraints. A game jam, student film, publication or event can provide relevant experience if you explain the actual responsibility.
Describe a dependency that was missed, a scope decision or a communication problem. What did you do, who needed to decide and how did the plan change? Listing the project's tools does not answer those questions.
Ask what an intern would maintain or support: a schedule, task tracking, meeting follow-up or another process. Then ask how the team teaches its workflow. A role becomes easier to evaluate when you know who relies on the information you would prepare.
Avoid treating production as a fallback for someone who likes games but has no technical portfolio. It has its own work and evidence requirements. Apply because those responsibilities interest you.
Read the candidate rules for the country you would work in
At the September 16, 2026 source review, Riot's U.S. summer program generally lasts ten to twelve weeks, requires full-time availability and is for actively enrolled applicants; enrollment need not be full-time. Its Sydney program is currently software-engineering focused, approximately fourteen weeks, and requires on-site attendance several days weekly. EMEA conditions vary, with current enrollment not required for roles in Germany, Ireland and the United Kingdom under the published general guidance. Exact postings still control.
EA's FAQ states that U.S. and Canadian internship/co-op applicants must be enrolled full-time, have at least one term remaining and be legally authorized to work without sponsorship. Other countries' conditions are left to their job descriptions.
Those are real differences. A candidate cannot borrow the most favorable condition from one company or region and apply it to another. Record your actual degree timeline, work authorization and location before deciding which program to pursue.
Use recruiting patterns to prepare, not to invent a deadline
The September 16, 2026 program-page review records general timing: Riot says U.S. summer applications open in the fall and advises checking individual roles. Activision describes a twelve-week U.S. summer program with applications generally opening September–November, with some art applications extending later. Neither statement creates one exact closing date for every discipline.
Prepare the reusable parts before the relevant period: résumé, portfolio access, contribution notes and a clear project explanation. Then read each posting when it appears. An old Summer 2026 requisition is not a Summer 2027 vacancy because its graduation window includes 2027.
Keep application dates, program dates and your expected graduation date in separate fields. These are easy to confuse in a crowded tracker and can lead to applying for the wrong cycle.
Passion should make your questions better
Use your experience as a player to notice a problem, then discuss it as a question rather than a verdict. You can explain why a feature interests you without claiming to know the team's constraints or internal data.
Riot's FAQ explicitly says applicants do not need a particular rank. That is a useful correction for students who assume competitive standing is the central qualification.
For player-facing or research work, prepare an example of listening, accurate communication or interpreting feedback. For an engineering role, prepare a technical explanation. The game connection supplies context; the discipline supplies the evidence.
Do not imply that being part of a fan community gives you permission to represent the studio, disclose private material or contact players on its behalf. Keep independent projects clearly identified.
Sources[1]
Compare internships by the assignment and review process
Ask what the intern is expected to finish, who reviews the work and what happens when priorities change. Clarify whether you would support an existing team or primarily complete an intern-specific project. Both can be useful, but the learning model should be understandable.
Then compare paid terms, worksite, schedule and relocation arrangements from the actual offer. A remote label does not remove country restrictions, and a possible travel benefit does not settle housing costs.
Your strongest application leaves a simple impression: you understand the discipline, have attempted relevant work and can explain what feedback changed. That is more persuasive than trying to prove you love the company's games more than every other applicant.