Wolt logo

Wolt Software Engineer Interview Questions
& Process

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

Based on 51 interview experiences · FREE TO READ

3.3 Rounds average
Average Typical difficulty
51% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Wolt.

Showing 3 of 51
Wolt logo
Wolt

Software Engineer

Engineering · nearly a year ago

Entry Average Neutral experience Decline offer 4 rounds
Interview process
Recruiter call Technical screen Take home Technical screen Onsite
Interview formats
Behavioral Technical Coding

Had a recruiter call first. Then interviewed with the tech team about my experience and their dev culture. After that, I had a test assignment, which was pretty well done, but I didn't get great feedback. Then a third interview focusing on the assignment, and finally a fourth interview to close things out. They mentioned on-call rotations really late, in the last interview, which was a bummer and kind of ruined it.

Confirmed questions1 question
  • Can you describe a time you had a conflict with a colleague regarding a technical solution and how you handled it?
Wolt logo
Wolt

Software Engineer

Engineering · nearly a year ago

Senior Average Positive experience No offer 5 rounds
Interview process
Recruiter call Technical screen Take home Technical screen Onsite
Interview formats
Behavioral Technical Coding System Design

We had several rounds: first an HR call that went over time from 30 to 70 min. then a 90 min call with 2 engineers (staff and EM) to dive deep into past experiences. After that, a take-home assignment due in 7 days, requiring production-grade code with attention to packages, logging, resilience, and tests; it was tested against their suites and I was told passing all is rare. Then, a system design round (90 min) where 2 senior/staff engineers reviewed the take-home, asked unrelated tech questions, and gave a system design problem to prepare. Finally, a 60 min interview with a VP of Engineering or Director. The whole process was very professional, with good feedback and responsive HR. Overall a great experience.

Confirmed questions8 questions
  • Can you describe a project you're particularly proud of?
  • Could you share an instance of how you managed a conflict?
  • What's your experience with mentorship?
Wolt logo
Wolt

Software Engineer

Engineering · more than a year ago

Mid Difficult Negative experience No offer 3 rounds
Interview process
Take home Technical screen Recruiter call
Interview formats
Technical Coding Behavioral

The interview process was quite annoying and frustrating. The tech lead interview itself was pretty straightforward, using STAR-style questions. However, the technical 'home assignment' (Venue Opening Hours) was really complex, involving many annoying edge cases and string transformations, and it required code that was 'production ready'. I was told during the tech-lead interview that the assignment was expected to take about 20 hours of a candidate's time, which I found to be an unreasonable amount of effort. For someone unfamiliar with Kotlin/Ktor, this could easily take up to a week. I usually avoid interviews with such demanding tasks, and this experience reaffirmed that. On the positive side, the recruiters were responsive and followed up quickly.

Confirmed questions2 questions
  • Can you describe a project you're proud of that you found interesting?
  • What specific issues would you point out in a poorly written PR? Provide examples.

Wolt Software Engineer Interview Questions

Quoted word for word from Wolt interview reports.

Could you create an endpoint that takes a restaurant's opening hours in JSON format and outputs them as human-readable text?

Read reports

Can you design an application that displays the opening hours for places?

Read reports

Could you design the database and write a corresponding SQL query?

Read reports

What led you to choose GET or POST requests for your assignment, and what are the best practices associated with them?

Read report

In your opinion, what constitutes good code or a well-written program?

Read report

How would you address the shortcomings of the provided API and suggest an alternative design?

Read report

Can you explain how to expand on that question using the backtrack method?

Read report

For a specific feature, what variables (including their names and types) would you set up?

Read report

Formats, difficulty and experience

Across all 51 Wolt interview reports.

Interview formats

Technical 30.3%
Behavioral 30.3%
Coding 24.2%
System Design 9.8%
Presentation 3.8%

Interview difficulty

Easy 13.7%
Average 72.5%
Difficult 13.7%

Candidate experience

Neutral 17.6%
Positive 51%
Negative 31.4%