RoadRunner Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 5 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at RoadRunner.
RoadRunner
Senior Software Engineer
Senior Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Phone screen Take home Technical screen
Interview formats
Coding Technical Other
The phone screening was straightforward and conducted professionally. Following that, I was given a timed online assessment via a platform called Woven Teams. This made me wonder if engineers are too busy for direct candidate coding skill reviews. Unfortunately, the Woven platform experience was not good. It was buggy on Firefox, making TDD difficult due to inconsistent test saving. A different browser might work better, but generally, the UX was frustrating. One part involved a PR review with a 35-minute limit. Most of this time was spent understanding the requirements, leaving little time for substantial comments. Online, I've seen many candidates report similar issues with Woven. It seems more like a filtering tool than a genuine skill evaluation. If you find it tough, it’s likely the tool itself.
Confirmed questions3 questions
- How would you approach the Monthly Invoice Puzzle if a third party were meticulously examining your code?
- Regarding a PR with 50 CVEs, what are your thoughts?
- Can you provide a frontend test for simple React hooks?
RoadRunner
Software Engineer
Entry Difficult Negative experience No offer 3 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Technical Coding
Had a quick chat with HR and then got a technical assessment to complete on Woven. The assessment wasn't too difficult. What's annoying is that even though I passed all 3 assessments, I was rejected right away. This is an entry-level role, so I'm not sure what a company expects someone to do in 45 minutes other than make the code work and pass most of the tests. I definitely would have done more if I had the time.
Confirmed questions1 question
- Complete 3 real-world scenarios on the Woven platform.
RoadRunner
Software Engineer
Senior Average Positive experience Decline offer 3 rounds
Interview process
Recruiter call Technical screen Take home Onsite
Interview formats
Behavioral Technical Coding System Design
I talked to the CTO about general culture and went over my resume. Then I had to sudo code an algo. Next, I spoke with a Senior Engineer who asked me questions on frontend, backend, and browser knowledge. We also discussed system design and security best practices. Finally, I had a take-home HackerRank with two medium algo questions, one SQL query, and a whiteboard system design.
Confirmed questions6 questions
- Css specificity?
- Browser cache questions?
- Database questions?
RoadRunner Software Engineer Interview Questions
Quoted word for word from RoadRunner interview reports.
“How would you make a simple https.get request and parse the response?”
Read reports →“API design (routes)?”
Read reports →“Can you provide a frontend test for simple React hooks?”
Read reports →“SQL and NO SQL?”
Read reports →“Can you explain SQL joins and how to use SUM?”
Read report →“Regarding a PR with 50 CVEs, what are your thoughts?”
Read report →“How would you approach an array iteration challenge?”
Read report →“How would you approach the Monthly Invoice Puzzle if a third party were meticulously examining your code?”
Read report →Formats, difficulty and experience
Across all 5 RoadRunner interview reports.