Real, anonymous reports from people who interviewed for Software Engineer at Turo, newest first and distilled into what to expect across the loop.
After talking with a recruiter and aligning on the logistics, the process moved into a structured technical track. The centerpiece of the experience was a take-home project that felt fairly straightforward: I worked with the Yelp API and built something that displayed results for a particular call. What surprised me was how much the next step focused on thinking rather than just finishing—about a week later I met with a small panel of engineers to walk through what I did, including why I chose my tech stack and the trade-offs I made with the time I had.
My impression was that the process was genuinely comprehensive, but still aimed to be understandable. The rounds touched a wide range of skills that come up in the job: system design and API design, plus algorithms and behavioral questions. Even though it cast a fairly wide net, the overall framing felt like it was trying to give me multiple chances to show different parts of my abilities rather than testing one narrow thing.
The interview process typically follows a structured flow, starting with a recruiter call, followed by a technical screen, and culminating in a virtual onsite that may span multiple days. Candidates noted that the process felt methodical and aimed at evaluating various skills relevant to the role.
Candidates should expect a strong emphasis on technical assessments, including coding challenges, system design, and API design. The interviews often require candidates to explain their thought process and design decisions, rather than just arriving at a solution.
Communication throughout the process can be inconsistent, with some candidates experiencing delays or a lack of follow-up after interviews. This has led to feelings of uncertainty and frustration regarding their application status.
Interviews often include behavioral questions aimed at assessing cultural fit and alignment with company values. Candidates noted that discussions about past experiences were common, and interviewers sought authenticity in responses.
The overall candidate experience can vary, with some reporting a supportive and respectful interaction with recruiters and interviewers, while others felt unprofessional treatment and lack of organization. Positive experiences often included thoughtful scheduling and follow-ups.
Candidates reported a mix of difficulty in technical assessments, with some finding the challenges to be unrealistic for the time allotted. It's advisable to prepare for a range of problem-solving scenarios, including both straightforward and complex questions.
