Software Development Engineer in Test (Luma)

We are seeking an SDET to join one of our agile engineering teams and help us build quality into LUMA, our scientific software platform. You’ll take ownership of testing for a specific module of the application — writing and maintaining automated tests, exploring new features, and working alongside developers, application scientists and DevOps engineers to make sure what we ship is reliable

This is a hands-on automation role with room to grow. You’ll be contributing to established test frameworks rather than building them from scratch, with support from senior SDETs who will help you develop your technical depth and your understanding of the science behind the product

While the primary focus is automation, the role also involves manual exploratory testing

Write, maintain and extend automated test suites for your module using Cucumber, TypeScript and Cypress (and Playwright where we use it)

Own day-to-day quality for your area: contributing test scenarios during planning, testing stories as they’re built, and giving the team a clear picture of release readiness

Design and document test cases that cover functional, regression and integration scenarios, and keep them useful as the product evolves

Investigate and reproduce defects, raise well-evidenced bug reports in JIRA, and verify fixes with developers and scientists

Keep your tests green and trustworthy in our CI pipelines, and help improve how tests run and report

Learn to read and interpret API documentation and turn it into meaningful automated coverage

Work with leading experts in software development, scientific product management and test automation — and be mentored by them- Just as importantly, you want to get better

We’re looking for someone who takes feedback well, is curious about the scientific problems our users are solving and wants to grow into a senior automation engineer over time

You’re comfortable working in a code-first way, you enjoy digging into how things work, and you’re happy asking questions when a domain is unfamiliar

You work carefully and pay attention to detail, and you can take a story or module, understand it and devise a concrete approach to testing going above and beyond the standard acceptance criteria

You’ll have 2–5 years’ experience in QA/testing, including at least a year of hands-on test automation

Experience with BDD / Cucumber, or a willingness to pick it up quickly — we write most of our specs in Gherkin

Working knowledge of TypeScript or JavaScript, including asynchronous code (promises, async/await). You don’t need to be an expert in generics and interfaces, but you should be able to read and write clean, maintainable test code

Practical experience with Cypress — writing tests, using selectors and custom commands, debugging failures, and working within an existing Page Object Model. Experience testing React applications is a plus

Comfort with Git and GitHub, including branching, pull requests and code review, plus experience working in JIRA or a similar tracking system

Test case design and documentation — the ability to break a feature down into clear, repeatable scenarios and write them up so others can follow them

Experience with Playwright, or interest in learning it — we use it for a subset of our tests

Any experience with performance or load testing (K6 or similar)

Exposure to API testing tools (Postman, REST clients) or writing API-level automated tests

Familiarity with validating data integrity across release upgrades, migrations or schema changes

A background or interest in science, engineering or research software