Veho (CO) Interview Questions
& Process

Had a call with the recruiter, then spoke with a senior team member, followed by a coding assignment, and finally an onsite interview that was mostly behavioral. The process was straightforward, but I wasn't selected. I'm still waiting for feedback. The role seemed junior given my background as a data science manager with over a decade of experience. Given the hiring manager is Boston-based, I suspect bias against me as a minority, despite my performance, which is typical for Boston-based hiring managers. This is expected behavior for this company, especially if you're a minority. They likely had someone specific in mind, not necessarily based on merit but on type. Proceed with caution.

It was a 5-round interview process, taking about 5-10 hours spread over two weeks. The first round was a phone call to chat about my background. Then there was a Leetcode-style test with 5 questions, each taking 3-6 minutes. After that, I had a 1-hour interview about my values, followed by a 1-hour System Architecture interview, and finally, a 1-hour Case Study where I had to find and fix a bug in some code. Rounds 1 and 2 were on separate days, but 3, 4, and 5 all happened on the same day, back-to-back. This involved about 3 hours of questions from 4 different engineers at the company. I completed all the required stages and got positive feedback, but the final decision not to hire me based on the reasons given raises concerns about fairness and transparency. Specifically, in the System Architecture interview, I was told to use any technology but then marked down for not showing a variety of technical solutions, which felt contradictory. In the Case Study, I found and fixed the bug, but they seemed to judge me negatively on how I navigated the code environment, which felt petty and unrelated to the actual task. Being rejected after finishing all five phases for such minor things is disappointing and makes me question the professionalism of their evaluation. Plus, the interviewers had less than 12 months of experience at Veho, which further reduces the credibility of the process. My interest in Veho was genuine, but being dismissed for what seem like trivial reasons makes me doubt the integrity of their hiring process.

The timed technical assessment was one of the most frustrating and quite frankly ridiculous exams I have taken. It was heavily AWS specific and nuanced. The SQL questions were very complex with too little time to digest the schemas, various SQL statements, and multiple choice answers. Three questions were coding questions though and those were quite easy with ample time. Im sure there is a HIGH false-negative rate, which filters out plenty of good talent. I didnt have AWS specific experience anyway, so I'm not sure why they even interviewed me if they care so heavily about that. It comprised probably 60% of the questions. Overall left me with a very bad impression of Veho.

The interview process was quite simple and easy. I was impressed with how quickly they responded and how flexible they were with my schedule. They do expect you to give a presentation to a panel on an exercise they provide beforehand. I was hesitant about the presentation, which involved a new process implementation. Since they're a startup, they don't have many established processes and are looking for ideas on how competitors operate. I didn't get an offer because my presentation lacked "depth." Just be careful what you share with them since they're a "Series A" startup. They really value your knowledge and ideas, so protect them. Unless you have an offer, don't agree to present on any process implementations.