QA Engineer

Job description

We’re in search of a Senior QA Engineer who takes pride in ownership, thinks holistically, and strives for releases with minimal defects. You will drive our manual and exploratory testing strategies, establish reliable release validation routines, and make sure every build leaving staging exudes certainty rather than guesswork. This is far from a checkbox QA role. It’s a creator-focused QA position—requiring curiosity, rigor, and a thorough grasp of how complex SaaS products perform in real-world scenarios. You’ll dig deep into issues to understand why they arise, not just that they exist. You’ll introduce structure where it’s lacking, advocate for solid processes, and continuously raise the bar for team-wide quality.

Responsibilities

• Lead exploratory and regression testing for web and API components (mobile coming soon)
• Define and evolve QA processes – from test case management to release sign-off
• Collaborate closely with developers to isolate, reproduce, and explain complex issues
• Establish a strong “break the build” culture while maintaining team trust and flow
• Ensure test cases and results are organized and traceable in TestRail and Jira
• Use Postman for API validation and sanity checks
• Identify smart automation candidates and work with the team to expand coverage
• Provide clear, actionable bug reports – not just findings but insights
• Uplift QA practices across the team by sharing context, methods, and discipline

Requirements

• Have 6+ years of QA experience, including 2+ years in SaaS environments
• Have been the most senior (and not the only) QA in a dev-heavy team
• Bring ownership over exploratory manual testing and regression validation
• Can design test plans, regression suites, and release validation protocols that scale across tenants and components
• Are able to deeply understand the system architecture, APIs, and data flows
• Are confident signing off on releases, knowing you’ve tested the right things the right way
• Think like a user, test like a hacker, and communicate like a teammate
• Believe that QA’s role is to prevent issues before users ever notice them

Bonus Experience (Nice to Have)

• Experience with performance and non-functional testing using tools like JMeter, Locust, or k6
• Familiarity with multi-tenant SaaS, feature flagging, or release branching models
• Experience testing video-based platforms, personalization engines, or content delivery systems
• Understanding of CI/CD pipelines and release readiness metrics
• Comfort using AI tools for test design, data generation, or reporting
• Exposure to Playwright, Cypress, or similar automation frameworks