Mapbox Interview Questions
& Process

I had my interview in June 2025. It started with a recruiter call, then I got a test task, which was to implement a Linux utility in C++. After that, I had a virtual interview day with 4 technical rounds. The first round was live coding with a LeetCode medium problem. The second was a system design round where I presented a complex feature from my experience. The third round, named 'Delivering results,' was a behavioral interview. The fourth was with the hiring manager, also behavioral. The whole process was quick and smooth. You can do all rounds in one day or split them up.

A recruiter reached out on LinkedIn. I had one recruiter throughout. First, we had a quick phone call to check qualifications. Then I spoke with the hiring manager who talked about the team's focus and what they look for. I was given a 2-hour take-home coding assignment. After that, two technical interviews happened: one about the coding assignment and SQL problems, the other about a past project's architecture. I had one final chat with the hiring manager because I had more questions. The recruiter was my main contact via email and phone. The whole thing took about a month.

For the take-home part, I had to find candidates for some really tough-to-fill roles with a lot of requirements, and also give a detailed guide on how I'd do it. I picked a diverse bunch to show how I work: some were a perfect match and already known to the company; others didn't quite fit the paper requirements on purpose to show that we shouldn't only focus on 'perfect' fits, and I explained this during our chat. The team didn't agree with how I approached it and gave my work a low score because of that. It's not good or bad, just different teams operate differently. I'm sharing this as a tip for others who might interview here.

The interview process felt excessively long. It consisted of a Recruiter Screen (30 min), a Hiring Manager Screen (30–60 min), and then a 90-minute Technical Interview. The technical part involved two interviewers, one of whom was mostly silent, and the other had trouble explaining the task clearly in English. They gave us a project involving a basic MapBox app with a search bar, a button, and a MapView, plus an internal library. The project required fetching API data using Retrofit. The main issue was the project itself, which seemed misleading. You'd expect to implement the search functionality given it was present but empty. Also, the questions were hard to grasp because the main interviewer phrased them poorly. I wouldn't recommend this experience; it's not worth the hassle, especially considering you'd have to work with these people if hired.