Manager, Quality Assurance

Plenful is building the AI operating layer for enterprise healthcare organizations. As an agentic workflow automation platform purpose-built for pharmacy and enterprise healthcare teams, Plenful connects fragmented systems, standardizes complex processes, and applies AI to automate the most labor-intensive and compliance-critical workflows. Today, more than 90 leading healthcare organizations rely on Plenful to power intake and prior authorization workflows, 340B compliance, rebate management, and claims reconciliation. By transforming institutional knowledge into scalable infrastructure, Plenful enables continuous operational improvement across distributed healthcare teams. As healthcare organizations increasingly demand automation that is intelligent, auditable, and enterprise-ready, Plenful is at an important architectural and organizational inflection point—scaling its platform, strengthening its engineering foundation, and expanding its AI capabilities to meet rapidly growing market demand. A Series B funded company, Plentiful has raised over $75M from investors such as Bessemer Venture Partners, Notable Capital, Arena Holdings, TQ Ventures, and Danaher Co-founder Mitchell Rales. Be sure to check out the press from TechCrunch, Forbes, Axios, etc. The Mandate We are seeking a Manager, Quality Assurance to define and own the quality strategy, systems, and operating model for Plenful. This is a high-leverage, planning-focused leadership role responsible for establishing how quality is measured, enforced, and continuously improved across the organization. This role is not focused on hands-on test execution. Instead, you will design the frameworks, policies, and quality signals that enable engineering teams and future QA ICs to deliver high-quality software at scale. You will act as the central owner of quality standards and governance, partnering closely with Engineering, Product, and Customer teams to ensure alignment on what “good” looks like—and how we prove it. What You’ll Own This role will take full ownership of: Release Readiness Policy Define clear, enforceable criteria for what constitutes a production-ready release, including quality gates, risk thresholds, and sign-off processes. Quality Metrics & Reporting Establish the core set of quality KPIs (defect rates, escape rates, test coverage, reliability signals, etc.) and build reporting frameworks that drive visibility and accountability. Defect Triage & Severity Framework Design a standardized severity model and triage process to ensure consistent prioritization, escalation, and resolution of issues across teams. Regression Strategy Define the long-term approach to regression coverage (automation vs. manual, risk-based prioritization, scope definition) to support rapid and reliable releases. Test Environment Strategy Establish requirements and best practices for test environments, including data management, environment parity, and CI/CD integration. Quality Signals & Evidence Standards Define what evidence is required to demonstrate quality (test results, logs, coverage, monitoring signals), and standardize how quality is measured and validated. Cross-Functional Intake & Prioritization for Quality Work Build and manage a system for capturing, prioritizing, and aligning quality-related work across Engineering, Product, and Customer-facing teams. What You’ll Do Define and evolve the end-to-end quality strategy, ensuring it scales with product complexity and company growth. Establish processes, policies, and standards that enable consistent, high-quality software delivery across teams. Partner with Engineering and Product leadership to embed quality into planning, development, and release cycles. Design a risk-based quality model, focusing efforts on the highest-impact areas rather than exhaustive coverage. Create clear feedback loops between customer-reported issues, internal quality signals, and product improvements. Build the operating system for QA, including documentation, governance, and decision-making frameworks. Manage and mentor QA engineers over time, while ensuring clarity between strategy (manager) and execution (ICs). Serve as the final escalation point for quality standards and decisions, not day-to-day test execution. What Success Looks Like Success in this role is defined by establishing a clear, scalable quality operating system that enables the organization to ship confidently and consistently—without relying on heroics or ad hoc QA effort. In the First 3–6 Months Release readiness is clearly defined and consistently enforced Every release follows