READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 145 of 153
Interview experiences · Veeva Systems
Veeva Systems Consultant Interview Experience: Mock project and executive presentation
After submitting my CV, I moved through a steady sequence: HR screening, an in-person interview, a presentation round, and an executive interview. The arc was clear: meet the team, show how I would handle a project, then meet leadership. The presentation was the biggest step. I received a mock project tied to their solution, had to work it out on my own, and then present it. It took real preparat…
Interview experiences · Veeva Systems
Veeva Systems Consultant interview: strong feedback and a prolonged no-offer process
The core stages took exactly one month and were packed. I started with an introductory call with the manager, then had a job-history interview and a home assignment with one week to complete it. I presented my solution in a meeting, and the process continued with an interview with the practice director. I passed each stage with strong feedback, so I was genuinely optimistic. Still, no offer came.…
Interview experiences · Veeva Systems
Veeva Systems QA Automation Engineer interview: repeated assignment and canceled onsite
Once the automated system started the process, things moved quickly. I received the same technical assignment I had completed during an earlier cycle, so I completed it carefully again and submitted it. This time I was told explicitly that my code was excellent. The recruiter then called to arrange an onsite interview. The day before the onsite, I emailed because I was missing some logistics. Rat…
Interview experiences · Veeva Systems
Veeva Systems QA Engineer interview: pharma domain-fit mismatch
I started with a screening call, then had a direct video call with the hiring manager about a day later. The tone felt urgent, as if they were trying to fill the need quickly. During that conversation, I realized the main gap: I did not have pharma domain knowledge, and my background was in finance rather than testing in regulated or pharma settings. The recruiter and manager conversations were s…
Interview experiences · Vercel
Vercel Software Engineer Interview Experience — A Metrics Database in the Second Coding Round
This was my second coding interview, after passing the earlier coding round with the hiring manager. It was on CodeSignal. The code had to run, but there weren't any prewritten test cases that my code had to pass. That was pretty nice. It seemed that as long as it compiled, writing one or two simple tests with print statements was enough. The problem was to implement metricDB. A metric class had…
Interview experiences · Verily
Verily Software Engineer interview: coding and an HR step
I applied online and then followed recruiter-driven scheduling. They reviewed my resume, explained the process, and moved me into a technical round before an HR step. The technical part matched what I expected for a software engineering interview there: coding-focused questions in the easy-to-medium range, with nothing that felt far off-script. It felt easier than processes with heavy design or d…
Interview experiences · Verkada
Verkada Account Executive interview: sales sequence with recruiter ghosting
I went through what looked like a standard sales-track process: an internal recruiter round, a sales-manager round, a data-and-sales-figures review, and then a peer from the sales team I would have joined. On paper it sounded straightforward, but the coordination was a mess. I received requests for times I had already said I was unavailable. The recruiter asked again for availability for the foll…
Interview experiences · Verkada
Verkada Software Engineer Interview Experience — A Confusing Camera-Logging API Screen
This one was exactly the same as another report I'd read on here. The interview itself was nice, though the interviewer spent a good chunk of time just explaining the problem. The gist of it: the cameras generate some logs, and we needed to implement a middle-layer API server so that users could communicate with the cameras (sending requests and sending logs). We didn't need to worry about where…
Interview experiences · Verkada
Verkada Software Engineer Interview Experience — An Ambiguous WordGuess Coding Screen
Here's another question that wasn't from the interview-experience wiki: Need to throw an exception when the input isn't valid. The interviewer's description of the problem was really ambiguous. I spent forever trying to clarify it and still couldn't figure out what he actually wanted. Was I supposed to implement just this one function, or simulate the whole game? The interviewer kept being vague…
Interview experiences · Verkada
Verkada Software Engineer Interview Experience — Motion Thresholds Across Multiple Cameras
I could not answer Part 2 and was rejected. Part 1 — Single Camera Imagine that a camera installed in your building can detect motion. The camera outputs a stream of timestamps and a value indicating the motion intensity at each time. You collect this data and want to determine the periods when the motion was at or above a given threshold. Write a function that takes an array of sorted (timestamp…
Interview experiences · Verkada
Verkada Software Engineer Interview Experience — Phone Screen Coding a Host Log Key-Value Parser
Interview question summary: Host Log Parser (key-value pairs) Background and goal Background: host systems and IoT edge devices (such as network cameras, access controllers, gateways, and so on) continuously produce runtime logs. Every log line starts with the timestamp of the event, followed by some key-value pairs joined with an equals sign. Goal: write a Python program that reads a log file an…
Interview experiences · Verkada
Verkada Software Engineer Interview Experience — Phone Screen Plus a Four-Round Onsite, No Feedback After Two Weeks
Phone screening: HR sent an environment setup prep ahead of time, asking me to set up my GitHub account beforehand and install Docker / PyCharm etc. locally. The interviewer was very patient and walked through the whole flow end to end — I needed to implement three API calls. The actual question matched a report I'd already seen in another thread on the forum. Onsite, live and in person: I drove…
Interview experiences · Verkada
Verkada Software Engineer Interview Experience — Real-Time Voting Results for a Halftime Survey
The coding question was LeetCode 36. The system design question felt new to me. I was asked to design a survey system for a Super Bowl halftime show. Each user could vote for one question, with either A or B as the result. There were two requirements: A user should be able to see the real-time result immediately after voting. The host should be able to see the accurate voting result after the eve…
Interview experiences · Verkada
Verkada Software Engineer Interview Experience — Technical Screen on Finding the Camera Super Admin
Problem description In an enterprise role- and group-based permission system (RBAC), there are three kinds of entities: users (User), groups (Group), and cameras (Camera). The input is a list of permission relations, perms_data, where every element is a triple (source, relationship, destination). There are two core relationships: "camera_owner": the format is (entity, "camera_owner", camera_id).…
Interview experiences · Verkada
Verkada Software Engineer Interview Experience — Two Coding Rounds, No System Design
Looking at other people's interview reports, most say they got one coding question and one system design question, but I got two coding questions — not sure if that's just because I was too slow and never got to the system design part... The first question: there's a camera that processes camera data. The input is a vector and a threshold. Each element in the vector is a timestamp and a motion le…
Interview experiences · Verkada
Verkada Software Engineer interview: product troubleshooting and networking
The interviews moved quickly after my recruiter conversation. I had three rounds, starting with a behavioral discussion about my background, who I was and what interested me in the company. The second round was the most technical. I worked through two coding-style questions involving connecting someone to the internet and troubleshooting a Verkada product. The questions felt practical: I had to t…
Interview experiences · Vertiv
Vertiv Software Engineer interview: live logic and project-based Python questions
Technical interviews followed fairly quickly after my recruiter call. In one screen, I shared my screen, built some logic live and explained it while answering follow-ups. It was hands-on, and I felt the interviewer was paying attention to my approach. The questions stayed close to my experience. One interviewer referred to a project I'd mentioned and asked a series of Python questions about that…
Interview experiences · Virtu Financial
Virtu Data Scientist Interview Experience — Basketball Shot Prediction Design and a Connect Four Round
Timeline: mass-applied -> OA -> HR screen -> Round 1 -> Round 2 The HR round just went over my resume, timeline, and identity/status information. None of the brain teasers people mentioned in earlier interview experience posts. Round 1 was an open-ended ML system design. The question: after a basketball is thrown, it can either go in or miss — how do you model this using information available at…
Interview experiences · Virtu Financial
Virtu Financial Full Stack Engineer interview: expected C++ and a JavaScript task
A recruiter contacted me about the role and my background. I appreciated how they handled my frequent job changes caused by layoffs. They described the process as "language agnostic" and said the first round would be DSA in C++. I scheduled the interviews quickly and concentrated on preparing in C++. When the interview began, the engineer asked me to solve a combined DSA and low-level design prob…
Interview experiences · Virtu Financial
Virtu Financial Quantitative Analyst interview experience
The process started with an online assessment that I was told only a small fraction of applicants passed. After I got through it, a recruiter call felt encouraging. The technical screen was unsettling. The interviewer introduced herself, asked me to introduce myself and explain why I wanted the firm, then moved to my research experience. She seemed repeatedly confused about its basis and kept ask…
Interview experiences · Virtu Financial
Virtu Financial Quantitative Analyst Interview Experience: Probability coding before HR
After applying, I started with a HackerRank-style coding round. It combined basic probability with straightforward coding questions, and it felt manageable if I was comfortable with standard programming and probability fundamentals. An HR conversation followed, and that was where my process ended. I felt I had cleared the technical part cleanly, so being screened out after the recruiter call was…
Interview experiences · Virtu
Virtu Quantitative Researcher Interview Experience — Five Hard Problems in a 105-Minute OA
Five problems in 105 minutes. The problems are hard difficulty, and some of them are straight LeetCode problems. Time is pretty tight. I got the OA within about two weeks of applying everywhere. Debt Transactions: LeetCode 465. Building Construction: LeetCode 2865. Reaching Points: LeetCode 780. Lifting Weights: Given an array weights of n plate weights and a barbell capacity maxCapacity, choose…
Interview experiences · Virtu
Virtu Quantitative Researcher Interview Experience — Rejected Before the Final Data Analytics Coding Round
First, there was a 35-minute logic test. The content was very simple, just some pattern recognition and things like that. After that, the difficulty went up. After asking a few questions about my resume, the first interviewer gave me a graph theory brainteaser: Let there be a polygon with n vertices. What is the maximum number of edges you can draw between them without making a triangle (three ve…
Interview experiences · Virtusa
Virtusa Software Engineer interview: AWS experience stopped progress
At a walk-in event, I completed an AI assessment and then a technical round, which I cleared. I was told a virtual HR call would follow, but it arrived about ten days later. After that call, I had another technical interview and felt it went smoothly. I did not progress because they said I lacked hands-on AWS experience. That was frustrating because the interviews themselves had gone well, and it…