Senior Quality Engineer

Give every team the confidence to ship more often, because they'll know when something breaks.

Build a repeatable end-to-end test, with realistic data, for the journeys that matter most: registration, login, ticket assignment and entry.

Build test identities and event-like data that every team can use.

Run the whole flow across the mobile apps and the services behind them, every week.

Give the team shipping a release clear evidence of what it depends on.

Work on site at events, watch what happens at the doors, and turn what you learn into a test, a monitor or a written decision.

You judge a test by the impact a failure would have on our users, not by a coverage number.

You're curious about the gaps between systems and about users who don't do what we expect.

You'd rather teach five teams to test than build tests for five teams.

You share what you know.

You'd rather be pretty sure this week than absolutely sure next quarter.

You can tell someone their release is at risk and still be welcome at their standup.

Strong programming skills and a record of building test software other engineers keep using.

Experience testing journeys across APIs, services, web or mobile clients and third-party systems, and judgement about which layer to test what at.

Experience creating reusable test data and environments, and running automated tests in CI/CD.

Experience investigating failures with logs, monitoring and crash reports, and explaining the risk plainly to engineers and non-engineers.

Comfortable using AI tools to write and maintain tests.

Working ability in at least one of Ruby, JavaScript, Swift or Kotlin, and able to read the others. Mobile automation such as Maestro would help.