Mapbox logo

Mapbox Engineering Manager Interview Questions
& Process

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

Based on 6 interview experiences · FREE TO READ

2.8 Rounds average
Average Typical difficulty
33.3% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Mapbox.

Showing 3 of 6
Mapbox logo
Mapbox

Engineering Manager

Engineering · more than a year ago

Manager Average Positive experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical

It was a 2-step interview process. The first step was with HR, and the second step was with a technical expert. The interview focused on the embedded area and required deep technical expertise. They also asked about line management skills, not project management skills.

Confirmed questions1 question
  • Can you describe your projects where you acted as an Engineering Manager?
Mapbox logo
Mapbox

Software Engineering Manager

Engineering · more than a year ago

Manager Average Positive experience No offer 6 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Behavioral Technical

The interview process was really well structured and organized, honestly one of the best I've been through. It was similar to how Amazon does things, which I thought was thorough and fair. It kicked off with a recruiter chat, then a first call with the hiring manager, and after that, there were four loop interviews. It was super clear what to expect at each step. A big focus was on the company's values, with each interview asking for examples tied to them. This was a cool way to show how my experience fits with their core principles. The interviewers were respectful and professional throughout, making me feel like my time was valued. It covered both technical skills and cultural fit, giving a balanced view. One thing though, some interviewers seemed a bit new to it all and didn't quite grasp the 'why' behind the process or how to identify a good candidate. There wasn't much clarity on what makes a good performance versus what predicts success in the role, which I think comes with more experience. I've passed coding and system design interviews at Google before, so hearing my performance was just 'mediocre' was a bit confusing. It's important they understand the reasoning behind the process and what they should be evaluating.

Confirmed questions0 questions

No confirmed questions were included in this interview report.

Mapbox logo
Mapbox

Engineering Manager

Engineering

Manager Easy Neutral experience Accept offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Panel
Interview formats
Behavioral Technical Case Presentation

The interview process was pretty standard, involving a walk-through of my prior experience, some what-if scenarios, and working through a problem with product. My general sense is there’s coordination difficulty with the multiple geographies, the executive team is an echo chamber and inexperienced, and there’s a lot of experimentation with approaches to organizational design. Might be good if you are okay with the excitement of org by trial and error, but as someone experienced the lack of clarity and cohesive vision will create execution pain. The product is interesting if they can get beyond their growing pains.

Confirmed questions1 question
  • Can you walk us through your experience?

Mapbox Engineering Manager Interview Questions

Quoted word for word from Mapbox interview reports.

Can you describe your projects where you acted as an Engineering Manager?

Read reports

Formats, difficulty and experience

Across all 6 Mapbox interview reports.

Interview formats

Behavioral 41.7%
Technical 33.3%
Other 8.3%
Case 8.3%
Presentation 8.3%

Interview difficulty

Easy 16.7%
Average 66.7%
Difficult 16.7%

Candidate experience

Negative 33.3%
Neutral 33.3%
Positive 33.3%