5 round interview process, 5-10 hours over about 2 weeks. 1 - Phone call to discuss my background. 2 - 3rd party Leetcode style test, 5 questions, 3-6 minutes per question. 3 - 1 hour "values" interview. 4 - 1 hour System Architecture interview. 5 - 1 hour Case Study to find and fix a bug in a code base. 1 & 2 happened on different days, 3,4,5 all happened back to back same day. 3 hours of questioning from 4 different engineers from the company. Here's why I cannot recommend Veho. While I completed all the required stages and received affirmative feedback on my performance, the reasoning behind the final decision not to hire me raises serious concerns about the process's fairness and transparency. Their reasoning - 1 - System Architecture Interview: Despite being instructed to use any technology of my choice, I was later penalized for not presenting a variety of technical solutions. This contradiction between the instructions given and the criteria used for evaluation is misleading and counterintuitive. 2 - Case Study Round: The task was to find and fix a bug, which I accomplished. However, being judged negatively for my navigation through the coding environment, a seemingly trivial aspect unrelated to the core task, is both petty and unreasonable. The fact that I was excluded after successfully completing all five phases of the interview process for such superficial reasons is not only disappointing but also calls into question the professionalism of the evaluation criteria. Moreover, the lack of long-term experience among the interviewers(less than 12 months) at Veho further undermines the credibility of the process. My commitment and enthusiasm for the role at Veho were genuine, and I was fully prepared to be a passionate and dedicated team member. However, being dismissed for reasons that seem inconsequential and unrelated to my actual performance leads me to question the overall integrity of your hiring process.

- The first step was an interview with the current lead software engineer, discussing a range of topics including tech experience, working style and career goals. - After that there was a scheduled chat with the CTO, with similar topics but with an enhanced focus on the startup thesis, traction, growth and overall vision. - The final step was a live remote coding session, with a variety of challenges of increasing complexity, followed with a brainstorming problem solving session and framework / library specific questions.