
Runway (NYC) Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 76 interview experiences · FREE TO READ
Which role are you interviewing for?
21 roles · 76 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Runway (NYC).
Enterprise GTM
This interview process felt like they were trying to extract as much info as possible from experienced AEs while they figure out their GTM strategy and product-market fit. It started with a recruiter screen, which was standard. Then a hiring manager chat that was more conversational and behavioral. Next, a written assignment that was expected to take 2-4 hours, involving significant research on the company and how Runway's product stands out. The final stage was presenting this assignment, but only if they liked your written work. It felt a bit strange: 'do 4 hours of work, and if we like it, you get to present it.' The questions focused on how I'd build out their GTM motion, strategy, and competitive landscape, rather than my past experiences. They wanted to know what I *would* do, not what I *have* done. I didn't proceed to the next stage and asked for feedback after putting in over 10 hours, but got nothing back. It's a tough market and product to sell, and they haven't found PMF yet, with no clear business case. The people seemed nice, but I'd be hesitant to join unless you're really keen on building something in a very competitive new space.
- In a competitive deal, how would you position Runway against Veo3 and Sora?
- What steps would you take to build a business case that supports Runway's pricing?
Software Engineer
My interview process with the Runway team was really smooth and they were super supportive as I figured out where I wanted my next role to be. The team was really clear upfront and throughout the whole process about what I'd be interviewed on, giving me info on who I'd meet and the expected timelines. They were also really flexible with my schedule. The interview process was quite thorough, involving meetings with several team members from different departments, which I really liked because it was a great way to meet the various people I'd be working with across the team. Can't wait to join this super ambitious, smart, and friendly team!
- Can you design the system and software architecture for a video editing web app?
Engineering Manager
The whole process felt really put together and effective. Recruiting did an amazing job with all the scheduling and making sure everything ran smoothly. They were always quick to respond and I knew what was coming next. The tests included designing a system, a coding problem, reviewing some code, and a bunch of chats with different leaders. The tasks were tough but felt like what the job actually entails. You could tell they put a lot of thought into them. Everyone I met was great – smart, driven, but also down to earth. The more I went through the steps, the more I liked the idea of working there.
- Can you design a system for processing data at a large scale?
- Here's a coding challenge for you.
- Let's do a mock code review.
Enterprise Go-to-Market
The interview process involved a few stages. First, a recruiter screen (30 min) was a basic check on background and role fit. Then, a hiring manager chat (30 min) went deeper into my experience, territory, ICP, and deal process. Next, I completed an asynchronous case study where I had to propose a use case for an AI product in a new market, delivering a memo or deck showing my strategy. Finally, there was a panel mock interview (30 min total) that was supposed to be 10 min discovery, 10 min product walkthrough, and 10 min Q&A. However, during the panel, the hiring manager cut off the discovery part early and steered it towards a live demo, not following the advertised structure. Some parts worked well, like the clear early stages and case study prompt, and the initial chats felt efficient. But the panel dynamics were tough, with the manager changing the flow and the tone feeling confrontational, which didn't feel like real enterprise sales interactions. It seemed more like a stress test with unclear rules or maybe they already had a top choice. The assessment also focused too much on handling interruptions instead of core sales skills. I even had to pay for product credits for the demo, which was unexpected. The whole panel experience made me question the company's leadership and decision-making because the actual execution didn't match the stated format. I ended up accepting another offer the next day.
- Could you outline a proposal, either a short memo or a slide deck, addressing the following points for an AI product in an untapped market?
- What specific segment or use case are you suggesting?
- What makes this proposal relevant and timely right now?
Runway (NYC) Interview Questions
Quoted word for word from Runway (NYC) interview reports.
“Write Python code to complete a task, and add tests for it.”
Read reports →“Can you design a system to retrieve videos for all users on a website?”
Read reports →“Can you design a system that takes a movie and intelligently outputs clips for a trailer?”
Read reports →“Given a small React spreadsheet app, make changes and improvements, specifically ensuring numbers in each cell are formatted correctly with dollar signs and commas.”
Read reports →“Can you propose a system design for a video search problem?”
Read report →“Can you describe a simpler solution to the async Python coding challenge that doesn't use the standard library?”
Read report →“How would you design an ML system for a video system?”
Read report →“Can you explain what Runway is to a person?”
Read report →“How would you design a system for labeling videos?”
Read report →Formats, difficulty and experience
Across all 76 Runway (NYC) interview reports.