Rover.com logo

Rover.com Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 51 interview experiences · FREE TO READ

3 Rounds average
Average Typical difficulty
39.2% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Rover.com.

Showing 3 of 51
Rover.com logo
Rover.com

Software Engineer

Engineering · a year ago

Lead Average Negative experience No offer 3 rounds
Interview process
Take home Technical screen Onsite
Interview formats
Coding System Design Technical Other

I interviewed for a Lead/Senior Software Engineer position at Rover. The whole process took several weeks and over 10 hours of my time. It involved a take-home assignment that took me about 7 hours to complete on my own, followed by live coding, system design discussions, and technical chats. Even though I put in a lot of effort, it felt like the process became more and more impersonal and disengaging. In the last round, the interviewers didn't seem very interested, making it hard to have a good conversation. I got rejected two days later with a standard automated email. It had no personal feedback, didn't acknowledge the time I spent, and offered no useful advice on how I could have done better. If you're thinking about applying, know that it's a very transactional process, and they don't seem to care much about the candidate experience. I can't recommend interviewing at Rover unless you're okay with a one-sided, impersonal experience. Companies that really want to hire good people should connect with candidates meaningfully and give good feedback, especially after several interview rounds.

Confirmed questions2 questions
  • The take-home assignment was an app for pet sitter reviews, which has been described in other feedback.
  • There was a quick Python string manipulation coding challenge, which should be easy if you have intermediate Python skills.
Rover.com logo
Rover.com

Senior Software Engineer

Engineering · a year ago

Senior Easy Negative experience No offer 9 rounds
Interview process
Recruiter call Take home Technical screen Panel Onsite Background check Offer
Interview formats
Technical Coding System Design Behavioral

This was a long process with 9 interviews in total. It started with an HR interview, then a manager interview. After that, there was a take-home assignment where I had to process a CSV file, perform calculations, and output a new CSV, which took about 4 hours for the task and another 12 hours to prepare with Docker and unit tests. Then came a panel interview for system design. Following that was a behavioral interview with the initial manager and an additional manager from another team. The process also included another take-home project involving coding where I had to implement a new requirement in front of two engineers.

Confirmed questions8 questions
  • For the system design question, how would you structure the database tables to handle chat conversations between a sitter, an owner, and potentially a support agent?
  • Following up on the chat system design, what approach would you take to handle a very high volume of messages per day?
  • For the take-home exercise, you're given a CSV of customer reviews. Your task is to write a command-line program that imports this data into memory and then implements Rover's search algorithm to generate a 'sitters.csv' file. This file should include Sitter email, name, profile score, ratings score, and search score, sorted by search score in descending order.
Rover.com logo
Rover.com

Software Engineer

Engineering · more than a year ago

Mid Difficult Positive experience No offer 5 rounds
Interview process
Recruiter call Phone screen Take home Technical screen Onsite Background check Offer
Interview formats
Technical Coding System Design Behavioral

I had a pretty good time interviewing at Rover. First, there was a recruiter call, then a technical phone screen, after which I got a take home assignment. The final stage was a virtual on-site which had 3 separate rounds. The phone screen was with an EM and focused on string manipulation. My take home involved a backend task. For the virtual on-site, I had a behavioral interview with the hiring manager, a systems design interview, and a coding interview where I had to extend my take home assignment. Although it was a long process, I really enjoyed talking to all the engineers and EMs. It was a bummer not to get an offer, but I really appreciated how communicative and supportive my recruiter was throughout.

Confirmed questions3 questions
  • Questions about building on the take home assignment
  • Questions about systems design
  • Behavioral questions

Rover.com Software Engineer Interview Questions

Quoted word for word from Rover.com interview reports.

How would you remove all instances of a substring from a given string?

Read reports

Create an OOP solution using a CSV file to calculate scores, including testing.

Read reports

Can you write unit tests for parsing a strange data format?

Read reports

Could you implement a class and its tests that parse a string and perform calculations on it?

Read reports

Given that the web application needs to handle a peak load of 10 searches per second, how would you design the API for the backend service that provides sitter and rank data to the frontend?

Read report

Design and implement a web application connecting dog owners, sitters, and featuring specific mathematical calculations.

Read report

How would you whiteboard a SQL schema for a threaded messaging system?

Read report

What factors influence your decision between a microservices architecture and a monolithic one?

Read report

Could you create a console application that processes a CSV containing dog sitter appointments? This app should transform the data into a list of dog sitters, calculating a score for each based on their booking review ratings, and then output this information as a new CSV file.

Read report

Formats, difficulty and experience

Across all 51 Rover.com interview reports.

Interview formats

Technical 32.1%
Coding 32.1%
Behavioral 20.1%
System Design 8.2%
Presentation 4.5%

Interview difficulty

Easy 29.4%
Average 58.8%
Difficult 11.8%

Candidate experience

Positive 39.2%
Neutral 17.6%
Negative 43.1%