READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 146 of 153
Interview experiences · Virtusa
Virtusa Software Engineer Interview Experience: Detailed JavaScript and React round
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…
Interview experiences · Virtusa
Virtusa Software Engineer interview: fundamentals, arrays, SQL, and HR
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…
Interview experiences · Virtusa
Virtusa Software Engineer interview: Java, architecture, and HR rounds
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…
Interview experiences · Virtusa
Virtusa Software Engineer interview: online assessment, abbreviated technical round, and HR
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…
Interview experiences · Virtusa
Virtusa Software Engineer interview: programming fundamentals and relocation
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…
Interview experiences · Visa
Visa New Grad Software Engineer Interview Experience — Three-Question OA Ending in a Shortest-Prefix Permutation Problem
Visa's latest OA questions. Three questions in total: the first two were fundamental questions, and the third was an intermediate question. Question 1 I don't remember the problem statement clearly. It was fairly basic; I remember you needed a hashmap optimization to avoid TLE. Question 2 Given an integer array (a vector). For each integer in the array, find the minimum k such that: It is a posit…
Interview experiences · Visa
Visa Product Manager Interview Experience — Recruiter Says Passing Round One Doesn't Guarantee a Second Interview
10/10 phone screen with Visa. At the start, the recruiter first confirmed my visa type, whether I need sponsorship, whether I could do hybrid at least two days a week, and confirmed there's no relocation sponsorship — then the actual questions started. Tell me about yourself Why do you want to apply for this position How do you make the product roadmap — tell me about your experience working on a…
Interview experiences · Visa
Visa Senior+ Software Engineer Interview Experience — Online Assessment with Perfect Substring and Connected Groups
Online Assessment First question: Perfect Substring Given a string s made up only of digits, and an integer k, we need to find the number of substrings that satisfy a specific condition: every distinct digit character that appears in the substring must appear exactly k times. Input: string s and integer k Output: the total count of substrings satisfying the condition Example: if s = "11020211" an…
Interview experiences · Visa
Visa Software Engineer I Interview Experience — CodeSignal OA and Two Technical Rounds
CodeSignal online assessment Array operations: given arrays A and B, count the pairs for which A[i] + B[j] equals a specified target. Matrix rotation and boundary handling: rotate an N by N matrix clockwise, then perform special calculations on boundary elements according to specified conditions. String processing and sliding window: find substrings in a long string that match a specified pattern…
Interview experiences · Visa
Visa Software Engineer interview experience
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,…
Interview experiences · Visa
Visa Software Engineer Interview Experience: Abrupt and disengaged technical round
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…
Interview experiences · Visa
Visa Software Engineer Interview Experience: Repeated postponements before pair programming
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…
Interview experiences · Visa
Visa Software Engineer Interview Experience — Three-Round Onsite With Longest Increasing Path, a Greedy Problem, and an Inventory Service Design
Round 1: the original LeetCode problem, longest-increasing-path-in-a-matrix. Debugging wasn't very convenient. I also had to write my own test cases and my own main, so that held me up for a long time and I didn't have enough time. At the end I brought up the optimal solution, using memoization to record results, but I was out of time. > Given an m x n integers matrix, return the length of the lo…
Interview experiences · Visa
Visa Software Engineer Interview Experience — Warehouse-Capacity Routing and a Pair-Sum-With-Updates Problem
Questions one and two were pretty easy, I don't really remember them. Three: The prompt was long. You're given an int array representing the capacities of warehouses 0 through n - 1, plus an array of events. Events are either "PACKAGE" (process one package) or "CLOSURE X" (close warehouse N). Packages start being processed at warehouse 0, and once a warehouse hits capacity, the next warehouse tha…
Interview experiences · Visa
Visa Software Engineer interview: payment states, retries and reference checks
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…
Interview experiences · Visa
Visa Software Engineer interview: short Java and algorithms round
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…
Interview experiences · Voleon
Voleon Data Scientist Interview Experience — Python File Handling Before an Open-Ended Regression Task
Question format The interviewer gives one or more datasets: X: contains multiple features, possibly an m x n matrix y: a continuous, real-valued target You're expected to explore: which columns are related to y which features provide useful signal whether there's redundant information or collinearity among the features how you should build and evaluate a predictive model Before that part, there w…
Interview experiences · Voleon
Voleon Data Scientist interview focused on live coding
My interview process focused heavily on live coding rather than a lot of conversational questions. The main topics were Python operations and basic statistics and probability. The way they tested me made it feel like they wanted to see how I actually manipulated data instead of hearing me discuss it abstractly. I expected straightforward technical work. The coding itself didn't feel impossible, b…
Interview experiences · Voleon
Voleon Data Scientist interview with a below-market offer
My experience was shaped less by the technical interviews than by compensation. The process was organized and pleasant, and I genuinely liked the people I met. The rounds covered data science work and included technical as well as people-oriented discussions, including expectations around team or people management. The pay was the part that landed poorly. After going through multiple interviews a…
Interview experiences · Voleon
Voleon Data Scientist interview with Python modeling and analysis
I went through a thorough, structured interview process with Voleon. It started with an initial interview, followed by two technical interviews, two soft-skill interviews, and a final tech-focused interview. There were a lot of rounds, and I got the sense that they were trying to cover several different areas instead of testing only one skill. The technical interviews involved Python coding tasks…
Interview experiences · Voleon
Voleon Data Scientist interview with Python modeling and data analysis rounds
After a recruiter step, I went through an extensive sequence focused on data work and model building. The first technical conversations covered data manipulation and EDA, then moved into modeling. The goal was to see whether I could connect statistical thinking and practical data familiarity to the way I constructed and interpreted models. The process felt thorough rather than trick-based. The qu…
Interview experiences · Voleon
Voleon Data Scientist live coding interview focused on pandas
My main interview experience was a live coding session focused on data manipulation in Python, especially pandas. There wasn’t much guidance, and I couldn’t remember every detail afterward, but I clearly remember that I didn’t produce something the interviewer seemed satisfied with. What threw me off was not knowing what level of polish or correctness they expected. I kept building and iterating,…
Interview experiences · Voleon
Voleon Machine Learning Engineer Interview Experience — A Time-Series Pipeline Coding Screen
After recruiter outreach, the author agreed to interview with Voleon and reports being rejected after a 90-minute machine-learning coding session. The exercise involved a pipeline with roughly five tasks and a CSV dataset containing time-series observations. The author remembers debugging, changing model parameters, running results, and extending the pipeline for inference, but not the remaining…
Interview experiences · Voleon
Voleon Quantitative Analyst interview: probability, statistics, and machine learning
My process started with a phone screen with another PhD, and the conversation was heavily focused on statistics and math. We worked through probability and statistics questions, and I got the sense that the interviewer wasn’t especially enthusiastic about the role. I asked directly and learned that the position wasn’t very flexible. New hires were initially assigned to teams somewhat randomly, an…