QA Tester
I believe that a great game is only as good as its stability. My background in Narrative and Level Design gives me a unique lens for QA; I don't just look for "broken code," I look for "broken experiences." Whether I’m stress-testing a Triple-A shooter or providing feedback on a peer’s indie prototype, my goal is always to bridge the gap between developer intent and player reality.
Functional Testing: Identifying "hard" bugs—collision issues, script breaks, and crashes.
​Narrative Consistency: Checking for dialogue loops, quest-line breaks, or environmental storytelling that contradicts the lore.
UX/UI Auditing: Ensuring menus are intuitive and that player feedback (HUD/SFX) matches the action.
Regression Testing: Verifying that new builds haven't reintroduced old "zombie" bugs.
Featured Testing Experience
AAA Industry Testing
-
Call of Duty (Series): Focused on environment collision, asset clipping, and multiplayer map flow. Provided detailed reports on "out-of-bounds" exploits that could break competitive balance.
-
Train Sim World: Conducted rigorous functional testing on simulation mechanics and UI accuracy. Ensured that complex control schemes translated clearly to the player across various hardware configurations.
Internal Peer Playtesting (Full Sail University)
Throughout my time at Full Sail, I acted as a Lead Playtester for over 15+ student projects.
-
The Goal: Help fellow designers find "fun-killers" early in the blockout phase.
-
The Result: Delivered actionable feedback loops that resulted in a 20% average increase in player retention during final build showcases.
My Testing Workflow
Identify: I use "Destructive Testing" methods—trying to do exactly what the designer didn't intend—to find the limits of the game world.
Isolate: I find the exact set of steps required to reproduce the bug 100% of the time.
Document: Using Jira or Trello, I create clear, concise tickets including:
-
Severity: (Blocker, Major, Minor, Trivial)
-
Steps to Reproduce: (1, 2, 3...)
-
Observed vs. Expected Result.
Advocate: I follow up with the engineering or design leads to ensure the fix doesn't compromise the narrative or gameplay "feel."