How Long Does It Take to Hear Back After a Wise Interview?
Wise publishes its interview rounds, but not its wait times. The careers site lists three steps: apply, interview, and offer. Candidates report a few weeks from the first call to a decision. Between rounds, a few business days is common.
Wise does state one thing clearly about replies. It says it does not give specific written feedback, as a matter of company policy.
Recruiters discuss the next steps instead, and give spoken feedback where they can. So expect a plain email rather than a written review of your rounds.
Timeline by Stage
| Stage | Typical wait | What is happening |
|---|---|---|
| After you apply | One to two weeks | A recruiter reads your application and reasons for applying |
| After the recruiter call | Two to five business days | The recruiter decides which role rounds apply to you |
| After a technical task | About one week | An engineer reads your code, tests, and notes |
| After the pair programming round | Three to five business days | An engineer writes up how you worked through the problem |
| After the product round | About one week | Cross team interviewers compare notes |
| After the final round | About one week | The recruiter gathers feedback and prepares an offer |
Wise publishes the format of each round, which helps you judge the waits. The backend pair programming round runs 60 minutes on HackerRank. Most of that is coding, with 5 minutes at the end for your questions.
The backend team writes Java. Wise says it tries to run the interview in the language you are most comfortable using. Tell the recruiter on the first call if that is not Java.
The backend system design round runs about an hour. Two Wise engineers join it, and you use an online collaborative whiteboard.
The engineering product round is different again. Wise also calls it the Product Mindset interview. It runs 45 to 60 minutes on Google Meet, or in a Wise office.
One or two people from other teams run it. Product managers lead it, and designers or analysts can join. It assesses five named areas: customer focus, impact and data, ways of working, cross functional collaboration, and communication.
A round with people from several teams takes longer to book. Allow extra days there.
Does Wise Send Rejection Emails?
Wise states its feedback policy in public. It does not give specific written feedback. Recruiters discuss next steps with you and give feedback where possible.
In practice that means a short rejection email with little detail. If you want reasons, ask the recruiter for a five minute call.
Wise also states that AI does not make hiring or rejection decisions there. It uses AI to summarise applications, help with scheduling, and improve job adverts.
Wise says recruiters review every application, every task submission, and every interview themselves. A slow reply means human review time, not an automatic filter. Wise asks candidates not to use AI notetakers, recording bots, or transcription assistants during interview rounds.
For the full round list by role, read What is the Wise interview process like?.
How to Follow Up
Email the recruiter who ran your first call. Wait five business days past any date they gave you.
With no date, wait ten business days after the round. Keep it to four sentences and ask one question.
Hi [Name], thank you for the [round name] on [date]. I am still very interested in the [role] team at Wise. Could you tell me where my application stands and what the next step is? I understand you cannot give written feedback, so a short call would work well for me.
Can You Reapply, and How Soon?
Wise does not publish a reapply rule. Six months is a usual waiting period for the same role at companies of this size. A different role can use a different set of rounds.
Wise publishes separate rounds for backend, front end, product management, and the engineering product round. So a rejection from backend does not decide a front end application.
One more detail helps while you prepare again. Wise says you may use AI to research the company and shape your stories, but not to generate code or answers during a live round.
What to Wear
Most Wise interviews happen on video. Wise says many of its interviews run on Zoom, and that you may be asked to meet in one of its offices instead.
The product round runs on Google Meet, so dress for video by default. A plain shirt in a solid color works well, and busy patterns blur on camera.
Test the link, the camera, and the microphone the day before. HackerRank rounds need a stable connection, so use a wired network if you have one.
For an office visit, clean trousers and closed shoes are enough. Wise does not publish a dress code, and a suit is not expected.
How to Prepare
- Practice pair programming under time. Sixty minutes on HackerRank is short, so rehearse with a timer. Grokking the Coding Interview teaches the patterns that make you faster.
- Prepare design questions about moving money. What to expect in the Wise system design interview lists the topics, and Grokking the System Design Interview covers consistency and scale.
- Build stories for the five product areas. Wise names them, so prepare one story each. Top Wise behavioral interview questions has the question list.
- Know why this company. How to answer why Wise shows how to link the mission to your own work.

GET YOUR FREE
Coding Questions Catalog

$123

$197

$72