Senior Quality Engineer

Job description

**About us:** How did Web Summit become, in the words of Forbes, “the best tech conference on the planet”? Meaningful connections. Our tech events are unmissable because we make it easier for the right people to meet and connect. Everyone at Web Summit works towards this goal. [And we’re just getting started.](https://www.youtube.com/watch?v=jaey4uZVEjk) We’re always looking to build on the impact we have already made at Web Summit. In the coming years we’ll take Web Summit to new markets, promoting global connectivity, highlighting important issues and connecting global leaders – all while making a positive impact on the environment and communities we encounter. To build a better company, we have to better ourselves. We do that by finding the most ambitious people to work with us. **About us:** Web Summit brings together founders, investors, speakers, partners and attendees at technology events around the world. We're headquartered in Dublin, with engineering teams in Dublin, Lisbon and throughout Europe. We build our own software because tightly integrated software lets us run the best events in the world. Our software helps attendees prepare, find relevant people and activities, and make connections. **About you:** Every attendee's journey, from buying a ticket to walking through the door, crosses a Rails monolith, native mobile apps, a React Native registration and access app, a CRM and a ticketing pipeline, built by several small teams. What breaks usually breaks between them. The whole thing gets its real test a few days a year, when tens of thousands of people arrive at the doors at once. As our first Senior Quality Engineer, you'll work across those teams as a hands-on engineer, building the tests, data and tools they use to show a release works end to end. The teams stay responsible for what they ship. You make it easy for them to know it works. ### What you'll achieve - 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. ### Who you are - 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. ### What we're looking for - 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. Stack: a Rails monolith, PostgreSQL, Sidekiq. Native Swift and Kotlin apps with Maestro, the React Native app, Salesforce, CircleCI and feature flags. Claude Code and Cursor in daily use.