Wolt Senior Developer interview questions

First, I had an HR call with basic questions, such as my expectations, questions about my background, and the role. After that, I had a 90-minute leadership interview with two engineering managers, where we discussed the challenges I’ve faced in my career and went over my past projects. Following that, I was given a take-home assignment. The assignment itself wasn’t particularly complicated, but it was really unclear what criteria they were using to judge it. I suspect they have a set list of tests or scenarios they use to evaluate the assignment, and it often comes down to luck whether you happen to address exactly what they are looking for. You might miss an edge case and fail, yet they don’t seem to evaluate the overall structure of the project, the approaches you used, or your thought process. I was failed based on the criticism that I hadn’t implemented a certain scenario, when in fact I had, and I documented it in the README. Any reviewer who had at least read the README would have seen that I had indeed done it and that I had multiple test cases covering that exact scenario. Overall, the experience was great until the take-home assignment stage. The recruiter and the engineering managers I met left a positive impression on me, but the assignment stage really soured the experience, especially since I spent a lot of time on it and put significant effort into the documentation.

Following that, there was a session with the Merchant Group engineers, who oddly insisted on a functional programming approach, despite it not being mentioned in the problem statement. The interview process itself was disappointing—not focused on evaluating relevant skills, but instead fixated on hearing specific answers. Thankfully, I didn’t doubt my abilities and ended up receiving offers from several Berlin-based companies I was applying to that summer, including DeliveryHero, Miro, Personio, and HelloFresh.