Quality Assurance Engineer

• Own quality strategy for features and domains, including test plans, risk assessment, and coverage decisions
• Identify ambiguities and testability gaps during requirements review
• Define acceptance criteria with Product
• Balance manual exploratory testing with automated regression coverage
• Document test plans, coverage decisions, and known risks
• Write and maintain API, integration, and end-to-end automated tests
• Keep automation suites fast, reliable, and maintainable
• Maintain CI/CD integration for test execution
• Monitor production features using observability tools
• Respond to developer escalations and incidents by assessing blast radius, conducting targeted regression testing, isolating root causes, and communicating findings
• Use AI tools daily to generate test cases and data, draft test plans, analyze bug patterns, and accelerate automation writing
• Critically review AI-generated test output and prioritize tests based on risk
• Write clear, reproducible bug reports and advocate for quality before release
• Collaborate with developers to improve testability and identify untested scenarios
• Mentor junior QAs at L3+ and establish AI quality standards at L3/L4
• Participate in shared engineering on-call rotation of approximately one week per month after ramp-up

• Strong testing fundamentals: test strategy, test case design, and risk-based prioritization
• Hands-on automation experience with Playwright
• Comfortable with API testing using Postman/REST clients and reading application logs
• Already using, or genuinely motivated to use, AI tools in a QA workflow
• Clear written communication for actionable bug reports and test plans
• Experience with API testing, browser automation, and unit/integration test frameworks
• Familiarity with GitHub Actions, AWS CloudWatch, application logs, metrics dashboards, PHP/TypeScript, Ruby/TypeScript, MariaDB, Redis, and AWS
• Experience testing an e-commerce, payments, or subscription platform is nice to have
• Familiarity with PHP, TypeScript, or Ruby codebases is nice to have
• AWS/CloudWatch or similar observability tooling is nice to have
• GitHub Actions or another CI/CD pipeline is nice to have
• Level expectations range from 0–1 years for L1, 1–3 years for L2, 3–6 years for L3, and 6+ years for L4

• Shared on-call rotation with engineering (~1 week/month after ramp-up)
• Regular knowledge-sharing sessions
• Open environment with opportunities for active participation in shaping the platform
• Career path: Junior QA → QA Engineer 1 → Senior QA → Lead QA → Head of Quality