Open Vacancies at LeverX - Join the team of talented software professionals

SAP Automation Engineer | Work at LeverX

Written by Danuta | Aug 26, 2025 6:48:26 AM

At LeverX, we have had the privilege of working on over 950 SAP projects, including some with Fortune 500 companies. With 20+ years in the market, our team of 2,200 is strong, reliable, and always evolving: learning, growing, and striving for excellence.

We are looking for an SAP Automation Engineer to join us. Let’s see if we are a good fit for each other!

we offer:

  • 89% of projects use the newest SAP technologies and frameworks, e.g., S/4HANA Cloud, BTP, CPI, RAP, CDS, and OData.
  • 98% of active development projects, with rare short-term support contracts.
  • Expert communities and internal courses.
  • Market-based compensation and regular performance reviews.
  • Valuable perks to support your growth and well-being.


    required skills:

  • 3-5 years as an SAP Test Automation Engineer with strong testing methodology (test design, page/screen objects, data-driven tests) and Agile experience.
  • Familiar with SAP landscape (Fiori, SAPUI5, launchpad, roles/authorizations, SSO).
  • Hands-on with QMate (writing, running, debugging tests, selectors, helpers) and WebDriver.
  • Proficient in JavaScript/TypeScript, Node.js, OOP, and Visual Studio Code.
  • Experience integrating WDIO/QMate into pipelines (Jenkins, GitLab, GitHub Actions), managing artifacts, reports (e.g., Allure).
  • Solid Git skills (branching, PR reviews, code quality tools).
  • English B1+.

nice-to-have skills:

  • Experience with UI5 mock server utilities in QMate and synthetic data generation.
  • Experience with Dockerized test runs (containerize WDIO/QMate, run headless in CI).
  • Awareness of basic checks or hooks in pipelines.

responsibilities:

  • Build and maintain an automated regression suite for SAPUI5/Fiori apps using QMate + WDIO.
  • Define test strategy, coverage, and critical paths; collaborate with QA/Dev/PO for acceptance criteria and stable IDs.
  • Create reliable selectors using view names/metadata/IDs; refactor to page objects; keep tests deterministic.