Narrative QA Analyst - job 1 of 2

As a Narrative QA Analyst at CD PROJEKT RED, your key responsibilities include developing and executing Narrative QA test plans, maintaining dialogue consistency checks, documenting testing processes, and collaborating with the design team to ensure narrative alignment. You’ll also be analyzing game narratives for coherence, engaging in comprehensive testing of storylines, and tracking and verifying bug fixes to enhance the overall narrative quality throughout the game.

To qualify for the Narrative QA Analyst position at CD PROJEKT RED, candidates should have a minimum of three years experience in a similar role, expertise in creating test checklists, and proficiency in bug-tracking tools like JIRA. A strong understanding of video game storytelling mechanics and collaborative feedback skills are essential, along with keen attention to detail and analytical thinking.

A Narrative QA Analyst at CD PROJEKT RED can enjoy a range of perks, including company-paid healthcare coverage, generous paid leave, a casual dress code, gym membership reimbursement, and opportunities for professional growth through training and workshops. The company also fosters a dog-friendly office vibe and boasts a diverse international working environment.

In the Narrative QA Analyst role, you'll contribute to the success of Project Orion by ensuring that every narrative element is polished and engaging. Your input on quest logic, dialogue accuracy, and emotional representation will directly influence the quality of the player experience, helping make Cyberpunk's next chapter both captivating and immersive, which is critical for the game's overall reception and success.

At CD PROJEKT RED, a Narrative QA Analyst can expect a dynamic and inclusive work environment that encourages creativity and collaboration. The Boston studio combines the fun of gaming culture with professionalism, offering a dog-friendly atmosphere and flexible working hours to support both personal and professional life. Teams from diverse backgrounds work together in a space filled with passion for gaming.

Certainly! In previous roles, I've focused on creating detailed test documentation by clearly outlining test cases, maintaining a bug tracking system, and ensuring that all findings are accessible to my team. I emphasize consistency and clarity in documentation, allowing for an organized approach to narrative QA processes.

To tackle dialogue consistency, I would create a checklist that outlines each character's speech patterns, phrases, and emotional tones. I would then test the dialogue within the context of the game to ensure it aligns with established character backgrounds and does not contradict previous interactions while also assessing for grammatical or contextual errors.

Effective feedback starts with targeted analysis. I review quest flow by playing through scenarios, paying attention to pacing and player choices. I document my observations clearly and provide constructive suggestions, focusing on enhancing player engagement while ensuring that quests are logically structured. Collaborative discussions with writers also help refine narrative elements.

I ensure emotional representation by analyzing the script and context of each scene, paying close attention to character motivations and outcomes. I also evaluate voice-over pacing and delivery during my tests, providing feedback on how effectively the scene captures the intended emotional impact and enhances the player's connection to the story.

In my previous experience, I utilized bug-tracking tools like JIRA to document narrative bugs systematically. Firstly, I reproduce the bug in-game, then I record its context, the impact on gameplay, and the steps to recreate it, assigning it priority levels based on how it affects player experience, ensuring clear communication with the development team for prompt resolutions.

I've worked extensively with branching narratives, which requires an intricate understanding of player choices and their consequences. This influences my testing approach, as each decision point must be analyzed for consistency. I create test cases that account for various player paths to ensure all outcomes are coherent and logically linked.

Collaboration is key in creating a cohesive narrative experience. I regularly hold meetings with writers and designers to discuss narrative goals and challenges. By being open to feedback and actively participating in creative discussions, I help bridge gaps between narrative intent and gameplay implementation.

Analytics play a significant role in understanding player engagement with narrative elements. I assess data from player interactions to identify trends in player behavior and feedback collected during playtesting. This data informs my testing focus, ensuring that narrative elements are optimized based on actual player experiences.

In a previous project, I discovered an inconsistency where a character's backstory contradicted their actions during a quest. I reported it through our bug tracking system and collaborated with the writers to revise the dialogue and quest design, ensuring that the character's behavior aligned with their established history, thus creating a more believable narrative.

I stay updated on industry trends by following notable game developers and narrative designers on social media, participating in online forums, and attending conferences or webinars. Continuous learning through workshops and reading up on studies related to narrative design helps me refine my approach as a QA Analyst in the ever-evolving gaming landscape.