Turvo Interview Questions
& Process

This interview process was quite an experience, showing how far things can go before basic communication falters. I went through four interviews, including talking with senior leadership and several managers. Throughout, I was consistently told they enjoyed our conversations and that my industry experience was highly relevant, which was encouraging as the process kept extending. After the last interview, though, communication completely ceased. There were no updates, no timelines, and no idea of what was next. I had to follow up myself, and only then was I told they had chosen other candidates. The rejection itself wasn't the problem. What was striking was the huge gap between the in-depth interview process and the total lack of urgency or clarity at the end. For a company that prides itself on customer-facing excellence, the candidate experience felt surprisingly unorganized. If anything, this process was a good test of patience and self-control. My advice to management: if four interviews are necessary, closing the loop without being asked would be a really strong way to finish.

The head of HR was very friendly, almost excessively so, which felt a bit much. It's now apparent they were building me up for the CPO, who turned out to be quite difficult. Several red flags appeared: (1) there was a significant gap between interviews, which killed the momentum. (2) The CPO's demeanor shifted from pleasant to dismissive within the first five minutes. The rest of the call felt like filler. It seemed like he had already decided I wasn't the right fit based on some preconceived notion, and he was just going through the motions politely. (3) When questioned, the CPO provided unclear and evasive responses. (4) They were ambiguous about the work location. Despite the job being advertised as remote, they strongly preferred an in-person role in Dallas, which felt hypocritical given the CPO himself was based in Seattle and hadn't relocated.

So there are 4 rounds in the interview process. First is the resume screening. Then there are two technical rounds. The first technical round covers basics in Java, programming questions, and API testing. The second technical round focuses on programs, projects, test cases, test scenarios, and negative scenarios. Finally, there's a managerial round where they'll ask about the release process, behavioral questions, and domain knowledge.

It was a pretty standard interview process for product teams. It started with an interview with the leader, then there was a panel interview, and finally, a presentation was requested. I decided to withdraw my application after they asked me to do a presentation because it felt like they wanted me to do work for the company rather than interviewing me for a job. My overall impression wasn't great because the team seemed very new, and the leader, who came from Salesforce, was trying to work in a transportation software company without any prior experience in that field.