QA Engineer

QA Engineer Position Overview

We're looking for a QA Engineer who operates less like a gatekeeper and more like the most demanding customer on the engineering team. Based in New York City's vibrant Flatiron District, Hatz AI is building the AI-native platform for Managed Service Providers (MSPs) and the small businesses they serve. Because you sit closest to the customer and understand our critical workflows better than anyone on the team, you'll own product quality strategy outright—deciding where risk-based coverage matters most, and owning end-to-end testing with full autonomy over the frameworks and tools you use to get there.

This isn't a role for someone who just executes a test plan handed to them. Critical workflow coverage is your version of code coverage—it's the metric you're accountable for, and you decide how to hit it. You'll partner closely with engineering: reviewing and getting hands-on with the integration tests they own, helping testability get considered before code is written, and using AI to build the rules, skills, and frameworks that scale your judgment across the team rather than routing everything through you.

• We ship. We'd rather see a working feature that isn't perfectly polished than a release that's stalled chasing edge cases nobody will hit. Bias toward end-to-end coverage—test the flows customers actually use before the ones that are easy to test.
• AI-native by default. We expect you to use AI as a force multiplier—not just to generate test cases faster, but to build reusable rules, skills, and frameworks that bake your quality judgment into the team's workflow, so testability gets considered without you needing to be in every conversation. That means reviewing what the model produces, catching its blind spots, and owning the result rather than blindly trusting it.
• Resilient under change. Features change fast, schemas migrate live, and APIs shift under you. We value QA engineers who write tests that survive change, isolate root cause quickly, and adapt coverage instead of letting the suite rot.
• Customer-fluent. You can explain why something broke (or why it matters) without hiding behind jargon, and you keep the real user experience in mind—not just whether a test passed.

This is the non-negotiable core of the role—what we're hiring for first.

• Own product quality strategy: help decide, based on critical customer workflows, where risk‑based test coverage matters most.
• Be responsible for end-to-end testing, with discretion to choose and evolve your own test frameworks and tooling. Critical workflow coverage is your version of code coverage.
• Build AI-assisted rules, skills, and frameworks that let testing judgment scale across the team without requiring manual testing input on every ticket.
• Review and get hands-on with the integration tests engineers write. Unit and component-level testing stays owned by engineering; you're encouraged to get involved wherever it strengthens coverage.
• File clear, reproducible bug reports, and grow into contributing fixes directly—AI-assisted coding makes this realistic once you're covering the core of the role.
• Define and track the quality metrics (critical workflow coverage, defect escape rate, regression trends) that tell us whether the strategy is working.
• Build and run evals for our AI features—golden datasets, regression suites, and scoring rubrics that catch hallucinations, accuracy drift, and prompt or model regressions before they reach customers.
• Communicate clearly with teammates and customers, translating quality tradeoffs and technical issues into plain language.

Quality strategy, end-to-end ownership, and critical workflow coverage are what we're hiring for. Once that core is solid, we'll grow you into:

• Performance and load testing.
• Exploratory testing.
• A/B test design and analysis.
• Beta and MSP customer programs.
• Support engineering.
• Contributing bug fixes directly, not just filing them.

• Experience owning quality strategy and risk-based test prioritization, not just executing a test plan someone else scoped for you.
• Proven ownership of end-to-end test…