Position Overview
As a Player-Coach Test Engineering Lead, you will lead a geographically distributed test engineering team while remaining a hands-on architect, coder and troubleshooter. You will own the engineering of a CI/CD-native quality system for cloud-based voice, media and contact-center platforms: functional automation, protocol- and traffic-level validation, synthetic monitoring, performance and chaos engineering. You will also transform conventional QA into an AI-enabled, continuously validating engineering capability. This is a player-coach role in a fast-paced, startup-like environment—not a coordination-only test management position.
Responsibilities
- Lead, mentor and grow a remote/distributed automation team; establish standards, technical direction, code review, delivery accountability and a visible engineering backlog while contributing production-quality code.
- Architect and implement Playwright-based UI/API automation, contract and integration tests, service-level tests, and end-to-end customer journeys. Select complementary tools for protocols and real-time media where browser automation is insufficient.
- Embed tests into GitHub Actions/Jenkins/Argo CD and GitOps delivery gates: pull-request checks, ephemeral environments, deployment verification, risk-based suites, release qualifications and fast failure feedback.
- Build reliable voice/media/contact-center test harnesses covering SIP signaling, RTP/SRTP media, WebRTC, IVR, agent interactions, call routing, conferencing, transfers, hold/resume, recording and messaging where applicable.
- Engineer continuous traffic generation and synthetic journeys across calling, messaging and API workflows; correlate functional outcomes with signaling traces, media quality, logs, infrastructure and service telemetry.
- Own performance engineering: workload modeling, load/stress/soak testing, concurrency, throughput, queue depth, latency, resource saturation, capacity limits and customer-experience thresholds.
- Introduce chaos/fault-injection scenarios (node failures, network impairment, dependency loss, rate limiting, failover, degraded media) with explicit blast-radius and rollback safeguards.
- Build agentic workflows for test generation, execution orchestration, flaky-test diagnosis, selective retesting, impact analysis, root-cause hints and self-healing pipelines; require auditable, reviewed repairs rather than silent assertion weakening.
- Drive observability-led troubleshooting using Prometheus, Grafana, Loki, Thanos, Alloy, OpenTelemetry, traces, packet captures and traffic analysis; debug failure across browser, API, network, Kubernetes, services and databases.
- Partner with platform, SRE, CloudOps, application engineering, security and release teams on security, zero trust, FedRAMP/PCI DSS/SOC 2 evidence, test-data protection and release readiness.