QC Manager

What You Will Own

1. End-to-End Quality Ownership

● Own the full quality pipeline from AI prompt input to final editor output

● Ensure every product feature — document, design, image, and video editors — meets the highest quality standard before and after release

● Take accountability for quality outcomes, not just quality processes

2. Bridge Between AI Quality and Software QA

● Identify whether issues originate from AI output quality or software/editor performance

● Eliminate ambiguity and finger-pointing between teams

● Own the intersection — the handoff point between AI-generated output and editor rendering

● Be the single point of escalation when issues are unclear in ownership

3. Build and Lead the QC Function

● Manage and mentor the Philippines-based AI/prompt QC team

● Collaborate closely with the Vietnam-based development team of 20+ engineers

● Work with developers to embed QA thinking into the development process

● Define team structures, workflows, and responsibilities across both locations

● Hire and grow the QC team as the product scales

4. Define Quality Standards and Frameworks

● Build QC frameworks for AI output quality — accuracy, relevance, consistency, and prompt reliability

● Build QC frameworks for technical/software quality — editor functionality, rendering, performance, cross-device and cross-browser behavior, file export formats

● Create and maintain a master quality benchmark for every editor type (document,design, image, video)

● Define what "done" and "quality" means for every feature released

5. Integration and Intersection Testing

● Design and own integration testing — testing the full flow end to end: prompt → AI output → editor → final deliverable

● Ensure no quality issues fall through the gap between AI and software teams

● Build regression testing processes to catch recurring issues early.

6. Bug Management and Resolution

● Own the bug tracking system — ensure all issues are clearly documented, prioritized, and resolved

● Create a clear issue flow so bugs are routed to the right team immediately

● Track bug resolution times and drive continuous improvement

● Report quality metrics and trends to leadership regularly.

7. Process and Communication

● Build clear communication protocols between the Philippines and Vietnam teams

● Run regular joint QC reviews across both teams

● Create standardized bug reporting templates so AI testers can clearly communicate software issues to developers

● Conduct regular QC syncs with product and development leadership

What We Are Looking For

Must Have

● Proven experience in QC or QA management in a software product company

● Strong understanding of AI-generated outputs — ability to evaluate prompt quality, output accuracy, and consistency

● Strong understanding of software QA — ability to identify, document, and prioritize software bugs across web-based editors

● Experience managing remote, cross-cultural teams across multiple locations

● Exceptional ability to identify root cause of issues at the intersection of AI and software

● A natural ownership mindset — you do not wait to be told, you act

● Strong communication skills — able to translate technical issues clearly between non-technical testers and developers

● Experience with bug tracking tools such as Jira, Linear, or equivalent

● Ability to build QC processes and frameworks from scratch.

Nice to Have

● Experience working with creative software tools — design, image, video, or document editors

● Familiarity with AI/ML products and how language or image models generate outputs

● Background in prompt engineering or AI output evaluation

● Experience scaling a QC team from early stage to growth stage

The Kind of Person We Need

● You own outcomes, not just tasks

● When something is broken, you are already working on fixing it before anyone asks

● You can make a clear decision on whether a bug is an AI problem or a software problem— and you are right most of the time

● You communicate directly and clearly — no politics, no blame

● You can work across cultures and time zones without losing momentum

● You are equally comfortable talking to a prompt tester in the Philippines and a senior developer in Vietnam

● You build systems and processes that outlast you — your team should get better because of the frameworks you build

● You care deeply about the end user experience — quality is not a checklist to you, it is a standard you hold personally

Key Performance Indicators

● Reduction in bug escape rate — fewer issues reaching end users post-release

● Reduction in bug resolution time — issues identified and fixed faster

● Improvement in AI output quality scores across all editor types

● Integration test coverage — percentage of end-to-end flows tested before release

● Team productivity — Philippines and Vietnam QC collaboration efficiency

● Regression rate — reduction in recurring bugs