Me postulé en línea. El proceso tomó 3 semanas. Acudí a una entrevista en Getaround (San Francisco, CA) en feb 2019
Entrevista
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.
Preguntas de entrevista [1]
Pregunta 1
Where do you see yourself in 2 - 5 years.
Describe one of the most challenging projects.
El proceso tomó 2 semanas. Acudí a una entrevista en Getaround (San Francisco, CA)
Entrevista
Did a phone screen and after several weeks got scheduled for an onsite interview.
I don't think they have much of an interview process there because the engineers I was supposed to be interviewed by were both sick and the people they got as replacements were just about the last people I'd want interviewing people. First one felt more like a interrogation than an interview, the guy was so cold that I couldn't relax at all. The second Interviewer wanted to ask a frontend question but didn't seem to have read my resume at all because he asked me to build something in react which is not something I have experience with.
after the first two the recruiter said that they wanted to stop because I seemed a little bit junior, which I was very insulted by since their whole process was a huge trainwreck.
Preguntas de entrevista [2]
Pregunta 1
Create a program to count the number of vowels in a word.
Me postulé a través de una recomendación de un empleado. El proceso tomó 2 semanas. Acudí a una entrevista en Getaround (San Francisco, CA) en mar 2018
Entrevista
I didn't officially apply but rather had been referred by an employee at Getaround. A recruiter reached out to me about a week later to set up a phone interview with one of their senior engineers. The interview question wasn't too hard – basically a graph problem (something like get dependencies for each folder). I almost solved it but ran out of time. Then I got an email to set up another tech interview over phone with another senior engineer at Getaround. This one was less algorithmic and more about you being resourceful and/or experienced in building APIs. I was asked to build a fake API in Python in three steps. I didn't have a lot of experience with Python but the interviewer was super nice and helpful.
I had a response two business days after. I got rejected because they were looking for people with more industry experience.
But overall it was a positive experience.
Preguntas de entrevista [1]
Pregunta 1
Build an API in Python with a fake server.
The API should:
1. Let users create cars
2. Let users get cars
3. Have an auth-system (if enough time)
