> Markdown version of [/jobs/ext/2158465-qa-engineer-sdet-risk-decision-workflow](https://www.wearedevelopers.com/jobs/ext/2158465-qa-engineer-sdet-risk-decision-workflow). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # QA Engineer (SDET) - Risk Decision Workflow - **Company:** Gruner + Jahr AG & Co KG - **Location:** Berlin, Germany - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** JavaScript (Programming Language), .NET Framework, Application Programming Interfaces (APIs), Artificial Intelligence, Confluence, JIRA, Automation of Tests, Unit Testing, Microsoft Azure, C Sharp (Programming Language), Continuous Integration, DevOps, JSON, Apache JMeter, PostgreSQL, Nunit, Azure DevOps Pipelines, Standard Sql, Software Engineering, Systems Integration, Test Data, Test Management, TypeScript, YAML, Performance Testing, Postman, Cypress (Programming Language), Git, Xunit, Gherkin, Apache Kafka, Restful APIs, Terraform, Software Version Control, Atlassian Bamboo, Docker, Key Vault, SDET - **Published:** August 21, 2026 - **Apply:** https://jobsearch.createyourowncareer.com/talentcommunity/apply/1428529633/?locale=en_US ## About the Role What will help you to succeed in the role: * 5+ years as SDET / QA Engineer / Quality Engineer, with automated tests in production CI * Solid knowledge of testing types and methods, and the judgment to choose unit vs integration vs functional vs E2E vs performance vs exploratory. * Strong experience testing complex APIs and integrations (auth, persistence, downstream HTTP, messaging). Comfort reading YAML/JSON configs and tracing behaviour across services. * Proven delivery of automated suites and, ideally, shared test libraries or pipeline templates - not only one-off scripts. * CI/CD, source control, and dependency management as a normal part of the job. Experience in a DevOps-style team. * BDD/Gherkin experience is useful (Xray/Reqnroll). It is not the only style we use; most new service tests are NUnit/xUnit. Comfort with mixed unit/integration/functional/E2E/performance tests across repos. * Curiosity about AI-assisted testing is a plus. Willingness to review, correct, and constrain generated tests is required. * As a person you are self-driven, proactive, and able to talk to both business and engineering stakeholders and fluent in English. ## Description Riverty's customers depend on accurate, consistent credit and payment risk decisions. In Risk Decision Workflows, quality is not a late-stage check: it is built into APIs, decision workflows, mocks, pipelines, and test evidence in Jira/Xray. We are looking for someone who combines a tester's judgment with an engineer's delivery habits: you write tests, you make services testable, and you keep CI honest. What will be your challenge: As a QA Engineer, you will develop software for testing - automated tests, shared libraries, mocks, and pipeline stages - and you will keep the Risk platform's quality visible to the team and the product owner. Day to day you will: * Plan and own test automation for existing and upcoming Risk work: unit tests, in-process functional/API tests, workflow/E2E coverage, and performance tests. * Design and implement tests for complex REST APIs and for Zoral Decision Engine (ZDE) workflows (authorization, creditworthiness, address/bank validation, and related Master decisions). * Keep services testable with developers: `WebApplicationFactory`, Testcontainers, PostgreSQL, WireMock, Docker Compose, and seeded test data. * Integrate and maintain automated tests in Azure Pipelines, including shared test templates, coverage, ReportPortal, Allure, and nightly Postman runs. * Own Xray/Jira traceability: review generated and handwritten cases, implement them in code, and keep reporting mapped to tickets and test plans. * Use and improve the team's AI-assisted QA workflow. You remain the reviewer; the agent is not a replacement for judgment. * Maintain test architecture and team conventions so new tests stay consistent across repos. * Work with mock/stub data providers used by functional and performance testing. * Brainstorm upcoming work with the team, keep quality in the design conversation, and mentor others on testing approaches and tooling. * Give the product owner a clear view of current quality status and the test plan for upcoming work. You will be using technologies: * Languages: C# / .NET, JavaScript / TypeScript, SQL * API & workflow testing: NUnit, xUnit, Postman / Postman CLI, HTTP clients, Gherkin/Xray * BDD / shared test libraries: Reqnroll, Testing Commons, AI agents * Test infrastructure: Docker, Docker Compose, Testcontainers, WireMock, PostgreSQL, mock external providers * CI/CD & Azure: Azure DevOps Pipelines, Azure (Key Vault, storage, ACR), Git, Terraform * Reporting & test management: Xray, ReportPortal, Jira, Confluence * Performance k6 and/or JMeter * Nice to have: Cypress, Kafka consumer testing, Responsible for processing the information provided in your application is the company specified in the job advertisement, with its registered office as indicated. The company processes your data for the purpose of establishing an employment relationship on the basis of Art. 6 (1) b GDPR / Section 26 (1) sentence 1 BDSG. The retention period for your data is determined by the statutory time limits applicable in the respective country, beginning upon completion of the recruitment process. You can find these here. ## Related Videos - [CI/CD with Github Actions](https://www.wearedevelopers.com/videos/856-ci-cd-with-github-actions) - [How a Small Team Shrank a Microsoft Monorepo by 94%](https://www.wearedevelopers.com/videos/1236-how-a-small-team-shrank-a-microsoft-monorepo-by-94) - [Continuous testing - run automated tests for every change!](https://www.wearedevelopers.com/videos/190-continuous-testing-run-automated-tests-for-every-change) - [Docker Compose: Rediscovered](https://www.wearedevelopers.com/videos/1978-docker-compose-rediscovered) - [Git for Code Reviews](https://www.wearedevelopers.com/videos/429-git-for-code-reviews) - [How I Built QA from Scratch in a Scaling Startup - no fluff real life story](https://www.wearedevelopers.com/videos/2041-how-i-built-qa-from-scratch-in-a-scaling-startup-no-fluff-real-life-story) ## Related Articles - [The 8 Best Code Testing Tools](https://www.wearedevelopers.com/magazine/402-the-8-best-code-testing-tools) - [Where To Find Software Engineering Jobs](https://www.wearedevelopers.com/magazine/396-where-to-find-software-engineering-jobs) - [The 12 Best Jobs for Software Engineers](https://www.wearedevelopers.com/magazine/401-the-12-best-jobs-for-software-engineers) - [The Biggest German Tech Companies](https://www.wearedevelopers.com/magazine/424-the-biggest-german-tech-companies) - [The Most Popular IT Jobs on the Market](https://www.wearedevelopers.com/magazine/376-the-most-popular-it-jobs-on-the-market) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline)