After I applied through Visa’s careers site and completed an online assessment, I got pulled into a technical interview round that became frustrating mostly because of scheduling. My first-round interview was postponed twice right before it was supposed to start. On the third attempt, I joined the call and waited about 15 minutes before reaching out to the recruiter, who told me the interviewer wasn’t available, and then rescheduled me for the next day.
The technical part itself was pair-programming. I solved the coding problem while explaining my approach, then had follow-ups that covered threads and concurrency. I initially answered one concurrency question incorrectly, but I caught the issue, corrected myself, and finished the round. Still, the interviewer seemed rushed and wrapped up the call shortly afterward, which left me with the sense that the interaction wasn’t fully open-ended.
3 months ago
Average Negative Bengaluru
My Visa process started with an OA, and once I got through, I ended up in a single technical interview round that left a really cold impression. The round was scheduled for 60 minutes to cover coding and low-level design, but it cut off after about 30 minutes, which immediately threw me off.
From the start, the interviewer never turned on the camera or joined via video, so the whole thing felt disengaged. When I tried to talk through my approach before writing code, the interviewer shut it down and insisted I just start coding, and even when I asked for alignment or clarification, I was told that hints weren’t allowed and that discussion wouldn’t happen until code was typed out. After one coding prompt, I sat through long pauses while the interviewer waited silently, and then the call ended early with no real space for questions or wrap-up.
3 months ago
Average Negative India
My process followed the familiar OA-to-interviews flow. After the online assessment, I went into two technical rounds: one round had an array-focused …
4 months ago
Average Positive Foster City, CA
My Visa process started with a GCA on CodeSignal, and I scored 570. After that, there was a short recruiter call, and then I got to the final round fo…
4 months ago
Average Negative United States
Once I cleared the early steps, the interview timeline moved pretty predictably. I had a 15-minute recruiter call first, then a separate recruiter int…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process typically begins with an online assessment followed by a recruiter call, and then progresses to one or more technical interviews, often including coding and design discussions. The timeline can vary, with some candidates experiencing delays or abrupt pauses in communication after interviews.
OARecruiter callTechnical interviews
Technical Interviews & Coding Challenges
Technical interviews often involve coding problems that are LeetCode-style, focusing on data structures and algorithms, with some candidates also facing system design questions. The coding rounds can be paired with discussions about concurrency, design principles, and real-world applications.
LeetCodeData structuresSystem design
Behavioral & Cultural Fit
Behavioral interviews are common and focus on candidates' backgrounds, motivations, and fit within the company culture. These rounds may also include discussions about past experiences and how they align with Visa's values.
BehavioralCultural fitMotivation
Interview Environment & Communication
Candidates reported mixed experiences regarding the interview environment; some found it engaging while others felt it was disengaged due to lack of video or interaction. Clear communication and the ability to articulate thought processes were emphasized as important.
CommunicationEngagementVideo calls
Feedback & Follow-Up
Feedback after interviews can be inconsistent, with some candidates receiving timely updates while others experienced long delays or no feedback at all. This lack of clarity can lead to frustration and uncertainty about the outcome.
FeedbackFollow-upCommunication delays
Preparation Insights
Candidates suggested focusing on core data structures, algorithms, and system design principles in preparation, as well as being ready to explain thought processes clearly. Familiarity with the specific technologies relevant to the role can also be beneficial.