Wizeline Software Engineer Interview Questions
& Process

I had two interviews and then on Friday I got 4 invitations for Monday and Tuesday of the next week. They didn't tell me what the interviews were about. On Monday, I had a technical interview with live-coding and it didn't go well, then I had another non-technical interview. The next day they cancelled both interviews and I asked for explanations via email since I had already arranged my schedule for them. I got a 'it didn't go well' as a response and an invitation to reserve a call for feedback. Lamentable professionalism.

It was a fast and well-organized process with four interviews happening in one week, each lasting 1-2 hours. Some interviews were later at night. The interviews were simple and conducted in a prepared environment without any code assistance.

So, I initially applied online back in March 2020. HR reached out and we did an HR screening. After that, I got a coding challenge on Codility with 3 problems to solve in about an hour, which was manageable if your algorithms were sharp. The next day, they said I passed and we scheduled a 90-minute phone interview that included QA and 2 coding questions (easy/medium difficulty). I got a bit flustered on the first coding question but managed to solve both with the interviewer's help. Then, we were supposed to move to an onsite interview, but everything got paused due to the pandemic. Fast forward to August 2020, a recruiter contacted me saying interviews were back on. After they checked with the engineering team, they mentioned they were actually looking for PHP or Go engineers, not Java (which I never specified I was). I clarified I'm a Software Engineer with PHP experience, so they sent a new Codility challenge, totally different from the first one. This time it was about optimizing existing code within an hour. I felt I could have done more optimization, focusing on readability and fixing bugs, and I only managed to fix two bugs. I noted a potential major refactor in a core part that I didn't have time for. Three days later, I asked for an update and learned I'd passed to a remote onsite interview, scheduled for the next day. The onsite had two parts: a 1.5-hour pair programming session focusing on debugging and adding a feature to a PHP API while considering scalability, and a 30-minute chat with the VP of Engineering covering soft skills. Later that day, I got the offer!