real interview stories, told over a cup of tea ♡
Interview Experiences
3935 interview stories from candidates at 857 companies: how each round went, what was asked and how it ended. Every company page links to practice questions in the same style.
- 3935
- Experiences
- 857
- Companies
- 532
- Offers
3935 results
- Veeva Systems Consultant interview: strong feedback and a prolonged no-offer processVeeva Systems · Consultant · Other · Jul 2026
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.…
- Veeva Systems QA Automation Engineer interview: repeated assignment and canceled onsiteVeeva Systems · QA Automation Engineer · Other · Jul 2026Rejected
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…
- Veeva Systems QA Engineer interview: pharma domain-fit mismatchVeeva Systems · QA Engineer · HR Screen · Jul 2026Rejected
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…
- Verkada Account Executive interview: sales sequence with recruiter ghostingVerkada · Account Executive · Jul 2026No response
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…
- Verkada Software Engineer interview: product troubleshooting and networkingVerkada · Software Engineer · Technical Screen · Jul 2026Offer
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…
- Vertiv Software Engineer interview: live logic and project-based Python questionsVertiv · Software Engineer · Technical Screen · Jul 2026
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…
- Virtu Financial Full Stack Engineer interview: expected C++ and a JavaScript taskVirtu Financial · Full Stack Engineer · Technical Screen · Jul 2026
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…
- Virtu Financial Quantitative Analyst interview experienceVirtu Financial · Quantitative Analyst · Online Assessment · Jul 2026
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…
- Virtu Financial Quantitative Analyst Interview Experience: Probability coding before HRVirtu Financial · Quantitative Analyst · Online Assessment · Jul 2026Rejected
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…
- Virtusa Software Engineer Interview Experience: Detailed JavaScript and React roundVirtusa · Software Engineer · Jul 2026
My virtual first round split heavily between frontend JavaScript theory and hands-on JavaScript coding. On React, I discussed the virtual DOM, why useMemo and useCallback matter, when react.memo helps, context API, Redux-style flow, and the difference between useRef and useState. For JavaScript, I wrote and explained the pattern 9 8 7 4 5 6 1 2 3, described as a snake-and-ladder-style pattern. I…
- Virtusa Software Engineer interview: AWS experience stopped progressVirtusa · Software Engineer · Online Assessment · Jul 2026Rejected
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…
- Virtusa Software Engineer interview: fundamentals, arrays, SQL, and HRVirtusa · Software Engineer · Technical Screen · Jul 2026
I had a straightforward set of rounds built around fundamentals and light coding. The technical flow began with theory and linked-list basics, then a small task to find an element in an array. SQL followed. I also explained my projects and why I chose particular technologies. In another technical conversation, I introduced myself before the interviewer followed with questions tied to my coding kn…
- Virtusa Software Engineer interview: Java, architecture, and HR roundsVirtusa · Software Engineer · Technical Screen · Jul 2026
I went through two technical rounds followed by a final HR conversation. The technical questions repeatedly returned to the details on my resume rather than staying at a surface level. The topics leaned toward programming fundamentals and Java-centered systems: OOPS concepts and language features, microservices design and patterns, authentication, and multithreading. I also faced coding questions…
- Virtusa Software Engineer interview: online assessment, abbreviated technical round, and HRVirtusa · Software Engineer · Online Assessment · Jul 2026
My interview followed a standard order: an online assessment, then a technical interview, and finally HR. The screening checked problem solving and programming fundamentals, while the later steps were more about technical fit and communication. OOPS concepts were a large part of the technical round. The session started late and ended quickly, so it did not get far beyond what they needed to cover…
- Virtusa Software Engineer interview: programming fundamentals and relocationVirtusa · Software Engineer · Technical Screen · Jul 2026
I had one technical interview followed by a short HR round. The technical discussion covered object-oriented concepts, Python and Java basics, and DBMS. I also solved a simple coding problem to demonstrate the fundamentals. HR focused mainly on practical availability matters such as relocation. I was surprised by how many topics the technical round combined. Overall, the process felt easy, straig…
- Visa Software Engineer interview experienceVisa · Software Engineer · Online Assessment · Jul 2026
After finishing the OA, I was selected for the next step. The interview combined a resume walkthrough with coding and fundamentals. They focused on my projects and hackathons, then asked at least one DSA question. The coding question was cycle detection in a linked-list-like structure, requiring me to reason through how to identify a loop. We also discussed CS fundamentals, situational questions,…
- Visa Software Engineer Interview Experience: Abrupt and disengaged technical roundVisa · Software Engineer · Jul 2026
The technical round was scheduled for 60 minutes and was meant to cover coding plus low-level design, but it ended after about 30 minutes. The interviewer never turned on the camera. When I tried to explain my approach before coding, they told me to start coding and shut down even small attempts to align or ask clarifying questions. There were long silences around a single coding prompt, and the…
- Visa Software Engineer Interview Experience: Repeated postponements before pair programmingVisa · Software Engineer · Online Assessment · Jul 2026Rejected
I applied through Visa's careers site and started with an online assessment containing two coding questions focused on dynamic programming and the two-pointer technique. The interview process was where it fell apart. My first-round interview was postponed twice just before its scheduled start. On the third attempt, I joined and waited about 15 minutes before contacting the recruiter. They said th…
- Visa Software Engineer interview: payment states, retries and reference checksVisa · Software Engineer · Online Assessment · Jul 2026Offer
I started with an online HackerRank test, then had a series of virtual interviews. The first technical round covered data structures, algorithms and system design. Later conversations went deeper into design and leadership. The DSA questions felt like familiar structured problems, but I still had to find a correct approach under time pressure. In system design, I needed to explain trade-offs in d…
- Visa Software Engineer interview: short Java and algorithms roundVisa · Software Engineer · Other · Jul 2026
My Visa interview lasted about 30 minutes and moved quickly. I began with a coding question and had around five minutes to produce a solution. That was followed by a logical puzzle. The interviewer then tested object-oriented programming and Java fundamentals, including implementing inheritance. The last part was a binary-search problem: I started with a brute-force approach, explained how I woul…
- Voleon Software Engineer interview: four-part virtual onsite pressureVoleon · Software Engineer · Technical Screen · Jul 2026Rejected
After a recruiter screen, I had a technical screen about a week later and then a four-part virtual onsite. The pace was fast for such a heavy process. The most intense piece was a two-hour coding session with several parts, framed as real-world problems rather than one tidy exercise. The loop focused on hard LeetCode-style coding. Even the system-design portion felt algorithmic and exercise-like.…
- Volkswagen Group Italia Software Engineer Interview Experience: A five-day backend assignment and disorganized staffing coordinationVolkswagen Group Italia · Software Engineer · Technical Screen · Jul 2026
A recruiter contacted me through LinkedIn even though I had not applied and, as far as I could tell, my profile was not in their pipeline. At first, they described it as a one-off interview and said they would keep my information for future opportunities even if I did not move forward. In reality, it lasted much longer and was hard to follow. I went through HR screening and then met a Backend tec…
- Volkswagen Group Italia Software Engineer Interview Experience: No-show technical meetingVolkswagen Group Italia · Software Engineer · HR Screen · Jul 2026No response
This recruitment experience felt extremely unprofessional from the first step. The initial HR conversation was not really an interview: there were no meaningful checks of my skills and no questions. It was mostly a briefing about what was meant to happen next. For the second technical meeting, I arrived on time and waited an hour, but no one showed up. I reported it immediately and received no ap…
- Volkswagen Group Italia Software Engineer interview: coding game and recruiter callVolkswagen Group Italia · Software Engineer · Other · Jul 2026
I started with a coding game exercise where I could choose from a flexible set of technologies. After I finished it, I had a call with the recruiter. During that conversation, the recruiter described the projects I might work on. The process felt like an early screen for both my technical approach and fit with those projects. It did not develop into a long sequence of rounds. Location: Lyon. Over…
- Volkswagen Group Italia Software Engineer interview: recruiter and business manager conversationVolkswagen Group Italia · Software Engineer · Jul 2026
I began with a recruiter call that covered my background and set expectations for what would happen next. Later, I joined an online interview with a business manager. We discussed my experience and skills, and they also explained the company and its approach to learning and growth. I had about ten minutes to introduce myself, then they asked questions as the conversation continued. It felt like a…
- Volkswagen Group Italia Systems Engineer Interview Experience: promised follow-up never cameVolkswagen Group Italia · Systems Engineer · HR Screen · Jul 2026
An HR contact reached out after I applied. The first phone interview did not go well because they wanted a profile different from mine. During that call, though, I was told someone else would contact me about a position that suited my background better. That follow-up never happened. I was frustrated because they had set a clear expectation and then the process simply stopped. Location: Milan. Ov…
- Walmart Data Scientist interview with supply-chain time series and a missed follow-upWalmart Labs · Data Scientist · Technical Screen · Jul 2026Rejected
The process felt unusually intense and a little chaotic from the start. After an initial technical screen, I had a supply-chain technical round with several interviewers. It covered SQL, Python, statistics, including a probability question, and deeper machine-learning model details. The session lasted about 1.5 hours and focused heavily on time-series modeling. It was hard to follow every prompt…
- Walmart de México y Centroamérica Account Executive interview: store conversations and customer scenariosWalmart de México y Centroamérica · Account Executive · Other · Jul 2026
Things usually moved quickly after I applied online. A recruiter or HR call would arrange an interview, which was brief and conversational. I spoke with someone from the store or hiring team about why I wanted to work there, how I'd handle customer-service situations, my availability and whether I could do the required tasks. The usual format was a phone or virtual screen followed by an in-person…
- Walmart de México y Centroamérica Software Engineer interview: coding feedback and no follow-upWalmart de México y Centroamérica · Software Engineer · Technical Screen · Jul 2026No response
An email invitation led to a virtual interview that quickly became a coding exercise. I had one LeetCode-style problem involving what seemed like familiar array logic, with a chance to talk through my approach. The interaction made it harder to concentrate. The interviewer's comments and reactions felt negative, as though I was already on the wrong track while I was still working out the problem.…
- Walmart de México y Centroamérica Software Engineer interview: conversational live codingWalmart de México y Centroamérica · Software Engineer · Jul 2026
I started with a recruiter screen and then, about a week later, had a structured, recruiter-friendly technical interview. The technical session was divided into a few rounds, and each interviewer explained the plan upfront. I completed LeetCode-style coding and also talked through my background, resume, and the tech stack I had used in past work. Kafka and Kubernetes came up naturally while we di…
