Visa Software Engineer candidates typically report a timed online assessment, easy-to-medium coding interviews, resume and project discussion, and a hiring manager or behavioral round. Formats vary by team.
$125K
Avg. Base Comp
$140K
Avg. Total Comp
3-6 rounds
Typical Rounds
Not reported
Process Length
Candidates interviewing for Visa Software Engineer roles most often describe an online assessment first, followed by live technical interviews and a closing hiring manager or behavioral conversation. The assessments reported are LeetCode-style, with several candidates citing four questions in about 70 minutes on HackerRank or CodeSignal. Expect the exact platform and format to vary by team.
The live coding is usually described as easy-to-medium DSA. Reported problems include copying a linked list with random pointers, longest substring without repeating characters, Number of Islands, linked list reversal and graph questions. A few candidates also met harder or more varied prompts, so don't assume every round stays light.
What sets the loop apart is how often it moves beyond algorithms. Several candidates were asked to walk through a resume project in detail. One was grilled on every technology listed, including Kafka, Kubernetes, OAuth, JWT and caching, so only list tools you can defend. Others reported core CS and engineering questions on OOP, REST, testing, design patterns, operating systems, TCP/UDP, SQL and DBMS, and one was asked about ExecutorService.
System design appears in some loops, often conversational and high level. Prompts mentioned include a file processor and scaling an example website. Behavioral questions covered why Visa, teamwork, favorite projects and handling feedback. Outcomes are mixed, with both offers and rejections after similar-looking loops, so prepare broadly rather than narrowly.
Synthesized from 56 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Visa process.
Still ongoing, 3 rounds. I actually didn't expect a SQL question to show up since the agenda just said coding and DSA, so I struggled a bit on that because I never really write SQL queries; I'm used to just reading them.
Questions asked: They asked me to introduce myself and go through my resume. They asked about the projects I worked on and wanted me to go in depth technically. The SQL question asked to query employees and their UIN and return null if it's not present.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Visa
Write a query to return the two students with the closest test scores and the score difference
| Question | |
|---|---|
| Employee Salaries | |
| Top Three Salaries | |
| Rolling Bank Transactions | |
| Total Spent on Products | |
| Sum to N | |
| Bagging vs Boosting | |
| Size of Joins | |
| Alphabet Sum | |
| Employees Before Managers | |
| Resumable Fact Table Load | |
| Hurdles In Data Projects | |
| Production Model Monitoring | |
| Fewer Orders | |
| Count Transactions | |
| RAG Strict Source Control | |
| Concurrent LLM Serving | |
| Implementing the Fibonacci Sequence in Three Different Methods | |
| Slow SQL Query | |
| Modifying a Billion Rows | |
| Swap Variables | |
| Filling Supermarket Bag | |
| User Event Data Pipeline | |
| Check Matching Parentheses | |
| Mouse Search | |
| The Longest Journey | |
| Search Timeout | |
| Solo ML Deployment | |
| Three Indexes Adding Zero | |
| SageMaker Deployment Architecture |
Synthesized from candidate reports. Individual experiences may vary.
Several candidates report a short recruiter or phone conversation covering their background, the company and next steps. One says expected salary also came up. Not every candidate describes this step, so it may vary by team.
Candidates report a timed online assessment. Several describe four LeetCode-style questions in about 60 to 75 minutes, ranging from easy to medium or occasionally harder. Practice under a clock, since time pressure is the most common complaint.
Candidates typically describe one to three live technical rounds of about 30 to 50 minutes. Reported topics include linked lists, strings and sliding windows, graphs, arrays and recursion. Some rounds mixed in behavioral questions, and some added SQL or DBMS questions.
Several candidates report being asked to explain resume projects in detail, including API calls and technology choices. Others mention OOP, REST, testing, design patterns, OS and networking basics. Some loops included a conversational system design prompt, so be ready to explain scaling and tradeoffs.
Candidates generally describe a final conversation with a hiring manager or HR-style interviewer. Reported questions cover why Visa, teamwork, favorite projects and handling feedback. Some say it mixed in resume scanning or technical discussion.
