Senior QA Engineer

We're looking for a seasoned Senior QA Engineer with 6-8 years of experience in complex, enterprise-scale software to join our Agile product team and be a quality champion embedded across the full software development lifecycle, from refining user stories to post-release checks, ensuring we ship reliable, performant software at pace. With core strengths in understanding applications and business processes, designing test strategies and test plans, and validating acceptance criteria via detailed test cases. Experience in QA automation is a plus, but it is not the focus.

Responsibilities:

• Own test strategy and perform end-to-end execution for complex, multi-module features.
• Shape quality upstream. Partner with product and engineering to clarify acceptance criteria and Definition of Done and raise quality risks while they're still cheap to fix.
• Test new features. Exploratory and scenario-based testing of new functionality.
• Own the regression suite end-to-end, its architecture, conventions, quality bar, and roadmap.
• Drive continuous improvement of QA processes, tools, and standards across the team.

Requirements:

• Ownership mindset: you can take a test suite as your own, set its standards, make and defend trade-off decisions, and say no when coverage isn't worth it.
• Product and feature literacy: you can look at a feature, reason about what matters to users, and translate that into the right tests, acceptance criteria, and risk-based priorities.
• Strong exploratory and scenario-based testing: boundary, negative, and edge-case thinking.
• API testing of REST services and comfort reading Swagger/OpenAPI specs.
• Solid SQL skills for data validation and defect investigation.
• Clear communication and the ability to mentor; comfortable in Agile/Scrum/Kanban.

Nice-to-have:

• Hands-on browser automation with Playwright (or strong Cypress/Selenium with willingness to move to Playwright), in TypeScript/JavaScript.
• Comfort with AI-assisted development tooling (Claude Code, Playwright MCP, Copilot) as an accelerant for writing and self-healing tests.
• Experience building or substantially evolving a test suite from scratch, not just maintaining one.
• Domain exposure to LegalTech, FinTech, or billing/AR workflows.
• Awareness of non-functional testing (performance, accessibility, security).