QA Automation Engineer — Cebu-Based (Remote + Hybrid)

About the Role

LEADAI is a voice-AI startup shipping real products people use. We move quickly and care about reliability. You’ll build the automation and monitoring that lets us ship with confidence—owning tests, synthetics, and release gates—and grow into a key stakeholder who shapes how we build.

Location & Work Setup

• Must be based in Cebu (non-negotiable)
• Remote day-to-day
• In-person in Cebu for sprint planning/retros/workshops (hybrid cadence)

Why This Opportunity

• Real ownership: your signals decide when we ship
• Interesting, practical scope: voice, web, APIs, webhooks
• Learn by doing: start simple, layer in more as we grow
• Tight feedback loops with founders and senior devs

What You’ll Do

• Build and maintain browser E2E tests (Playwright or Cypress, TypeScript/JS) for top flows (e.g., login → place call → webhook confirm)
• Add a handful of API checks (auth, happy/negative cases, clear assertions)
• Set up scheduled synthetic checks (every 5–10 minutes) with actionable Slack/email alerts
• Wire observability: enable Sentry for errors/release health and stand up a lightweight dashboard (Grafana Cloud / New Relic / Datadog) for latency/error/synthetic signals
• Add a basic release gate in CI (GitHub Actions) so obvious regressions don’t reach users
• Write concise runbooks (“when this turns red, try this”) so anyone can fix common issues fast

What You Won’t Be Stuck Doing

• Endless manual regression marathons
• Maintaining a giant, flaky suite nobody trusts
• Writing reports nobody reads—we focus on crisp signals and shipping fixes

Must-Have Skills (Baseline)

• TypeScript/JavaScript and hands-on Playwright or Cypress (selectors, fixtures, parallel runs, basic deflaking)
• API testing with auth and clear assertions
• CI basics (GitHub Actions or similar): run tests on PRs and block merges on red checks
• Comfortable reading a dashboard and wiring Slack/Email alerts
• Clear written notes—bugs, reproduction steps, short runbooks

Nice-to-Haves (Okay to Learn Here)

• Sentry (errors & release health)
• Observability: Grafana Cloud / New Relic / Datadog; some OpenTelemetry for adding spans/attributes
• Synthetics: Checkly or Grafana Cloud Synthetics (scheduled browser/API checks)
• Feature flags: OpenFeature/flagd; basic circuit-breaker patterns
• Familiarity with Next.js and Supabase

Tools You’ll Touch Here

Playwright or Cypress (TS/JS) • Sentry • Grafana Cloud or New Relic or Datadog • GitHub Actions • (optional) Checkly • OpenFeature/flagd

What Success Looks Like (Step-by-Step Progress)

• Sentry enabled across key services
• A reliable set of E2E and API checks covering our most important journeys
• 24/7 synthetic checks with actionable alerts the team trusts
• A clean dashboard highlighting p95 latency, error rate, and synthetic pass rate
• A release gate protecting at least one mission-critical flow
• Two short runbooks engineers actually use during incidents

How We Work

• Startup pace, human process: short cycles, clear ownership, quick decisions
• Pragmatic standards: small, reliable suites over sprawling flaky ones
• Collaboration over ceremony: pair when needed; document what matters

• Must be based in Cebu, Philippines (non-negotiable)
• Remote day-to-day; willing to join in-person sessions in Cebu for sprint planning/retros/workshops

Required Qualifications

• Proficiency in TypeScript/JavaScript
• Hands-on with Playwright or Cypress (solid selectors, fixtures, parallel runs, basic de-flaking)
• API testing experience (incl. auth, happy/negative paths, clear assertions)
• CI basics (GitHub Actions or similar): run tests on PRs and block merges on failing checks
• Comfortable reading an observability dashboard and wiring Slack/Email alerts
• Clear written communication: concise bug reports, repro steps, and short runbooks

Preferred (Nice-to-Have)

• Sentry (errors & release health)
• Observability with Grafana Cloud / New Relic / Datadog; some OpenTelemetry (spans/attributes)
• Synthetics: Checkly or Grafana Cloud Synthetics (scheduled browser/API checks)
• Feature flags: OpenFeature/flagd; basic circuit-breaker patterns
• Familiarity with Next.js and Supabase