
MakeSpace Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 31 interview experiences · FREE TO READ
Which role are you interviewing for?
13 roles · 31 reportsCandidate interview experiences
First-hand accounts from people who interviewed at MakeSpace.
Sales Representative
Sarah the recruiter reached out to me on LinkedIn. After that, the process was: Initial phone interview, Online Assessment, 2nd phone interview with the Sales Manager, In Person interview with the Sales Manager and Hiring Manager, and then the Decision / Offer. The whole interview process was quick and efficient. Every person I met was courteous, friendly, professional and genuine. It was a great insight to the working environment at MakeSpace. I would recommend anyone I know to this company. Reason for declining: personal, but it has absolutely NOTHING to do with the role or company. This place is amazing!!
- What is your motivation for pursuing a career in Sales?
- What qualities do you possess that would make you successful in this position?
- What specifically about MakeSpace and this particular role appeals to you?
Software Engineer
I applied on LinkedIn and a recruiter reached out in about a week. We had a call to discuss the company and open roles. Then, I spoke with a hiring manager who went over the job details, what they expect, and their current products. After that, I had a tech screen with Karat IO. It was an hour long, with two coding questions. They were pretty simple, mainly about parsing strings and creating an aggregated output. I managed to complete one and explained my approach for the second before time ran out. I messaged the recruiter two days later for an update, but they never got back to me. Totally ghosted, no info on my application.
- Can you parse a list of parts (strings) and a list of required parts for a product to determine all the products that can be built? This involves matching strings and tracking the parts needed for each product.
Senior Frontend Developer
It was a pretty standard interview process. Started with a recruiter phone screen, then a video call with the CTO, followed by a live coding challenge. After that, there were a series of behavioral interviews. The technical challenge was okay, not too hard but not too easy. I didn't even finish it, but I think my explanation of the solution was good enough to move forward. I didn't end up getting an offer, but I really enjoyed interviewing there. Everyone was super friendly and seemed genuinely passionate about their work. The main downside was the duration of the whole thing; it stretched over a month. But they were hiring for a lot of roles at the time, so I guess they were just swamped.
- What's prompting your job search away from your current role?
Customer Service Representative
So first I had a phone call with the team supervisor, it felt like a get-to-know-you thing. Then about a week later, I went in for an interview with the head of HR, three different managers, and one of the founders. They all gave me a different idea of the job. A couple weeks after that, I had a video interview with the CEO, who was trying to make me say bad things about myself, but I was good. Then they did a reference check. I got the job offer in the end. It was a really long and hard interview process for an entry-level job.
- What makes you a suitable candidate for this role?
- What are your career aspirations for the next five years?
MakeSpace Interview Questions
Quoted word for word from MakeSpace interview reports.
“Given a JSON file with geographic points (latitude, longitude, id), create a Python script that accepts an integer 'n'. The script should read the file and output the IDs of the points, divided into 'n' groups, into a file named 'groups.json'. This output file should be a list of lists, containing dictionaries similar to the original points.”
Read reports →“Can you parse a list of parts (strings) and a list of required parts for a product to determine all the products that can be built? This involves matching strings and tracking the parts needed for each product.”
Read reports →“Given a selection of random images, identify a problem and propose a product solution within a 30-minute timeframe.”
Read reports →“What's been your biggest mistake?”
Read reports →“Can you tell me what you know about Makespace?”
Read report →“Could you solve a data structure and algorithm problem involving arrays?”
Read report →“Can you list three reasons why someone shouldn't work for MakeSpace?”
Read report →“Could you share your favorite app and the reasons behind your choice?”
Read report →“What are the reasons this role might not be a good fit?”
Read report →Formats, difficulty and experience
Across all 31 MakeSpace interview reports.