Middle QA Automation Engineer (Python + Playwright)

A project where tests actually matter

Tired of automating meaningless UI forms while your tests break with every release?
 

Let’s change that.

We’re hiring a QA Automation Engineer for our trusted European product partner (iGaming industry — online casinos, betting systems). You’ll help migrate from Java/Selenium to Python/Playwright and build a robust, modern QA process.
 

This is not just another “test this button” job. It’s long-term, tech-driven, and fully remote — with a team that respects testing and builds with quality in mind.
 

Your impact:

  • Develop and maintain automated tests for API and UI (Playwright, pytest)
  • Analyze requirements, write test cases and checklists that actually make sense
  • Integrate your tests into the CI/CD pipeline (GitHub Actions)
  • Collaborate directly with developers — not just receive tasks
  • Report bugs, track issues in Jira, and generate test reports in TestRail
  • Support the migration of tests from Java/Selenium to Python/Playwright
     

Tech Stack:

  • Python 3.9+
  • pytest, Playwright, Selenium
  • REST API testing with requests, Postman, Swagger
  • GitHub Actions
  • Git (pull requests, code review, branching)
  • Docker, Kubernetes
  • Jira, TestRail, Confluence
     

 What we’re looking for:

  • 2+ years of experience as a QA Automation Engineer using Python
  • Hands-on knowledge of pytest and Playwright
  • Solid understanding of REST API testing
  • Experience in building and maintaining automation for both API and UI
  • Familiarity with CI/CD workflows (GitHub Actions or similar)
  • Confident with Git-based collaboration
  • Good grasp of testing theory: types, levels, techniques
  • Ability to write proper test documentation (cases, checklists)
  • Comfortable working in Agile/Scrum environments
     

Nice to have:

  • Basic understanding of Java
  • Experience with Lens or other Kubernetes monitoring tools
  • Background in gambling platforms, online casinos, or sportsbook systems
  • Experience with writing or managing mocks/stubs for external services
     

What you’ll get:

  • A long-term product role — not project-based, not a startup in survival mode
  • A chance to modernize automation and ditch legacy tools
  • A tech-friendly environment with mature processes and no micromanagement
  • Fully remote work with flexible hours
  • Direct communication with the product team — no middle layers
  • Full context before the interview: tech info, team structure, and expectations
     

📩 Ready to write tests that actually get used and valued?

Let’s talk. We’ll walk you through the role, tech challenges, and growth potential — no fluff, just the truth.

Published 12 April
147 views
·
38 applications
98% read
·
95% responded
Last responded 2 weeks ago