Wizeline logo

Wizeline Interview Questions
& Process

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

Based on 172 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
62.2% Positive experience

Which role are you interviewing for?

30 roles · 172 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Wizeline.

Showing 4 of 172
Wizeline logo
Wizeline

Senior Android Engineer

Engineering · nearly a year ago

Senior Average Positive experience Accept offer 2 rounds
Interview process
Recruiter call Technical screen
Interview formats
Behavioral Technical

It was a quick process with HR and then straight to the technical team, with technical questions and questions about my last few years of experience. They asked about what I do day-to-day and also what I would do in certain situations.

Confirmed questions2 questions
  • What has your experience been like in recent years?
  • What is your experience with large-scale applications?
Wizeline logo
Wizeline

Publishing Specialist

Other · nearly a year ago

Entry Average Negative experience No offer 3 rounds
Interview process
Recruiter call Take home Presentation
Interview formats
Behavioral Presentation

The interview process was fast but it wasn't super clear what the job was actually about. It started with a recruiter call, then I had an assessment, and finally I did a presentation to the team. The recruiter did a good job setting expectations and pushing for me, saying I could fit even though I didn't have direct publishing experience. But the interviews showed some internal confusion: they kept asking about my lack of publishing background and how I handle problems, even though the recruiter had framed my strategic experience as a plus. One person straight up said they weren't looking for my background and that the team wanted to change the job title, which made it seem like they weren't sure what they wanted in the role. The assessment went well, but they never really defined what the job entailed. The recruiter later admitted there was a lot of confusion internally about what the role should be, which made sense given the mixed feedback.

Confirmed questions1 question
  • What's your approach when dealing with colleagues who are unwilling to collaborate?
Wizeline logo
Wizeline

Product Manager

Product · nearly a year ago

Mid Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Technical screen Presentation Offer
Interview formats
Behavioral Case Presentation

Everyone I talked to was really nice and made me feel comfortable. But, it seemed like the team members didn't communicate super well with each other. I told them in the first chat that I hadn't done a specific thing before. They still made me go through the whole process, and then at the very end, they told me I didn't get the job because I lacked experience in that one area.

Confirmed questions1 question
  • What's your approach to handling situations where two stakeholders have completely opposing views on the product?
Wizeline logo
Wizeline

UI Designer

Design · more than a year ago

Senior Average Neutral experience No offer 3 rounds
Interview process
Recruiter call Presentation Background check
Interview formats
Behavioral Presentation Technical

I was contacted on LinkedIn and the overall experience was good. The first interview was with a recruiter where we discussed average questions, my years of experience, background, tools, and salary expectations. Then, I had a second interview with two design leads where I presented a project for an hour. Finally, there was a cultural fit interview. They initially mentioned a 3-interview process, with a possible fourth if the client required it. However, they later proposed a 1-hour 'challenge' to assess seniority, which wasn't discussed upfront and felt like micromanagement, unlike typical hiring processes. This raised a red flag, and I decided to withdraw from the process. I suggest improving the hiring process to prevent wasting candidates' time.

Confirmed questions4 questions
  • Can you share your years of experience?
  • Tell me about your background.
  • What design tools are you proficient with?

Wizeline Interview Questions

Quoted word for word from Wizeline interview reports.

Can you parse a string to check if it's a valid IPV4 address?

Read reports

Find the first word that does not repeat within a list of words

Read reports

Given an array of votes, print the candidate who received the most votes.

Read reports

What are the differences between an array and a slice in Go?

Read reports

Can you create a function that takes a list of words and identifies anagrams within it?

Read report

Why choose between requesting data in an endpoint using a query string or URL parameters like url/{id} versus url?id=x?

Read report

Write an SQL query with aggregations, joins, and filters, given a relational database model.

Read report

Can you write a method to find the intersection between two lists, A and B?

Read report

How would you refactor a Python (Flask) application that reads data from a CSV file?

Read report

Formats, difficulty and experience

Across all 172 Wizeline interview reports.

Interview formats

Technical 33.6%
Behavioral 28.5%
Coding 22.6%
Presentation 6.8%
System Design 5.1%

Interview difficulty

Easy 16.9%
Average 64%
Difficult 19.2%

Candidate experience

Neutral 11%
Positive 62.2%
Negative 26.7%

Reports by job function

Engineering 127
Design 11
Operations 9
Other 7
Analytics 6
Sales 4