Associate QA Engineer

We're looking for a QA Engineer who owns quality end-to-end — someone who doesn't just find bugs, but prevents them from shipping. You'll test a multi-tenant event management platform used by thousands of organizers, covering payments, live streaming, registrations, and integrations where failures have real customer impact.

Experience

2–4 years in Software Quality Assurance, with hands-on automation experience (not just exposure)

Required Skills

• Test automation with Playwright (preferred) or Cypress/Selenium — able to write and maintain suites independently
• Strong manual and exploratory testing fundamentals — automation doesn't replace judgment
• API testing (Postman/Bruno) including auth flows, webhooks, and negative scenarios
• AI-assisted testing workflows — using tools like Claude, Copilot, or similar to generate test cases, analyze failures, and speed up test authoring (we expect this to be part of how you work, not a novelty)
• Bug tracking and sprint workflows in Linear/Jira/Any other standard tool
• Understanding of CI/CD basics — how tests run in pipelines, reading build failures
• Strong analytical and written communication skills — clear bug reports and repro steps matter here

Good to Have

• Experience testing payment gateways, subscriptions, or billing flows
• Performance/load testing exposure (k6, JMeter)
• Experience with event-driven systems, webhooks, or third-party API integrations
• Mobile/responsive web testing

Responsibilities

Own test strategy for features from requirement review through release

Build and maintain automated regression suites; keep flaky tests out of the pipeline

Perform functional, regression, exploratory, and smoke testing across web and API layers

Use AI tooling to accelerate test design and coverage analysis, while applying your own judgment on what actually needs human eyes

Reproduce, isolate, and report bugs with the detail developers need to fix them fast

Collaborate with developers and PMs during design — flag testability and edge-case risks before code is written

Contribute to release sign-off decisions with data, not gut feel