QA Automation Engineer - Full Stack

Pay Theory; Deutschland; Vor Ort; EUR 55.000 - 75.000; Vollzeit

Zusammenfassung

A Pay Theory está em busca de um Engenheiro de Qualidade para expandir a engenharia de qualidade em serviços backend e portais frontend. Você deve liderar a automação e garantir a estabilidade dos testes, com um enfoque significativo na resolução de problemas de flutuação nos testes.

Procuramos um profissional com experiência em TypeScript e frameworks de teste modernos, capaz de trabalhar em um ambiente dinâmico. É necessário fluência em inglês (C1 ou superior) para interações com engenheiros dos EUA.

Qualifikationen

• 3-5 anos em SDET, QA Automation ou papel equivalente.
• Fortes habilidades em TypeScript.
• Experiência prática com uma estrutura de teste moderna.

Aufgaben

• Possuir e expandir engenharia de qualidade em serviços backend.
• Liderar esforços para identificar e eliminar testes instáveis.
• Otimizando o repositório de testes end-to-end.

Kenntnisse

API

JavaScript

Quality Assurance

TypeScript

Tools

Vitest

Jest

Playwright

AWS Lambda

GitHub Actions

Bash

Jobbeschreibung

Habilidades

API, JavaScript, QA - Quality Assurance, TypeScript

O que nós buscamos

WHAT YOU'LL DO

Own and expand quality engineering across our backend services and frontend portals. Drive automation expansion in repositories that lack adequate coverage, prioritizing high‑risk and high‑traffic surfaces. Lead the effort to identify, triage, and eliminate flaky tests — treating flakiness as a first‑class engineering problem rather than background noise. Own QA gates in the release process — define and enforce what "ready to promote" means as code moves through environments. Take ownership of our central end‑to‑end testing repository, optimizing its runtime, reporting, and coverage. Extend our testing tooling and CI/CD pipelines — this is a builder role, not a maintainer role. We expect you to ship framework code, not just consume what's already there. Scope and lead a contract testing rollout across our service‑to‑service interfaces. Partner with engineering early — review designs and technical specs for testability before code is written. Codify regressions after incidents — when bugs reach production, ensure the same class of bug can't recur silently. Collaborate with infrastructure and operations on CI/CD reliability, test runtime, and runner stability.

YOUR FIRST 90 DAYS

• Days 1–30: Become fluent in our testing infrastructure and tooling. Run our test suites end‑to‑end across pre‑production environments. Shadow a release cycle.
• Days 31–60: Ship meaningful new coverage in at least two service repositories. Begin instrumenting flaky‑test detection. Start contributing to our central end‑to‑end testing repository.
• Days 61–90: Take full ownership of the central end‑to‑end testing repository. Propose and begin executing a CI/CD QA improvement plan. Deliver a recommendation on the contract testing rollout.

Principais responsabilidades

WHAT WE'RE LOOKING FOR

• 3–5 years in an SDET, QA Automation, or equivalent role on a production SaaS product.
• Strong TypeScript skills — our integration test layer is TS‑based regardless of the underlying service language.
• Hands‑on experience with a modern testing framework (Vitest, Jest, Playwright, or similar).
• AWS Lambda or serverless testing experience — comfortable with mocking, event‑driven flows, async retry behavior, and using cloud logs as a debugging surface.
• REST and GraphQL contract and integration testing experience.
• Bash fluency — comfortable reading and extending shell scripts.
• CI/CD pipeline ownership experience (GitHub Actions or comparable) — matrix strategies, artifact passing, runner concurrency.
• A track record of measurably reducing test flakiness in a prior role.
• Reads Go and Python well enough to add unit tests, debug failures, and review test PRs. You don't need to ship feature code in either language.
• Clear written communication — bug reports, test plans, and release sign‑offs that engineers and non‑engineers can both act on.
• Fluent English (C1 or higher) — near‑native written and spoken. You can lead technical discussions, write test plans and bug reports, and pair with US‑based engineers in real time without friction.

NICE TO HAVE

• Multi‑tenant or multi‑environment test design experience.
• Prior ownership of a shared or central test harness used across multiple service repositories.
• Familiarity with capability‑based or tag‑based test selection.
• Experience with idempotency, retry, and webhook‑replay testing patterns.
• Prior involvement in a Pact or contract testing rollout.
• Payments, banking, or other regulated‑industry exposure.
• Experience building test reporting dashboards or surfacing test health metrics to engineering leadership.
• Familiarity with feature‑flag‑driven rollout patterns.
• Comfort with AI‑assisted development tooling.