QA Engineer - Automated Testing

• Playwright E2E suite - expand and systematize coverage across the application, owning the roadmap for what gets tested next and why.
• Vitest integration tests - write tests for database triggers, stored procedures, and accounting logic running against a real PostgreSQL instance.
• AI-generated test review - raise the bar on AI-assisted tests, ensuring assertions are meaningful rather than surface-level.
• CI pipelines - maintain and extend GitHub Actions workflows for both test suites, including job dependencies, caching, and artifact management.
• Coverage standards - define what gets flagged, what gets blocked, and what the right thresholds look like as we scale.
• Test health visibility - build and maintain reporting on pass rates over time, coverage trends, and flakiness so the whole team stays informed.
• Accounting domain depth - develop real understanding of our GL, AR/AP, invoicing, and bank reconciliation workflows to write assertions that catch actual regressions.
• Risk surfacing - when you see a pattern that could become a problem, bring a proposed solution, not just the observation.

What you'll need

• TypeScript, * Frontend + API: Next.js (TypeScript), tested with Playwright (including Playwright's API testing)
• Database: PostgreSQL via Supabase, tested with Vitest + Drizzle ORM
• CI/CD: GitHub Actions
• Package management: Bun
• AI tooling: AI coding assistants used throughout the workflow

The stack

• Frontend + API: Next.js (TypeScript), tested with Playwright (including Playwright's API testing)
• Database: PostgreSQL via Supabase, tested with Vitest + Drizzle ORM
• CI/CD: GitHub Actions
• Package management: Bun
• AI tooling: AI coding assistants used throughout the workflow

How we work

We use AI coding assistants throughout our workflow - for scaffolding, iteration, and getting to passing tests faster. We expect you to do the same. What we care about is whether the resulting tests are actually valuable: meaningful assertions, real coverage, and a suite that tells us something true about the health of the system.

Our dev team already writes tests alongside features. You won't be fighting an uphill battle for buy-in - you'll be raising the standard of what already exists and making the case for what comes next.

This role is based in our Stuart, FL office Monday through Thursday, with the flexibility to work remotely on Fridays.

• Experience with a modern E2E testing framework (Playwright preferred, Cypress or similar accepted). Page Object Model, semantic locators, fixture patterns, API testing, avoiding flaky anti-patterns.
• Vitest or equivalent. Comfort writing integration tests that hit a real database, not mocks.
• Working experience with GitHub Actions. Reading and modifying CI workflows, understanding job dependencies, caching, artifacts.
• Comfort with PostgreSQL at a read level. Enough to understand what a trigger does and write a test that verifies it.
• Ownership mindset. You'll be defining what needs coverage, prioritizing it yourself, and advocating for it across the team.
• Raises issues early with context. You don't wait until something is critical to flag, and you come with a point of view on what to do about it.

• 401(k) matching
• Health insurance
• Paid time off

Round 2 AI is an AI-first business management consultancy serving small and mid-sized businesses that have outgrown the patchwork of disconnected tools holding their operations together. We work across accounting, operations, and AI - building proprietary systems tailored to each client's environment rather than selling a one-size-fits-all product. Because our solutions are custom-built and carry real financial weight, the integrity of the underlying systems is everything. We've developed a sophisticated internal technology foundation - purpose-built to power the work we do for clients - and we treat the quality of that foundation with the same rigor we'd expect from any serious engineering team. That means a real testing strategy, not an afterthought. We're looking for a QA engineer who wants to do more than maintain a test suite. You'll inherit strong foundations - database integration tests, a Playwright E2E suite, and a dev team already accustomed to writing tests alongside features - and shape what quality engineering looks like here going forward. This is not a manual testing role. You'll spend your time writing code, thinking about coverage strategy, and bringing ideas to the table. What you'll own