
Getaround Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 5 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Getaround.
Software Engineer
This was the most disorganized on-site interview in my career. The office is a mess, very dirty and too small for the number of people working there. The coordinator was late and rushed me through the office tour. When we got to the scheduled conference room it was occupied by other people that were in the middle of the meeting. I'm not sure if they have any process around scheduling conference rooms as they were arguing of who was the first to book this room :) So couple minutes later we were able to find a first available room and start my first panel interview. During my conversation, interviewers were constantly looking at the watch and finally interrupted me in the middle of the interview saying that we will have to move to another room in couple minutes and that I don't have to write anything on the board because of it. After that, I had 3 more panels scheduled and for each panel I had to switch rooms. When it came to my virtual interview - they didn't have the meeting setup, so one of the interviewers had to set it up. Overall it didn't seem like interviewers were interested candidate's personality at all. The accent was mostly on the tech skills. Because of the disorganized process, there was o time for me to ask questions. They were stopping the interview and apologizing for the lack of time. Overall it was a very hectic experience. Will not recommend it.
- In 2 to 5 years, where do you envision yourself?
- Can you describe one of the most challenging projects you've worked on?
Software Engineer
Got referred by someone at Getaround, so I didn't formally apply. A recruiter hit me up about a week later for a phone interview with a senior engineer. The question was a graph problem, like finding folder dependencies. I almost finished it but ran out of time. Then, another phone interview was scheduled with another senior engineer. This one was less about algorithms and more about being resourceful or experienced in building APIs. I had to build a fake API in Python in three stages. I wasn't super experienced with Python, but the interviewer was really nice and helpful. They got back to me two business days later and rejected me because they wanted more industry experience. It was a good experience overall though.
- Build a fake API in Python, including a fake server, that allows users to create cars, retrieve cars, and implement an authentication system if time permits.
Software Engineer
So a recruiter hit me up on LinkedIn and then set up a 1-hour chat with the Engineering Manager. I had a really good talk with the manager, and they asked me a bunch of behavioral questions and also about the work I've been doing at my current place. They also threw some basic Python questions my way and said I'd be heading for an onsite. But since then, crickets... I've reached out to the recruiter a few times with no luck.
- Tell me about microservices.
- Can you explain your experience with Python?
Getaround Software Engineer Interview Questions
Quoted word for word from Getaround interview reports.
“Build a fake API in Python, including a fake server, that allows users to create cars, retrieve cars, and implement an authentication system if time permits.”
Read reports →“Tell me about microservices.”
Read reports →“In 2 to 5 years, where do you envision yourself?”
Read reports →“What are your thoughts on product management?”
Read reports →“Can you explain your experience with Python?”
Read report →“Can you describe one of the most challenging projects you've worked on?”
Read report →Formats, difficulty and experience
Across all 5 Getaround interview reports.