> Markdown version of [/jobs/ext/4652656-test-engineer](https://www.wearedevelopers.com/jobs/ext/4652656-test-engineer). 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).

---

# Test Engineer

- **Company:** Latchform
- **Location:** Hamburg, Germany (Remote available)
- **Contract:** Permanent contract
- **Skills:** JavaScript (Programming Language), Application Programming Interfaces (APIs), Automation of Tests, Burp Suite, OAuth, Openid Connect, Software Engineering, Test Data, Postman, Git, Pytest, Bug Reporting, Information Technology, Playwright, Restful APIs
- **Published:** November 10, 2026
- **Apply:** https://www.adzuna.de/details/5959909243

## About the Role

* A degree in computer science, software engineering or a related field, or comparable training
 * Experience writing automated tests (pytest, Jest, Playwright or similar) in a job, an internship or a project
 * You can call and read a REST API: methods, status codes, headers and tokens
 * Git

Also counts
Burp Suite, OAuth 2.0 and OpenID Connect, the ISTQB Foundation certificate, a CI pipeline you set up yourself.

## Description

Hamburg, 20095
Unbefristet
Vollzeit
More of the product teams that ask us for a review sell to German customers, and their engineers often work in Germany too. So our next Test Engineer will be based there. The job is full-time and remote from anywhere in Germany; the rest of Latchform works from San Francisco, nine hours behind, so team calls land in your late afternoon.

A broken access check is only useful to a client if their engineers can reproduce it and keep it fixed. You turn our findings into tests they can run.

In scope

 * Write reproduction steps and automated API tests for each finding, against the client's staging environment and test tenants
 * Check role and tenant boundaries request by request with Postman or Burp Suite
 * Retest fixed findings at the follow-up and record what changed
 * Keep the test accounts and test data of each review in order
 * Write the testing notes that go into the report