Unprofessional as I haven't heard from them after the interview. I had made time for an entire day to write an Android app for the interview. There was also a call prior to the interview with a director.
Questions d'entretien [1]
Question 1
What happens if you don't use an Observable return type for a retrofit call to an http get call?
J'ai postulé en ligne. Le processus a pris 6 semaines. J'ai passé un entretien chez Turo (San Francisco, CA) en août 2025
Entretien
- Directory + Manager: Meet with two great people, and we talked about the company, my experience, and future projects at Turo.
- Take-home Project: Pretty straightforward, consuming the Yelp API and showing the results for a particular call.
- Go over the take-home project: Meet with 3 other engineers, and we talked about the strengths of my project, my choice of tech stack, and all trade-offs I took given the time I was given to finish such project. We also talked about refactoring a few pieces here and there, and how to do so.
- API Design / Data Modeling (System Design): We went through a 3-step prompt, building on top of each of the previous steps to design an API that could be consumed for a particular goal-screen.
- Engineering Hiring Manager: Meet with the same manager from the 1st interview, given that the actual hiring manager was in parental leave.
- Engineering Hiring Manager v2: Final interview with the actual team's hiring manager (once he got back from parental leave a few days later), who further explained some of the projects that they usually take upon, on what kind of work I would be doing.
Questions d'entretien [1]
Question 1
My favorite question was: What are you building/working on outside interviewing or Turo?
J'ai postulé via un recruteur. Le processus a pris 2 semaines. J'ai passé un entretien chez Turo (San Francisco, CA) en juil. 2022
Entretien
Turo follows pretty standard interview process, it was very well put together, the process consisted of an
HR sync up, followed by phone screen then virtual-onsite. the focus areas were system design and coding.
Questions d'entretien [1]
Question 1
1. asked to code the solution to a coding problem in about an hours, the problem was solvable in an hour, even if you hadn't seen it before.
2. system design which is API, backend + functionality deep dive. this interview is spread across 3 different interviews so there is a fair bit of detail that has to be discussed here.
