Position Responsibilities
We’re building a culture where quality is not a gate,but a capability—powered by automation, clear systems, and shared ownership across teams—so we can move fast while maintaining a high bar for reliability. As a QA Team Lead, you will play a central role in making this real. You will design and build systems that enable teams to ship with confidence—embedding quality into the development lifecycle rather than treating it as a final step. This is a hands-on leadership role. You’ll work closely with product, design, and engineering to define how quality is owned and executed across squads, while also contributing directly through automation, tooling, and observability. Over time, you will help establish and grow a scalable quality engineering function that supports the organization as it scales.

What You’ll Do:

• Build and evolve test automation frameworks across frontend and backend systems
• Define and drive test strategy and planning with engineering squads
• Review releases and provide risk-based quality assessment before deployment
• Design and implement observability and performance monitoring systems to detect regressions early
• Partner with engineers to shift quality left into development rather than post-development testing
• Establish quality standards, practices, and tooling across multiple squads
• Mentor and uplift QA engineers, while actively contributing hands-on work
• Help engineering teams improve delivery reliability and reduce production incidents.

Qualification and Experience

What You Bring:

• Strong experience with test automation tools such as Playwright, Cypress, or Selenium
• Solid understanding of API testing tools like Postman or REST Assured
• Experience working with Ci/CD pipelines (GitHub Actions, GitLab CI, or similar)
• Familiarity with observability tools such as Datadog, New Relic, Grafana, or OpenTelemetry
• Ability to integrate testing and quality checks into modern delivery pipelines

• 8‒12 years of experience in software quality, QA engineering, or test automation
• Background in startup or product engineering environments where systems are evolving rapidly
• Experience operating in environments with immature or evolving QA processes, and building structure from scratch
• Bonus: experience scaling QA systems or internal quality platforms in high-growth team

• Strong ability to communicate and collaborate across product, design, engineering, and QA
• Comfortable influencing without authority across multiple squads
• Strong systems thinking—you design frameworks, not just test cases
• Pragmatic decision-making around speed vs. quality tradeoffs
• Ability to coach engineers on quality ownership, not just enforce testing practices
• Strong bias for action in ambiguous environment

• Quality becomes a shared engineering responsibility, not a QA bottleneck
• Automated coverage significantly increases across critical system paths
• Production issues and change failure rate are materially reduced
• Teams gain early visibility into risk through testing + observability systems
• Engineering squads actively incorporate quality thinking into development cycle

• Prefer building systems over executing tickets
• Take ownership of outcomes, not just test execution
• Are comfortable operating without rigid structure
• Care about real-world reliability over theoretical perfection
• Move quickly, experiment, and improve systems iteratively

• Prefer strict direction and predefined QA processes
• Focus mainly on manual or isolated testing work
• Are uncomfortable working across multiple squads and stakeholders
• Prioritize process over delivery impact