Visa interview notes, page 1 of 4

“I went straight to behavioral signals like velocity checks and device fingerprinting, but I think I underweighted the geography-specific angle.” The rest of the author's notes on Product Manager interview at Visa, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Pretty standard opener.” The rest of the author's notes on Product Manager interview at Visa, Recruiter / HR Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I knew this one, which was a relief.” The rest of the author's notes on Software Engineer interview at Visa, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“My first instinct was to just iterate up to n and tally digit sums.” The rest of the author's notes on Software Engineer interview at Visa, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Started with the basics, username/password, session tokens, and then they kept pushing.” The rest of the author's notes on Software Engineer interview at Visa, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“It's a variant of a known LeetCode problem but the twist of returning answers for every K from 1 to n in one shot is what killed me.” The rest of the author's notes on Software Engineer interview at Visa, Onsite - Coding / Algorithms round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“It's basically that well-known problem but they split k into three separate values, which changes the complexity a bit.” The rest of the author's notes on Software Engineer interview at Visa, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Classic frequency count problem.” The rest of the author's notes on Software Engineer interview at Visa, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This is basically a bounded knapsack variant and I knew that going in, but the 'distinct sums' framing threw me for a second because I kept second-guessing whether I needed to track combinations or just reachability.” The rest of the author's notes on Software Engineer interview at Visa, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I knew the brute force immediately, just check every pair and track the minimum.” The rest of the author's notes on Machine Learning Engineer interview at Visa, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.