← Back to Directory

Visa interview notes, page 2 of 4

Large Enterprises

Most of these Visa write-ups come from Software Engineers (26), then Product Managers (7) and Data Scientists (3). The most reported rounds are the technical phone screen (17), the product sense round (4), the system design round (4) and the recruiter screen (4).

37 interview notes · updated Sep 2026

Visa·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at Visa for a software engineer role, focused entirely on building an A/B testing assignment service from scratch. The question was broad enough to fill two hours and I don't think I got close to covering everything they wanted.
  • Design an online A/B testing assignment service where the API takes a user ID and feature name and returns which variant the user is assigned to.
  • How would you handle sticky and deterministic assignment so the same user always gets the same variant across sessions?
  • How would you store experiment configuration, and how does the service know which experiments are active and what their traffic allocations are?
  • How would you implement eligibility targeting so only certain users qualify for a given experiment?
  • Walk me through how you'd handle experiment overrides, things like QA accounts always seeing a specific variant, or a killswitch to disable a feature entirely.
  • How would you design the exposure logging system, and how do you ensure idempotency so the same exposure isn't counted multiple times?
  • What are the latency and availability requirements for this service, and how would you design fallbacks if the service is degraded?
  • How would you handle privacy and compliance requirements like GDPR or CCPA in the context of this experimentation system?
  • Describe the full lifecycle of an experiment from creation through analysis, including how you'd support pausing or stopping mid-flight.

“This is one of those questions that looks like a single system but is actually like eight systems duct-taped together.”

View Post

Visa·Software Engineer·Technical Phone Screen

May 2026
Interviewed at Visa for a Senior Software Engineer role and the whole experience was kind of a mess. Round 1 got rescheduled three times, including once where I sat in a waiting room for 15 minutes before someone told me the interviewer wasn't available. The actual technical interview covered pair programming and concurrency, and after a week of following up I got a generic rejection with zero feedback.
  • Pair programming exercise: solve a coding problem while explaining your thought process out loud.
  • Follow-up questions on threads and concurrency in software systems.

“Went through it fine, talked through my approach as I coded.”

View Post

Visa·Data Scientist·Onsite - Behavioral / Leadership

May 2026
Behavioral screen for a data scientist role at Visa. Pretty standard opening round, two questions back to back about conflict and job change motivation. Nothing technical yet.
  • Tell me about a time you had a conflict with a teammate. What caused it, how did you handle it, and what happened in the end?
  • Why are you thinking about leaving your current role, and what does your ideal next position look like?

“I structured it as situation-action-result and it felt okay, but I spent too long on the backstory and kind of rushed the resolution part.”

View Post

Visa·Software Engineer·Technical Phone Screen

May 2026
Visa SWE interview with a meaty data structures problem that required designing something efficient enough to handle large-scale inputs. The question had a clear algorithmic angle but also pushed into system design territory with the complexity analysis ask.
  • You have two integer arrays A and B and need to support two operations: Query(T) returns the count of pairs (i, j) where A[i] + B[j] equals T, and Replace(idx, val) updates B at a given index. Design a data structure to handle these operations efficiently for very large inputs, and analyze the time and space complexity.

“This one took me a minute to even parse.”

View Post

Visa·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at Visa for a software engineer role, focused entirely on designing a ride-hailing service like Uber. Pretty deep dive, they pushed hard on the distributed systems side of things.
  • Design a ride-hailing service like Uber, covering the full ride lifecycle from request to payment, real-time driver location tracking, and driver-rider matching.
  • How would you prevent two drivers from being matched to the same rider simultaneously in a distributed system?
  • Walk through how you'd handle millions of driver location pings per second at scale.
  • How would your system handle sudden traffic bursts, like a major event ending and everyone requesting rides at once?
  • What sharding strategy would you use for storing ride and driver data across a globally distributed system?

“Big open-ended prompt.”

View Post

Visa·Software Engineer·Technical Phone Screen

May 2026
Visa SWE interview with a pretty involved simulation problem. Not a typical LeetCode grind question, more of a design-your-own-data-structure situation with a lot of moving parts.
  • Given an array of warehouse capacities and a sequence of PACKAGE and CLOSURE events, simulate package routing: packages are assigned to the first available warehouse at or after a rolling pointer, warehouses that fill up are skipped until the cycle resets, and closed warehouses are permanently removed. After all events, return the warehouse id that processed the most packages, breaking ties by largest id. What data structures and algorithm would you use to keep per-event complexity low, and what edge cases do you need to handle?

“This one took me a minute to even parse.”

View Post

Visa·Product Manager·Onsite - Product Sense / Strategy

May 2026
Visa PM interview with a market sizing question about US transaction volume. Pretty classic for a payments company but I underestimated how deep they wanted me to go.
  • How many financial transactions happen in the United States on a typical day?

“I started with population segmentation which felt right, but I kept second-guessing whether to include cash transactions or just card-based ones.”

View Post

Visa·Product Manager·Recruiter / HR Screen

May 2026
Recruiter-style behavioral screen for a PM role at Visa, covering the usual intro, motivation, and a stakeholder tradeoff story. Pretty standard stuff but Visa's angle on payments infrastructure and compliance gives it a specific flavor you have to prepare for.
  • Walk me through your background and how you got to where you are today.
  • Why do you want this role at Visa specifically?
  • Tell me about a time you had to make tradeoffs between competing stakeholder priorities on a product or project. What made it hard and what did you do?

“I went present-to-past which felt natural but I rambled a bit in the middle.”

View Post

Visa·Software Engineer·Technical Phone Screen

May 2026
Visa SWE interview with a dynamic programming problem that flips the usual constraint, which threw me off more than I expected for something that looks like a classic knapsack variant.
  • Given an array of binary strings and two integers m and n, find the size of the largest subset where the total number of zeros is at least m and the total number of ones is at least n. Each string can be used at most once.

“I jumped straight to 2D DP because it looks exactly like the 0/1 knapsack problem on zeros and ones.”

View Post

Visa·Software Engineer·Technical Phone Screen

May 2026
Visa SWE interview had at least one algorithmic problem that looked straightforward on the surface but had a non-obvious optimal approach. The kind of question where you can get a working solution pretty easily but the interviewer clearly wants something better.
  • Given a sorted integer array, an integer k, and a target value x, return the k integers from the array that are closest to x, sorted in ascending order. If two numbers are equally close, prefer the smaller one.

“I got a working solution pretty fast using a sorted approach but the interviewer kept pushing on time complexity.”

View Post