On Apex Legends I took on the role of a Senior QA Analyst on the Player Expression team which included MTX and UI. 

​

In addition to my normal duties as a QA Analyst since our team on Apex was much larger and had dedicated testers I was able to focus on higher level duties such as testing coordination, guiding testers, process improvements, data collection, documentation, and information sharing between teams. One of my biggest initiatives on Apex was bridging the gap between QV teams on projects and sharing processes between the two. To do this I audited all of Apex's processes and created a massive presentation on all of them for the Jedi team that went over what the process was, how it worked on Apex, negatives and positives, and how we could adapt it to work on Jedi (if it made sense for Jedi). ​

​

​One of the initiatives that I'm most proud of getting Apex up and running on the Epic Games store. While I wasn't the only person who worked on getting Apex running on the EGS, I was the only person from QV spearheading the testing initiative. Getting it off the ground was surprisingly complicated since we were redirecting Apex to the EA App which caused all kinds of problems and required me to work together with multiple different teams external to Respawn on solutions and create my own documentation for our QV to reference in the future.

​

Apex was a really cool project to work on because it was my first project that wasn't on Unreal and was managed completely different compared to the Jedi team. There was a lot of really great opportunities to experiment with processes in between seasons and bridge the communication between Respawn's two QV teams, a gap that historically had never really had a bridge built over it.