What Visa Tests in Coding Rounds
- Know the two coding surfaces at Visa: the online assessment and the live technical rounds
- Know which LeetCode-style problems candidates report from the last 12 months, newest first
- Know where Senior and Staff loops swap algorithm work for Java, Spring, LLD or an applied AI build
Software engineer candidates at Visa Inc., the payments company, write code in two places. The online assessment decides whether you get interviews at all. After it, the technical rounds mix a talk about your projects with one or two algorithm problems and questions on the stack in the job posting.
The live problems are mostly LeetCode mediums with a light coat of paint. A coin-collecting problem where you can't take two neighbours is House Robber, and a "linked-list-like structure" with a loop is cycle detection. Many problems below have a single report. Read them as examples of the shape Visa asks. The ones with repeat reports get the most space.
The two coding surfaces
The online assessment
The platform changed in 2026, so check the date on any advice you read. Through January 2026 the test was mostly a CodeSignal assessment with four problems in 70 minutes, scored out of 600, and CodeSignal sets were still reported in March and August 2026. The first two were quick warm-ups, and the third and fourth took most of the time. Since February 2026 most reports describe a HackerRank "Technical Skills Assessment" in tiers named Beginner, Intermediate, Advanced and Expert. New grads and interns mostly report Intermediate. A Senior invite promised one intermediate and one advanced question. A Staff test in July 2026 was two medium-to-hard problems in 90 minutes.
There are exceptions. A Staff candidate still got CodeSignal in February 2026, and one late-2026 report describes HackerEarth with three problems, one easy and two medium. The India campus drives from September to November 2026 used HackerRank-style sets of three problems, 75 minutes at one college.
The CodeSignal tests were proctored with webcam, microphone, screen share and photo ID. One November 2025 candidate got a retake email that cited "typing pattern irregularities" and looking away from the screen. Don't paste code you wrote somewhere else. Visa publishes no cutoff, and a good score doesn't guarantee anything: one candidate was turned down at 567 out of 600, and another with a perfect 600 never heard back. The Visa OA lesson covers formats, tiers and the problems that repeat.
The live technical rounds
Most loops have two technical rounds of 45 to 60 minutes, then a hiring manager round. A typical round opens with your projects and current work, moves to one or two DSA problems, and closes on the stack. India backend loops run on Java. A Staff candidate in June 2026 wrote, "All code was done in java." Other stacks get their own turn. An October 2026 loop was .NET and Angular, a November 2026 campus round used Python with pandas, and frontend roles get JavaScript, Angular or React.
Reports from 2026 rarely name the coding tool. One 2025 round ran in CodeSignal's interview editor, and some Bengaluru drives that year were in person on the same day, one on pen and paper with no laptop. Ask your recruiter which you'll get, because writing Java by hand is a skill of its own.
How much DSA you get depends on the team. Two 2026 Senior candidates had no coding problem at all, only concepts and production experience, and an Austin recruiter told a Senior candidate in May 2026 that the round wouldn't be LeetCode style. Other 2026 Senior loops had a medium. Fewer US loops are written up. When a candidate asked about a Bellevue onsite in November 2026, a Visa engineer replied that onsites are very team specific, and that theirs had two LeetCode mediums, one hard and a resume discussion.
What the interviewers score
Candidates describe the same arc again and again: a brute force first, then the optimized version, then the complexity of each. The October 2026 House Robber candidate walked through both. A July 2026 Bengaluru candidate opened a binary search problem with brute force, then optimized it and compared the complexity as they went. Several interviewers pushed past the first good answer. In February 2026 a Staff interviewer wanted O(n) on a problem where O(n log n) was the natural answer. A May 2026 Staff round asked for a Premium question and then a version faster than O(n^2).
Some rounds test range more than speed. In August 2026 an SDE1 was asked to solve a Premium question with DFS, then again with BFS, and compare the two. A September 2026 onsite candidate had to write their own test cases and a main method. Treat neither as a surprise. The bar isn't LeetCode-easy either. The July 2026 Staff OA ran medium to hard, and a Staff interviewer that same month wanted a complete, working LRU cache plus a design question inside 45 minutes.
Say the brute force out loud in a sentence, give its complexity, then build the better version. Run it on a small example before the interviewer asks. When they push for a faster bound, they usually have one in mind, so ask what the input sizes look like.
What Visa asks in live rounds, newest first
These five have repeat reports and at least one in the last 12 months. Report counts include older years, which are labelled.
Premium question. Four reports, the newest in October 2026. That candidate, on a .NET and Angular loop, got something like House Robber I at the end of round one and something like House Robber III, the tree version, in round two. In February 2026 a third-round problem was a Premium question, with a follow-up much like the circular version. The other two reports are from 2025. House Robber & DP works all three versions.
Premium question. Three reports, two of them in 2026. The August 2026 SDE1 round asked for DFS, then BFS, then a comparison, and moved on to HashMap and ConcurrentHashMap internals. A January 2026 round paired it with a GenAI discussion. The third report is from 2019. See Graphs, Grids & Trees.
LRU cache. Five reports since 2021, three of them in the last 12 months, which with House Robber makes it one of the two most reported live problems. July 2026 brought the Staff round above, where nothing short of full working code would do. In March 2026 it sat inside a Senior round otherwise about Java and Spring Boot, next to hashCode and equals. In November 2025 it was the third question on a US CodeSignal OA. See Linked Lists & the LRU Cache.
Premium question detection. Three reports, the newest a July 2026 Bengaluru screen that described "a linked-list-like structure" with a loop. The others are from 2025 and 2021. It lives in the same linked list lesson.
Premium question. Three reports, the newest a June 2026 Staff DSA round, all in Java, where it followed a linked list intersection problem. The others are from 2025 and 2022. See Arrays, Strings & Binary Search.
Single reports from 2026 fill out the same lessons. A November 2026 campus round asked for each node's descendant sum in a tree, and an August 2026 round had Dijkstra with a priority queue.
Other patterns from 2026 rounds
Some candidates name the pattern and nothing else. A September 2026 onsite had "a greedy problem" in round two, which the candidate solved with a HashMap and one loop. A July 2026 Bengaluru round had a binary search problem, brute force first. An August 2026 Senior round opened with a medium that needed two pointers and binary search, done in about 15 minutes. A UK OA in July 2026 had one DP problem and one two-pointer problem. Drill these patterns too.
The OA problems that keep coming back
The CodeSignal-era OA reused its problems more than the live rounds do. A bus departure question has four reports, the newest from a Senior OA in March 2026: given departure times in HH:MM and a current time, find something like the bus that left most recently. A newspaper layout task, close to Text Justification with centred lines and a border of asterisks, has three reports up to December 2025. Counting numbers with an odd count of zeros and a memory allocator simulation, close to Design Memory Allocator, have two reports each, both newest in March 2026.
So far the HackerRank tests repeat less. The July 2026 Staff pair was one graph problem and one DP problem, both medium to hard. A question about jumping between two sorted lists of departure times showed up on an August 2025 intern OA and again in an October 2026 campus drive. A Premium problems are all worked in the OA lesson, and the India campus OA lesson covers the 2026 India drives.
Practical and LLD coding at Senior and Staff
Senior and Staff rounds often trade the LeetCode problem for code you'd write at work. A January 2026 Senior round for a Java and React role had no DSA. The candidate built a map from department to employees with Java streams, then a Product class with CRUD operations in Spring and JPA. Last came a JavaScript function that fetches from an API, with questions on how headers and auth tokens get passed. Streams questions have three reports, from 2022 to January 2026.
AI work has started to show up as code. In August 2026 a Senior candidate's second round, with a principal architect, asked them to assemble a RAG pipeline from Python interfaces the interviewer provided. Pseudocode was allowed, and the follow-ups covered embeddings, retrieval, cosine similarity and when RAG is the right tool. One candidate reported it, so treat it as a sign of where some teams are going. Java Streams, Spring & SQL covers it next to the Java and SQL problems.
Staff design rounds can end in code. A June 2026 Staff candidate designed a payment system with payment states, several payment methods, durable execution and retries, then coded the main entities and a service class with a strategy pattern for each method. That one is in Design a Payment System. A March 2026 Staff round asked for a distributed scheduler in pseudocode, with no working solution expected, covered in Design a Distributed Job Scheduler.
Practice by lesson
Start with the OA, since nothing else happens until you pass it, plus the campus lesson if you're in an India campus drive. Then the live mediums, House Robber first, then the practical rounds that match your stack.
The Visa OA on HackerRank and CodeSignal
Formats by period, the HackerRank tiers, scoring with no cutoff, and the bus departure and newspaper layout problems. Free.
The India Campus OA
The September to November 2026 campus drives: the format, the topics asked and a sliding-window rate limit. Free.
House Robber & DP
One of the two most reported live problems, all three versions, plus stock trading and a Premium question.
Linked Lists & the LRU Cache
The LRU cache as a live round and an OA item, plus cycle detection and the a Premium question.
Graphs, Grids & Trees
a Premium question, a tree given as an adjacency matrix, Dijkstra and a trip rebuilt from city pairs.
Arrays, Strings & Binary Search
Sliding windows, rotated arrays, subarray sums and a recursive count from loops in the last year.
Java Streams, Spring & SQL
Streams grouping, Spring CRUD with JPA and a top-spenders SQL query, plus pandas filters and the 2026 RAG round.
Frontend & JavaScript Rounds
Fetching from an API with auth headers, a React component round and two frontend problem-solving tasks.
The last lesson holds three classics last reported in 2025 or earlier, each labelled with its years. Do it once the current lessons feel solid.
Older Practice Problems (2019-2025)
a Premium question, a Premium question and level order traversal, each with two or more reports.
Common questions
Does Visa ask LeetCode questions?
Yes, in most loops. The live rounds are mostly LeetCode mediums, sometimes reworded, and the OA is LeetCode-style too. Some 2026 Senior rounds skipped DSA for Java, Spring and production questions, and one Austin recruiter said a Senior round wouldn't be LeetCode style. Ask what your loop has.
What are the most common Visa LeetCode questions?
In live rounds from the last 12 months, a Premium question, the LRU cache and a Premium question have the most reports, followed by a Premium question detection and a Premium question. On the OA, the bus departure question and the newspaper layout task repeat most. Most other problems have one report each.
What is the Visa technical interview like?
Usually two rounds of 45 to 60 minutes after the OA, then a hiring manager round. Each technical round covers your projects, one or two DSA problems, and the stack in the job posting, which is Java and Spring Boot for most India backend roles. Senior and Staff loops add system design, sometimes with classes to code.
What language should I use in the Visa coding interview?
The one you're fastest in, unless the role says otherwise. Java dominates Indian backend loops, and the stack questions will be in Java anyway. Python, Go, C# and JavaScript all appear in 2025 and 2026 reports.
Can I use AI in the Visa coding rounds?
No. Visa's interview tips say using AI during interviews "is strictly prohibited" and can end your candidacy. The CodeSignal OA was proctored and flagged unusual typing. AI does come up as a topic: a hiring manager in late 2026 asked how the candidate uses tools like Claude Code, and Visa's recent postings say every role needs fluency with tools like generative AI.
How hard is the Visa coding interview?
Many first rounds are easy to medium. The July 2026 Staff OA ran medium to hard, interviewers often push for a better complexity, and the CodeSignal fourth question was usually the hardest of the set. The bar is a clean, optimized medium with the edge cases handled, plus fluent answers on your stack.
Key Takeaways
- ✓The OA gates everything. It was mostly CodeSignal through January 2026 and has mostly been tiered HackerRank since.
- ✓Live rounds pair a project talk with one or two LeetCode mediums, then questions on your stack.
- ✓House Robber, the LRU cache and a Premium question are the live problems reported more than once in 2026.
- ✓Senior and Staff loops may swap DSA for streams, Spring, LLD classes or a RAG build.
Free Visa interview pages
Visa interview guideKnow what Visa asks before you walk in.
30 coding · 8 system design · 20 behavioral questions
Get their questions first.
InterviewLegend is independent and not affiliated with or endorsed by any company it covers.