← Back to Directory

Visa interview notes, page 4 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·Hiring Manager Screen

Jun 2026
Interviewed at Visa for a program manager role, one round, one question about global team management. Pretty sparse as far as interviews go.
  • What experience do you have managing global teams?

“I rambled a bit.”

View Post

Visa·Product Manager·Onsite - Product Sense / Strategy

Jul 2026
Visa PM interview focused almost entirely on roadmap discipline, which sounds straightforward until you realize they want you to treat it as a strategy document, not a feature backlog. The follow-ups were pointed and payments-specific, so generic PM answers don't really land here.
  • Walk me through how you build and manage a product roadmap, from the inputs you use to how you keep it updated over time.
  • What sources do you pull from when deciding what problems the roadmap should address?
  • How do you decide which initiatives make the cut and in what sequence?
  • How do you get cross-functional stakeholders to actually align on the roadmap rather than just nod and then do their own thing?
  • How do you handle a top-down request that conflicts with what's already on your roadmap?
  • What happens to user-facing features when a compliance requirement shows up and needs to take priority?
  • How do you communicate uncertainty in the roadmap to stakeholders who want firm commitments?
  • How do you know when a roadmap initiative actually worked?
  • How frequently should a roadmap change, and what triggers a re-prioritization?

“This is a big sprawling question and I kind of rambled at first.”

View Post

Visa·Data Scientist·Recruiter / HR Screen

Jul 2026
HR phone screen for a Data Scientist role at Visa, pretty standard stuff: motivation, cultural fit, tech background, and comp. Nothing too surprising but I felt underprepared on a couple of fronts.
  • Can you walk me through your background and what makes you a stronger candidate than others applying for this role?
  • Why do you want to work at Visa specifically?
  • What programming languages do you work with regularly, and how would you rate your proficiency in each?
  • Tell me about a time you had to navigate a difficult situation at work.
  • What are your salary expectations for this role?

“I rambled.”

View Post

Visa·Software Engineer·Technical Phone Screen

Jul 2026
Visa SWE interview, coding round with a string problem. Pretty standard stuff but the substring angle made me second-guess my approach midway through.
  • Given a string, how would you count the number of palindromic substrings it contains?

“Started with the brute force and they let me run with it for a bit before nudging me toward something better.”

View Post

Visa·Software Engineer·Technical Phone Screen

Jul 2026
Visa SWE interview with a graph problem. Pretty standard algorithmic round, nothing too wild.
  • Given a directed weighted graph, find the shortest path between two nodes.

“Knew it was Dijkstra the second I read the problem.”

View Post

Visa·Software Engineer·Onsite - System Design / Architecture

Jul 2026
System design round at Visa for a software engineering role. Just one question but it had enough surface area to go in a lot of directions, which I found both freeing and kind of paralyzing.
  • Design a system that stores multiple images inside a single file, with support for efficient storage, retrieval, and metadata.

“I started with the obvious stuff, a container format with a header index, offsets per image, maybe a footer checksum.”

View Post

Visa·Data Scientist·Technical Phone Screen

Jul 2026
Technical round for a Data Scientist role at Visa where they gave you a transactions dataset and made you solve the same problem twice, once in pandas and once in SQL. Pretty straightforward if you're comfortable with both, but the dual-format requirement caught me slightly off guard.
  • Given a transactions table, calculate each user's total amount spent in 2023, excluding negative amounts (refunds). Return user_id and total_spent sorted descending. Solve it first in Python using pandas, then rewrite the same logic in SQL using a CTE and GROUP BY.

“The pandas part was fine, filter by year, drop negatives, groupby user_id, sum, sort.”

View Post