Knovon Consulting
Website:
knovonconsulting.com
Job details:
The Product Quality Analyst owns business-side test validation — designing and running UAT and beta test cycles, and conducting exploratory testing from a real-user and real-workflow perspective — while also writing the acceptance criteria and requirements those tests are built against. This role validates that what gets built and tested actually matches business intent, working closely with the Product Owner to shape requirements up front and with Development to make sure those requirements are technically clear before a single line of code is written.
Working closely with QA, Product, and Development, this role is the business-facing check across the full delivery cycle — from shaping what gets built, to confirming it works for real users doing real work, not just that it passes scripted test cases.
KEY RESPONSIBILITIES
1. UAT, Beta & Exploratory Testing
(primary focus)
- Design & Run UAT: Build and execute UAT scenarios directly, based on business requirements and acceptance criteria.
- Coordinate Beta Cycles: Run structured beta testing with real users on new features and releases, collecting and triaging feedback before general rollout.
- Exploratory Testing: Conduct unscripted testing from a business-fit angle — usability, workflow gaps, and edge cases that scripted QA test cases don't target.
- Validate Business Fit: Confirm AI/ML output and Web UI behavior make sense from a real-user, real-workflow perspective.
2. Requirement Refinement & Functional Analysis
(partnering with Product Owner & Development)
- Shape Requirements Early: Work directly with the Product Owner to break down new features, surfacing edge cases and gaps before they reach development — not just testing after the fact.
- Write Acceptance Criteria: Convert business requirements into clear, testable acceptance criteria that both development and testing can build against.
- Align with Development: Partner with Development to confirm requirements are technically feasible and scoped correctly before sprint commitment.
- Bridge Build and Validation: Sit in refinement and planning sessions so testing isn't a downstream afterthought — it's built into how features are scoped from day one.
3. Cross-Functional Support & Sign-Off
- Triage support tickets into confirmed bugs vs. user error, feeding real usage patterns back to the Product Owner.
- Give final business sign-off on releases, based on UAT/beta/exploratory results.
KNOWLEDGE, ABILITIES AND EXPERIENCE
Essential:
- UAT Design & Execution: Hands-on experience designing and running UAT test cycles.
- Beta Testing Management: Experience coordinating structured beta programs with real users.
- Exploratory Testing: Strong exploratory testing skills from a business/usability angle.
- Requirements Partnership: Experience working directly with Product and Development to shape and refine requirements pre-build, not just validate post-build.
- AI/ML Output Validation: Experience validating AI-generated output for business relevance and accuracy.
- Attention to Detail: Able to spot subtle inconsistencies in behavior or output.
- Cross-Functional Collaboration: Comfortable operating across Product, Development, and QA with a clear view of where each role's ownership begins and ends.
Desirable:
- Familiarity with Product and Test management tools (Jira, TestRail, Zephyr, Azure DevOps, etc.).
- Understanding of release governance and deployment cycles.
- Experience in SaaS or pharma-tech environments.
KEY PERFORMANCE INDICATORS (KPIs)
- UAT defect detection rate.
- Beta program coverage and feedback turnaround.
- Exploratory testing coverage from a business/usability lens.
- Production defect leakage tied to gaps in business-side testing.
- % of features refined with Product/Dev input before sprint start.
- On-time business sign-off against release schedule.
WHAT SUCCESS LOOKS LIKE
A successful Product Quality Analyst brings a real-user, real-workflow lens across the full delivery cycle — shaping requirements with the Product Owner before a feature is built, aligning scope with Development so nothing gets lost in translation, and then catching usability friction and edge cases before customers ever see them. They give the business genuine confidence that a release actually fits how people use the product, turning scattered UAT, beta, and exploratory feedback into clear, actionable insight so the team ships with certainty rather than guesswork.
Click on Apply to know more.
