Wise logo

Wise Product Manager Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 82 interview experiences · FREE TO READ

2.6 Rounds average
Average Typical difficulty
40.2% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Wise.

Showing 3 of 82
Wise logo
Wise

Product Manager

Product · half a year ago

Senior Average Negative experience No offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Technical Behavioral

The interview process involved a Recruiter/Talent Screen as the first stage, followed by a Hiring Manager + Engineering Lead interview. The first stage was pretty basic. In the second stage, I was asked to discuss a theoretical problem for half the time and then something I had previously worked on. The interview felt poorly organized, and the engineer on the call had a rude attitude and poor interpersonal skills. Afterwards, I got an automated email saying I didn't move forward, which is fine, but candidates should receive actual feedback instead of a generic email. If you take the time to interview someone, you should take the time to provide candidate feedback, or else don't hire! No relevant feedback was provided.

Confirmed questions1 question
  • Can you describe a complex, technical project you've worked on, excluding aspects related to stakeholder alignment?
Wise logo
Wise

Product Manager

Product · nearly a year ago

Lead Average Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen
Interview formats
Behavioral Technical

So, let's talk about job interviews with Wise. A lot of people I know have had their interviews canceled at the last minute, not politely rescheduled in advance, just canceled, or endlessly moved around. Mine didn't start that way. It started hopeful, normal, and maybe even encouraging. And then came the plot twist. I was assigned a manager whose entire professional universe seemed to exist exclusively inside Wise. No 'before Wise,' no 'outside Wise,' according to his LinkedIn, no reference points beyond the company's internal reality in his questions and responses. Now, I have over fifteen years of experience: senior roles, well-known global companies, different industries, different cultures, different kinds of problems. The kind of experience that usually helps people see patterns instead of rules. And that's when something uncomfortable clicked. This wasn't really an interview, it actually felt more like a competition disguised as process. There's a very specific look someone gives you when they can't map your experience to their internal playbook but can't admit it. Instead of curiosity, it turns into something else. The unspoken conclusion is simple: 'I don't understand this, therefore it's not relevant.' That's usually the moment when things become clear. Certain people end up acting as gatekeepers, not because they're looking for the best person, but because they're looking for someone familiar. And judging by conversations with people in my professional circle, my experience wasn't unique. But in a strange way, it's probably fair they didn't hire me. When a company is really looking for a reflection rather than perspective, experience stops being an asset and starts being a liability. And in that case, it's better for both sides to walk away early, even if the process pretends it's about something else.

Confirmed questions1 question
  • Can you discuss your past work experiences and any challenges you've faced?
Wise logo
Wise

Product Lead

Product · a year ago

Lead Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Phone screen Phone screen
Interview formats
Behavioral

It started with a recruiter call, then a call with the hiring manager. After that, I spoke with some cross-functional leads and then a leadership call. Mostly, it was about telling stories of my past experiences and accomplishments. They asked a few hypothetical questions too, really digging into my decision-making, motivations, and the reasoning behind my choices. There wasn't any live problem-solving, workshops, case studies, or homework involved.

Confirmed questions2 questions
  • Can you share an instance where you influenced a key metric?
  • What led to your departures from your previous two positions?

Wise Product Manager Interview Questions

Quoted word for word from Wise interview reports.

Considering we're looking to launch a product in one of three countries with identical market segment sizes, what factors should guide our decision on where to launch?

Read reports

What criteria do you use to determine the success of prototype testing and proceed with development?

Read reports

Given these user flow screens, what strategies would you propose to enhance conversion throughout the entire flow?

Read reports

What metrics or indicators would you use to determine the success of a product you developed?

Read reports

For one of those products, can you walk us through its history? We'll choose which one.

Read report

When presented with multiple design choices by a designer, how do you select the optimal one?

Read report

As a Product Manager, what are your thoughts on improving The Weather Channel's offerings in the USA and how would you tackle the competition?

Read report

Were there any specific questions related to the payments role? The questions were quite specialized, not general industry knowledge.

Read report

Can you share details about a past feature release, including the rationale behind its implementation and its ultimate impact?

Read report

Formats, difficulty and experience

Across all 82 Wise interview reports.

Interview formats

Behavioral 47.4%
Technical 30.6%
Case 10.4%
Presentation 9.2%
Other 1.7%

Interview difficulty

Easy 17.1%
Average 63.4%
Difficult 19.5%

Candidate experience

Negative 41.5%
Positive 40.2%
Neutral 18.3%