heartbeathealth - Heartbeat Health - Principal Quality Engineer

• You've established or significantly evolved a QA function - not just executed within one. You've defined the principles, chosen the tools, and changed how a team thinks about quality. • You work as a peer alongside engineers and product, not downstream from them. You influence development practices, not just validate outputs. • You have deep technical fluency in test automation, CI/CD, and testing infrastructure. You can build frameworks, not just use them. • You think in systems: risk models, failure modes, configuration matrices, integration boundaries - not just test cases and coverage percentages. • You balance automation with exploratory testing and have strong judgment about when each is appropriate. • You're comfortable with ambiguity. This role has clear objectives but no playbook. You'll define the structure. • ## Strongly Preferred: • Experience in healthcare, fintech, or other regulated industries where reliability, auditability, and documentation rigor are non-negotiable. • Familiarity with clinical data standards or healthcare integrations (FHIR, HL7, CCDA). • Experience testing highly configurable systems - platforms where behavior varies significantly by client, configuration, or data conditions. • Practical experience validating AI/ML-assisted workflows, including understanding the difference between testing deterministic logic and testing probabilistic systems. • ## How We Work: • Our core development team is small and intentionally lean. Every team member has outsized impact on how the platform grows. • We value solutions that are understandable, maintainable, and right-sized. We ship small, testable increments and adjust based on what we learn. Our process is Kanban-style flow — not rigid sprints or bloated backlogs. We invest in tooling and observability so we can understand what's happening in production and move quickly with confidence. • We avoid silos. Engineers collaborate directly with product, clinical, and compliance stakeholders through shared ownership, not handoffs. The best outcomes come from close, cross-functional work - not heavyweight processes or long ticket queues. • This is a remote-first, high-autonomy environment. You need to be comfortable working independently, collaborating asynchronously, and shipping incrementally.