Visa · Primly Community

Visa product manager interview questions: what the PM loop actually looks like

apm_aisha · 4 replies

Done three PM loops at payments companies in the last two years. Just finished Visa's. Dropping notes here because there isn't much out there about the Visa PM interview specifically.

Visa has a product org that's larger than people realize. They hire PMs for consumer products, merchant solutions, platform/APIs, data products, and internal tooling. Which org you're targeting matters because the interview flavor differs somewhat.

Here's what I saw in my loop for a Senior PM role:

Product sense. The prompt was something like: "Visa wants to expand its reach with small-to-medium businesses that currently use cash or informal payment methods. How would you approach this?" It's not a trick question, but it has layers: user research, market sizing, prioritization, go-to-market. They want to see you structure ambiguity, not just brainstorm features.

Analytical. They gave me a dataset scenario: you see a drop in authorization rates in a specific geography, how do you investigate? This is classic PM analytics: segment the data, form hypotheses, identify root cause, know what questions to ask engineering. If you have a data background, this is a gift. If not, prep the diagnostic framework.

Execution/roadmap. "How do you balance technical debt requests from engineering against new feature asks from commercial partners?" Visa has a lot of internal stakeholder tension between product and the commercial/enterprise side. They want PMs who can manage upward, sideways, and technically.

Behavioral. Standard: a time you shipped something with imperfect data, a time you killed a feature, conflict with engineering partner.

Things that helped: framing answers around Visa's actual business model (interchange, network effects, merchant vs issuer vs consumer dynamics). Showing you understand the two-sided market is a quick signal that you're not a generic PM candidate.

4 replies

apm_aisha

The "two-sided market" framing is such good advice. I prepped this way for a fintech PM interview and it made my answers feel way more grounded than generic "increase DAU" type thinking.

growth_gabe

The authorization rate drop scenario is a classic but specifically in the payments context it has some non-obvious wrinkles. You'd want to look at issuer-side decline codes, not just merchant-side. Did they go deep on the payments-specific nuance?

jordan_pm

Yes, the interviewer lit up when I asked about decline code categories. Definitely not surface-level. Knowing the difference between a soft decline and a hard decline helped.

ops_omar

How long did the full PM loop take start to finish? Trying to calibrate my pipeline.