Mapbox Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 54 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Mapbox.
Mapbox
Software Engineer
Mid Average Positive experience No offer 5 rounds
Interview process
Recruiter call Take home Technical screen Presentation Onsite Background check Offer
Interview formats
Coding System Design Behavioral Technical
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.
Confirmed questions2 questions
- Tell me about an innovation you introduced in a past project. Also, describe how you've handled team conflicts.
- Describe a time you innovated on a project and how you resolved conflicts within your team.
Mapbox
Software Engineer
Entry Average Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Take home
Interview formats
Behavioral Technical Coding
The process was pretty smooth from start to finish, and the HR and Hiring Manager were professional, really putting in effort for a good candidate experience. But that's where the good stuff stops. During the technical challenge, the interviewers were sarcastic and smug. They didn't seem interested in helping me succeed but rather focused on how little I knew about their specific domain problems. Plus, their questions were vague and poorly phrased, like "What is the problem with code?" It felt like they only hire people from Eastern Europe, and the interviewers I met barely spoke proper English. I'm not sure if they only use their native language internally. I'd recommend avoiding this place unless you speak Russian.
Confirmed questions2 questions
- Do you have any experience working with clients?
- What's wrong with the code?
Mapbox
Software Engineer
Senior Average Negative experience No offer 4 rounds
Interview process
Recruiter call Phone screen Take home Technical screen
Interview formats
Behavioral Technical Coding
I interviewed for the Helsinki office. First, I had a recruiter interview, which was fine. Then, I interviewed with the hiring manager, and it was a nice conversation, lasting longer than scheduled. After that, I received a take-home assignment. The assignment's requirements were generic and didn't reflect real-world software development. They estimated 1-3 hours, but I spent over 10 hours refactoring, implementing, writing unit tests with full coverage, and documenting everything due to the open-ended nature and various opinionated approaches possible. I got an email a few days later saying my solution was sufficient, but the feedback was generic and lacked explanation, criticizing the lack of detail despite my documentation. They expected production-level code for an interview process, which felt like a waste of time, as the evaluation seemed based on reviewer opinion rather than the programmer's experience.
Confirmed questions3 questions
- General recruitment questions.
- Deep dive into their current solution.
- Discuss my background and my last project.
Mapbox Software Engineer Interview Questions
Quoted word for word from Mapbox interview reports.
“Can you implement a retry function that calls an arbitrary input function automatically with retries? The retry function should accept the input function as an argument. If the invocation fails, it should retry the input function up to 2 times (total of 3 attempts). The retry function should return the result of the first successful invocation or the error from the last attempt.”
Read reports →“Write a function to mark duplicate IDs by linking them into groups (Mark Duplicates).”
Read reports →“Can you write code to determine if two strings are anagrams of each other?”
Read reports →“What additional functionality could be added to the retry function once the initial implementation is done?”
Read reports →“Can you complete the class functions and make sure all the test cases pass for this coding question, which involves graphs and has pre-written test cases and classes?”
Read report →“How would you design a system that can collect service metrics at scale?”
Read report →“How can we ensure a project is stable and prepared for release?”
Read report →“How would you design a tool for non-technical users to perform git operations like commits, pushes, and pulls, considering options like a web app, CLI, or other interfaces?”
Read report →“How would you implement a web system and architect its various components?”
Read report →Formats, difficulty and experience
Across all 54 Mapbox interview reports.