ThriveCart - Quality Assurance Engineer

• Technical Environment • Testing: API testing (Postman/REST clients), browser automation (Playwright), unit/integration test frameworks • CI/CD: GitHub Actions (tests run on every PR) • Observability: AWS CloudWatch, application logs, metrics dashboards • Platform stack: PHP/TypeScript, Ruby/TypeScript, MariaDB, Redis, AWS • Playwright is our standard framework for browser automation — what matters most is strong testing fundamentals • Strong testing fundamentals — test strategy, test case design, risk-based prioritization • Hands-on automation experience with Playwright • Comfortable with API testing (Postman/REST clients) and reading application logs • Already using — or genuinely motivated to use — AI tools in a QA workflow • Clear written communication: bug reports and test plans others can act on without a meeting • Experience testing an e-commerce, payments, or subscription platform • Familiarity with PHP, TypeScript, or Ruby codebases • AWS/CloudWatch or similar observability tooling • GitHub Actions or another CI/CD pipeline • L1 (Junior QA) — 0–1 yrs: Executes test plans, writes simple automation with guidance, reports bugs clearly. Bootcamp, internship, or early professional QA experience is fine — we're hiring for rigor and curiosity over tenure. Uses AI to learn faster and generate test cases; validates all AI output. • L1 (Junior QA) — 0–1 yrs: • L2 (QA Engineer 1) — 1–3 yrs: Has independently owned quality for a feature or product area — not just extended someone else's test plan or suite, but built one. Writes comprehensive test plans and automation, and responds to incidents with targeted testing. • L2 (QA Engineer 1) — 1–3 yrs: • L3 (Senior QA) — 3–6 yrs: Has led incident response from the QA side and mentored other QAs. Owns quality strategy for complex projects, improves automation architecture and infrastructure, and uses AI to multiply output rather than just speed up individual tasks. • L3 (Senior QA) — 3–6 yrs: • L4 (Lead QA) — 6+ yrs: Has set QA standards or practices for a team, not just followed them. Serves as the quality authority for a domain, drives major incident response, and partners with leadership on quality metrics and AI tooling strategy. • L4 (Lead QA) — 6+ yrs: • Success Metrics • Success Metrics • 30 days: First test plan written and approved, first automated tests in CI pipeline, understands the most critical user journeys • 30 days: • 60 days: Independently owning quality for a feature, automation suite stable, first incident response contribution • 60 days: • 90 days: Contributing to test strategy discussions, handling dev-escalations independently in your area • 90 days: • On-Call • Career Path • Junior QA → QA Engineer 1 → Senior QA → Lead QA → Head of Quality