Support Systems Engineer

We are building AI to simulate the world through merging art and science.

We believe that world models are at the frontier of progress in artificial intelligence. Language models alone won’t solve the world’s hardest problems – robotics, disease, scientific discovery. Real progress requires models that experience the world and learn from their mistakes, the same way that humans do. And this kind of trial and error can be massively accelerated when done in simulation, rather than in the real world.

World models offer the most clear path to general-purpose simulation, changing how stories are told, how scientific progress is made and how the next frontiers of humanity are reached.

Our team consists of creative, open minded, caring and ambitious people who are determined to change the world. We aspire to continuously build impossible things and our ability to do so relies on building an incredible team. If you are driven to do the same, we'd love to hear from you.

*Titles posted to our careers page are updated regularly to best advertise the role and expected seniority, but internally we have a flat titling system with two types of titles: one for individual contributors and one for people managers.

About the role

Open to hiring remote across North America and London — we also have offices in NYC, San Francisco, Seattle, and London.

We're building a tool that makes content creation easy and accessible for all types of creatives. Our users love it. Runway has an actively engaged and growing community of passionate artists and creators worldwide. And we're scaling the systems behind our support team so we can keep delivering delightful experiences as that community grows.

We're looking for a Support Systems Engineer who ships production code, not tickets and specs: someone who takes a fix from proposal to merged PR themselves. This role reports directly to the Head of Customer Experience.

What you’ll do

• Own the AI support agent, our ticketing system and other Support tools end to end: authentication (JWT), response logic, routing, escalation paths and tone, tested in staging before it sees live traffic

• Ship daily product changes that remove ticket volume. Recent example: extending automatic refund eligibility to one-click credit purchases, accidental upgrades and month-based proration on annual terms

• Build and maintain internal CX tooling as real software, not one-offs: scripts, jobs, dashboards, admin surfaces

• Run QA and evals with real test suites and pass/fail rubrics, plus monitoring and alerts for outages, bugs and volume spikes

• Own releases: staged rollouts, a regression suite before every ship, clear rollback criteria, a writeup when something reaches production