You should be happy to know that I just send in my resume for QA. However I have noticed there are several QA position- Whats the difference between those:

quality assurance analyst
technical quality analyst
release analyst



PS How long will I hear from them after submitting my application?

this thread op bump

Sometimes you need to get your foot in the doorway and then work your way up. Most of the original QA we've have hired at Riot are not doing QA anymore. The fields they have moved to are quite diverse.

Also we have a high bar for all our positions including QA.

Its a good question. I think having examples of hobby games that you've worked on even if they are board games, is one thing that could help. Of course the more game related experience you can show the better.

Bump

I just felt I needed to point out... I am the original Lee Sin here.

Are you guys taking QA jobs/internships over the summer? Because I sent in an application but never got a response. D=

Also applied to Game Engineering and Design, only received reply from Design (didn't make it), and GE has it's hands full (thank you for indirectly answering that part of my question hohums =D).

quality assurance analyst: General QA doesn't require specific technical knowledge. This is playing the game or trying out specific things to find bugs. You'll probably be placed on a specific team that looks after a specific feature.

technical quality analyst: You need at least some technical knowledge. It will be used for things like writing code to test code or figuring out more technical QA related issues.

release analyst: This is closer to a leadership role with QA as well in that you'll be responsible for making sure releases are good to go. It involves having a strong voice and smart decision making to make sure critical issues get fixed before release.

:P

I just want to add that QA can and is expected to speak up at all phases. From the earliest planning stages to after release, QA provides input. I know what every dev on my team is doing, and I know if they are running into difficulties. If someone outside my team needs to know what's up or what a developer is working on, they can talk to me instead of the developer.

We do QA a product or feature, but we also are responsible for the quality of our team's process. QA and Production are quite blurred, especially as you move up.

EXCELLENT! I love speaking up... sometime I am a bit too loud ha. ha. ha.