Senior Automation Engineer

Firmable is the market-leading B2B sales intelligence platform in Asia-Pacific. Our competitive moat is our data: the deepest, most localised company and people dataset in every market we operate in. We've proven the model in ANZ. Now we're scaling it across Southeast Asia and the US.

Quality is how we protect that moat. This role owns it.

The Role

Senior QA Automation Engineer owns test automation end-to-end: building and maintaining Playwright regression suites, running synthetic monitoring in production, and leading the move to AI-assisted testing. You're the voice of quality in the team: you speak up early, write clearly, and report results that matter to engineers and product managers.

This is not a "test reporter" role where you run tests and log bugs. It's an automation ownership role where you build the testing infrastructure, debug flaky tests to root cause, and shape how quality gets designed into features from spec onwards.

Reporting to Engineering Lead, based in Melbourne (hybrid, flexible).

~75% hands-on execution: building and growing Playwright suites; running synthetic monitoring; debugging flaky tests; building CI/CD quality gates; testing APIs, auth, integrations (CRMs, extensions); maintaining test data; leading AI-assisted test generation and maintenance.

~25% strategy: test design and coverage strategy; test reporting; quality advocacy; working with engineers and product early in the spec and PR stages.

What You'll Own

Test automation infrastructure

• Playwright regression suites: build and grow suites across search, company and people views, lists, signals, credits, sign-up and CRM flows; own page object patterns, parallelism, retries

• Synthetic monitoring: run Checkly production monitoring; configure alerts and SLOs; own the health of journeys that matter

• CI/CD quality gates: build gates against preview and staging deployments; own gate configuration and failure analysis

• Test data management: manage and maintain test data; ensure data isolation and repeatability

Quality through design

• Flaky test debugging: find and fix the root cause of flaky tests; own test reliability and suite speed

• API and integration testing: test APIs (REST, auth, role-based access control); test integrations end-to-end with HubSpot, Salesforce, Dynamics, Pipedrive and our Chrome extension

• Test design: turn rough testing notes into clear, structured test cases; own test strategy and coverage decisions

AI-assisted testing

• Agentic and LLM-assisted tests: lead the move to AI-assisted testing using frameworks like Browser Use, Stagehand or Playwright MCP; experiment with agentic and natural-language browser tests

• AI-generated test cases: work with LLM-generated test cases from specs; use Claude Code or Cursor to write, maintain and review test specs

• Quality reporting: publish regression reports that engineers and product managers understand; speak up early and clearly

What We're Looking For

Must Haves

• 5+ years test automation in Playwright: you've built and maintained production Playwright suites in TypeScript or JavaScript; you know the framework inside out

• Solid test design: page objects, test strategy, parallelism, retries; you know how to find and fix the root cause of flaky tests, not just re-run them

• API testing and CI/CD: REST API testing; auth and access control testing; integrating suites into CI/CD (GitHub Actions or similar); building quality gates

• Hands-on AI in testing: you've generated, run, maintained or triaged AI-assisted tests. You can explain where it worked and where it didn't. You use AI coding assistants (Claude Code, Cursor) every day and review their output critically

• Very good communication: clear written bug reports and test reports; confidence pushing back on a release when the risk is real; comfort working async with a team in Australia

• Product mindset: you think like a customer; you prioritise by risk, not by coverage numbers. You care about what matters to users, not just coverage metrics

• You live and breathe AI tools. You use AI daily for test spec writing, test generation, debugging test failures, and test maintenance as your default way of working, not a productivity experiment. In 2026, this is how test automation moves fast, and you need to already be doing it.

Highly Valued

• Synthetic monitoring: Checkly or similar production monitoring; alert configuration; SLO thinking

• Chrome extensions or complex integrations: hands-on experience testing browser extensions or thick CRM integrations

• Agentic testing frameworks: Browser Use, Stagehand, Playwright MCP or similar; experience experimenting with agentic approaches

• Performance and load testing: k6 or similar; understanding of performance constraints in web testing

• Visual regression testing: tools and patterns for visual regression

• SQL and test data: Postgres/Supabase knowledge for managing and seeding test data

• B2B SaaS or data products: experience in B2B or data-heavy products where quality and integration complexity matter

The Environment

Firmable runs lean and ships fast: small senior teams, no layers, minimal process. You'll work closely with the engineering team in Melbourne and push quality gates hard. There's no separate "QA team": you own the full scope from test design to CI/CD reporting, with engineers as your partners.

We are an AI-native organisation. That means AI isn't a tool we reach for: it's the default operating mode. You'll use AI for test spec writing, test case generation, debugging test failures, and test maintenance. You'll experiment with agentic testing frameworks as they emerge. If you're not already working this way, this role isn't right for you.

Why This Role

• Automation ownership: you own the full testing stack from design to CI/CD. No handoffs, no "that's someone else's job."

• AI at the core: AI-assisted testing isn't experimental; it's how you'll scale coverage without bloating maintenance. You'll ship AI-assisted tests every quarter.

• Real career runway: as the platform scales and the team grows, you can move into quality architecture, test strategy, or lead a growing testing team. The ceiling is set by output, not tenure.