Veho (CO) Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 5 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Veho (CO).
Veho (CO)
Software Engineer
Senior Difficult Negative experience No offer 5 rounds
Interview process
Recruiter call Technical screen Group Presentation Technical screen
Interview formats
Technical Coding System Design Case Behavioral
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.
Confirmed questions3 questions
- The System Architecture task required designing a distributed system in Whimsical within an hour, with the initial instruction to use any technology. However, it turned out that presenting a diverse range of technical solutions was implicitly expected, a detail not communicated but clearly important for the evaluation.
- For the Code Debugging Task, the goal was to identify and resolve a bug in a codebase within one hour. What wasn't explicitly stated was that the speed and efficiency of navigating through the code itself were heavily considered in the assessment. Time spent on understanding the code or locating variables appeared to be penalized, which is not a realistic expectation for a real-world debugging scenario.
- The Values and Principles Discussion, lasting an hour, felt somewhat superficial in the overall context of the interview process. It seemed to have a much smaller impact on the final decision compared to the technical assessments, regardless of my performance in this section.
Veho (CO)
Associate Software Engineer
Entry Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Technical screen Onsite Background check Offer
Interview formats
Coding System Design Behavioral Technical
It started with a recruiter call to chat about my background and projects. Then, there was a technical test via Karat, which involved solving two LeetCode-style problems (easy/medium). The last part was a virtual onsite with three rounds with different engineers: one for system design, another for behavioral/culture fit, and a final round where I had to find and fix a bug. The engineers were all really nice and professional, making it a good experience overall.
Confirmed questions2 questions
- Karat: Given two arrays, identify the longest contiguous subarray where elements are equal.
- Onsite: Create a design for a URL shortening service.
Veho (CO)
Software Engineer
Mid Difficult Neutral experience No offer 4 rounds
Interview process
Recruiter call Technical screen Onsite Offer
Interview formats
Behavioral Coding System Design
So first I had an HR screen, then a Karat interview, and then a 3 hour onsite. The onsite included behavioral questions, coding problems based on their existing codebase, and a system design exercise.
Confirmed questions1 question
- They asked me to design a rate limiter.
Veho (CO) Software Engineer Interview Questions
Quoted word for word from Veho (CO) interview reports.
“Karat: Given two arrays, identify the longest contiguous subarray where elements are equal.”
Read reports →“An app that displays photos starts to lag and freeze after a few images. What's the cause and how would you resolve this issue?”
Read reports →“They asked me to design a rate limiter.”
Read reports →“Onsite: Create a design for a URL shortening service.”
Read reports →“The System Architecture task required designing a distributed system in Whimsical within an hour, with the initial instruction to use any technology. However, it turned out that presenting a diverse range of technical solutions was implicitly expected, a detail not communicated but clearly important for the evaluation.”
Read report →“For the Code Debugging Task, the goal was to identify and resolve a bug in a codebase within one hour. What wasn't explicitly stated was that the speed and efficiency of navigating through the code itself were heavily considered in the assessment. Time spent on understanding the code or locating variables appeared to be penalized, which is not a realistic expectation for a real-world debugging scenario.”
Read report →“The Values and Principles Discussion, lasting an hour, felt somewhat superficial in the overall context of the interview process. It seemed to have a much smaller impact on the final decision compared to the technical assessments, regardless of my performance in this section.”
Read report →“What's motivating your decision to leave your present employment?”
Read report →Formats, difficulty and experience
Across all 5 Veho (CO) interview reports.