Zume logo

Zume Software Engineer Interview Questions
& Process

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

Based on 19 interview experiences · FREE TO READ

2.6 Rounds average
Average Typical difficulty
26.3% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Zume.

Showing 3 of 19
Zume logo
Zume

Software Engineer

Engineering · more than a year ago

Mid Difficult Positive experience Decline offer 1 round
Interview process
Recruiter call Onsite
Interview formats
Coding System Design Technical

The interview process with Zume was great, I would highly recommend applying to anyone interested in the company. The recruiting team was perhaps the best I've ever worked with - very efficient, friendly, and sincere in their interest in my well-being. The onsite interview experience was also one of the better ones I've participated in. It was shorter than most (~4 hours) and had a well-balanced range of questions and topics. I was impressed with each employee that interviewed me. Lunch was provided, but unfortunately, it was a catered meal and not made by Zume's robots.

Confirmed questions3 questions
  • Standard whiteboard coding exercises were asked
  • System design was assessed
  • Candidates were asked database questions
Zume logo
Zume

Software Engineer

Engineering

Mid Average Negative experience No offer 3 rounds
Interview process
Onsite
Interview formats
Coding System Design

I had an onsite interview at their Mountain View office. It was pretty standard, with typical interview rounds focused on data structures and algorithms. They did provide pizza after the interview, but it was cold and hard. Usually, other companies have a proper lunch session if they offer food. The Mountain View office itself seemed very new, with a lot of empty desks, small rooms, and ongoing renovations. There were some pizza trucks outside, but they didn't seem to be used much, maybe because the office is so new. While the pizza wasn't great, I guess that's the problem they're trying to solve.

Confirmed questions2 questions
  • Were the coding questions not difficult?
  • Were there system design questions?
Zume logo
Zume

Senior Software Engineer

Engineering

Senior Average Negative experience No offer 1 round
Interview process
Technical screen
Interview formats
Technical Coding

I thought I was interviewing with Zume for a Senior Software Engineer role, but it turned out to be Karat, an outsourced company. They asked really basic questions without enough context to answer properly. I thought I did fine, but then I got a generic rejection email from Greenhouse saying another candidate was a better fit. I find it hard to believe there are many candidates with robotics experience for this specific role, as I never even spoke to anyone from Zume. It felt unprofessional.

Confirmed questions2 questions
  • Can you solve some simple matrix problems?
  • Given this generic traffic graph, what insights can you derive from it?

Zume Software Engineer Interview Questions

Quoted word for word from Zume interview reports.

Can you find the longest common subarray between two given arrays?

Read reports

What is the relationship between the different parts after splitting and storing the strings in a HashMap?

Read reports

If you're given an array of meeting time intervals with start and end times, what's the minimum number of conference rooms needed?

Read reports

Given this generic traffic graph, what insights can you derive from it?

Read report

Can you explain the distinction between a thread and a process?

Read report

How would you manipulate strings, split them, and then store the results in a HashMap?

Read report

Design a system for real-time tracking of food truck locations and inventory.

Read report

Could you design a system for tracking filesystem changes across multiple virtual machines?

Read report

Formats, difficulty and experience

Across all 19 Zume interview reports.

Interview formats

Technical 30.6%
Coding 30.6%
Behavioral 16.3%
System Design 16.3%
Case 2%

Interview difficulty

Easy 26.3%
Average 63.2%
Difficult 10.5%

Candidate experience

Neutral 21.1%
Negative 52.6%
Positive 26.3%