We're looking for a Staff Automation Engineer to own and scale automated testing infrastructure end-to-end.

This is not a traditional QA role focused only on writing test cases.

You will define automation architecture, build and maintain scalable frameworks, and own the CI/CD systems supporting automated testing across the engineering organization.

This role requires deep expertise in Playwright, TypeScript, and CI/CD, along with strong infrastructure ownership.

Location: Tashkent, Uzbekistan (On-site)

What You'll Do

• 
  Own the architecture and evolution of test automation infrastructure
• 
  Design, build, and maintain scalable end-to-end test frameworks using Playwright and TypeScript
• 
  Integrate automated testing into CI/CD pipelines and deployment workflows
• 
  Improve test reliability, execution speed, and maintainability
• 
  Build and optimize test environments, reporting, parallelization, and diagnostics
• 
  Improve release confidence through robust automation and infrastructure improvements
• 
  Partner closely with engineering teams to improve developer workflows and product quality
• 
  Establish best practices for automation architecture, test strategy, and infrastructure ownership
• 
  Troubleshoot flaky tests, pipeline failures, and automation bottlenecks

Requirements

• 
  Strong hands-on experience with Playwright and TypeScript
• 
  Strong knowledge of CI/CD systems and automation integration
• 
  Experience owning or designing test automation infrastructure
• 
  Experience building scalable automation frameworks, not just maintaining test suites
• 
  Strong debugging and problem-solving skills
• 
  Experience improving test reliability, performance, and pipeline stability
• 
  Ability to work closely with software engineering and DevOps teams
• 
  Strong ownership mindset and systems-thinking approach

Nice to Have

• 
  Experience with Docker or Kubernetes
• 
  Experience with GitHub Actions, GitLab CI, Jenkins, or similar tools
• 
  Experience with large-scale web applications or distributed systems
• 
  Exposure to observability or monitoring tools
• 
  Experience in fast-paced product or startup environments