READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 144 of 153
Interview experiences · Valeo
Valeo Software Engineer Interview Experience: C code tracing and embedded protocols
I started with an online assessment on HackerRank, which immediately set the tone. It leaned heavily on data structures and algorithms in C, with many code-tracing prompts where I had to predict how snippets would behave and whether they would compile. There were also multiple-choice questions on embedded systems and communication protocols, especially UART, SPI, and I2C. After the assessment, I…
Interview experiences · Valeo
Valeo Software Engineer Interview Experience: HackerRank, an online-store task, and a project walkthrough
The process began after I sent my CV. I completed a HackerRank assessment covering backend, frontend, HTTP, and cloud-related knowledge. Then they sent a task to build a simple online store or marketplace. The next step was an interview where I walked through the task and my experience, including what I did and how I approached it. The process felt structured and work-like because the conversatio…
Interview experiences · Valon
Valon Senior Backend Engineer Interview Experience — Four One-Hour Onsite Rounds in a Single Day
The recruiter got back to me within a day, really fast. First round, coding — 3 levels, 2 of which were the bar to clear. You write a schemaless database (an in-memory SQL), but you're given each column's type and name. Some rows might be missing certain columns. The first level is figuring out what data structure to use, then basically being able to store and read. The second level does filter a…
Interview experiences · Valon
Valon Software Engineer Interview Experience — Phone Screen on an Out-of-Order Loan Ledger
This was the phone screen. It was an OOP coding problem about a bank ledger. I had seen someone mention it on the forum but with no specifics, and if you haven't prepared in advance, time gets a bit tight. The first part is designing a simple dataclass and 2 basic functions, which are just simple addition and subtraction. The second part is the real focus. You design 2 functions that handle the 2…
Interview experiences · Valon
Valon Software Engineer Interview Experience — Two-Hour Bank Service Build, Then an HM Round
Valon's onsite format is pretty unusual: you get 2 hours to implement one problem. The goal is to build a banking service made up of 5 parts. My feeling is that you need to get through at least parts 3-4, but you are not required to finish everything. How the time is split: First 30 minutes: go through the problem with an engineer, discuss the design, and start building. Middle 90 minutes: you wr…
Interview experiences · ValueMomentum
ValueMomentum Software Engineer interview: communication, reasoning, and workplace scenarios
I began with a communication and reasoning screen made up of several parts. A prompt appeared in a video section and I had to answer it aloud. Then I received an audio question with the same idea, then typed an email-style response to a specific department. I also answered behavioral questions about what I would do in a workplace situation and whether I would report something to a manager. The pr…
Interview experiences · Vanguard
Vanguard Software Engineer interview with study case
After applying, I received an email with the process details and a study case to prepare before interviewing. On interview day, everyone I met was respectful, the tone was pleasant, and I did not feel there were gotchas. The process had two steps: a technical round and a more personal one. The technical part included a project-style question and a straightforward LeetCode-style coding problem, wh…
Interview experiences · Vanta
Vanta Account Executive fourth-round interview
My Vanta Account Executive process felt long, but it made me think more than I expected. It had five steps, and I reached the fourth round. The difficult part was not knowing where I stood relative to the other candidates. I kept waiting to understand what that stage meant in terms of the competition, and the uncertainty lingered. I appreciated the intentional, thought-provoking nature of the rou…
Interview experiences · Vanta
Vanta Account Executive interview: missed rounds and a generic rejection email
The recruiter stage set a bad tone for me. The process began with a recruiter screening, and everything afterward felt chaotic. The recruiter seemed disoriented and moved between two different recruiters before returning to the original person. Scheduling kept changing too. Meetings were rescheduled at the last minute, and the recruiter eventually joined the call late. More interviews were then s…
Interview experiences · Vanta
Vanta Account Executive interview with an AI note-taking setup
The Account Executive process felt miserable from the start and never recovered. I showed up late, then got distracted by messages during the interview. The interviewer seemed to be reading from a checklist. There was almost no curiosity about my answers, no real follow-up, and no acknowledgment beyond moving to the next question. The most jarring part was that they seemed to be using an AI note-…
Interview experiences · Vanta
Vanta Account Executive interview with principles discussion and mock cold call
After a recruiter screen, I was set up to meet the hiring manager. The next steps focused on the company’s principles and ended with a mock cold call. Even at that stage, it was clear what they wanted to evaluate: how I would think through the principles and how I would perform in a sales conversation. I didn’t receive an offer, but the process felt straightforward while it was underway. Location…
Interview experiences · Vanta
Vanta onsite
First day was system design and leadership sessions. System design was a simple DAU and MAU tracking in an existing system, I gave a pretty complete solution, however, there were some parts where the interviewer was getting confused on where the data was being stored and why. I'd suggest keeping the solution very simple as it seems like that is what they were looking for. Leadership session was p…
Interview experiences · Vanta
Vanta Software Engineer interview
After talking with the recruiter, I had a phone technical screen. It began with a simple conditional or if-else problem, then moved to a BFS-style graph traversal question. I later had a couple of onsite rounds split between coding and system design. The difficulty ranged from average to high. What stayed with me was the scheduling: the interviewers arrived a little late, then seemed rushed to re…
Interview experiences · Vanta
Vanta Software Engineer interview: concerns about the work environment
What stood out to me was not technical content but the environment I thought I could see through the people I met. From the outside, the culture felt suffocating. The engineers I observed seemed tired and frustrated. Managers came across to me as inexperienced and political, and the recruiting interactions felt biased and unsupportive rather than collaborative. The stated difficulty was average,…
Interview experiences · Vanta
Vanta Software Engineer Interview Experience — A Rough Technical Round Got the Next Day Cancelled
All of this had come up before. Coding: Implement a command line tool, uniq, with global uniqueness. Follow-up: what if the memory can't hold the entire hash table? SD: Metrics for most viewed URLs / subscription conversion rate of their web app. I didn't do well on the technical round, and the interview scheduled for the next day was cancelled outright. Feedback from the recruiter: Overall the t…
Interview experiences · Vanta
Vanta Software Engineer Interview Experience — Four-Part Onsite Ending in Rejection
I had my onsite (VO) on Monday and Tuesday. Three days later, today, the recruiter just emailed saying they decided to move forward with other candidates who are the best fit for the role. They asked if I wanted to talk through feedback. Overall I felt the interviewers were pretty good — they were responsive. At the start the recruiter gives you a Google doc with a pretty detailed writeup describ…
Interview experiences · Vanta
Vanta Software Engineer interview: two technical rounds and one behavioral
My process started with an online assessment, followed by a recruiter call and a standard technical process that became a virtual onsite. The onsite had two technical rounds and one behavioral round. Overall, it felt fairly professional and organized. What I remember most was how high the bar seemed for moving forward. The formats were conventional, but the interviewers appeared strict about what…
Interview experiences · Vanta
Vanta Software Engineer interview with 5 of 6 OA questions correct
I passed the resume screen and immediately received an online assessment. I answered 5 of the 6 questions correctly, covering arrays, hashmaps, and matrix or grid problems. After that, I was invited to a one-hour technical interview in a LeetCode-style format. They sent an interview prep guide beforehand, and I liked that it emphasized mapping out the solution before writing code. The interview f…
Interview experiences · Vanta
Vanta Software Engineer interview with a 4-of-6 online assessment
I passed the resume screen and then took an online assessment, but my process ended there. I got 4 out of 6 questions correct and was partially correct on a fifth. The problems were mostly about arrays, along with two-pointer problems and two grid-based questions. The test made it clear what they were evaluating, and I didn't score well enough to move on. The process didn't stretch across multipl…
Interview experiences · Varroc Group
Varroc Group Software Engineer interview: automotive fundamentals
After an assessment, I moved to a technical round and then an HR round. The technical discussion began with my resume and past work before moving into automotive fundamentals. I was asked about automotive protocols and the electronics concepts behind them, and the difficulty matched the average level they seemed to want. The HR conversation lasted around 15 minutes and acted as a short check-in a…
Interview experiences · Veeam
Veeam QA Engineer interview: homework and a two-hour technical panel
The process was demanding, with one stage seeming to lead to another. I began with a technical homework assignment. Next, I answered prepared questions online while staying on a call for a technical interview. That round felt rigid and focused on completing the tasks. I then had a one-on-one technical conversation. The final stage was more intense: a two-hour technical interview with three hiring…
Interview experiences · Veeam
Veeam Software Engineer interview: five rounds halted after hiring pause
I went through a longer process that was mostly standard in structure even as it dragged on. After a recruiter touchpoint, there were about five rounds: a coding-pad-style test, a hiring-manager conversation, technical interviews, and a system-design round. It seemed to be progressing in a controlled way, and I was told I had cleared every stage and could advance my candidacy. Then the momentum s…
Interview experiences · Veeva Systems
Veeva Systems Consultant interview: a 25 to 30 hour project
The experience was focused and brutal. I spent something like 25 to 30 hours on a project, and I believed the result was technically strong. I expected constructive next steps or at least a clear evaluation, but the team rejected the work coldly. The stated reason was essentially that my Zoom connection had been poor. That did not seem to match the effort I had invested or the quality I thought I…
Interview experiences · Veeva Systems
Veeva Systems Consultant interview: behavioral and take-home case presentation
The process felt thorough and mostly well run, although it took a while. The early focus stayed on why I wanted to work there, what value I could bring, and how I presented on a case. There were multiple stages, with relatively short initial screens of around half an hour each and fairly quick feedback on whether I would move forward. Then I had a behavioral round about interactions with people a…