Glassdoor users rated their interview experience at Coolblue as 100% positive with a difficulty rating score of 4 out of 5 (where 5 is the highest level of difficulty). Candidates interviewing for Senior Software Engineer and rated their interviews as the hardest, whereas interviews for Senior Software Engineer and roles were rated as the easiest.
The hiring process at Coolblue takes an average of 30 days when considering 1 user submitted interviews across all job titles. Candidates applying for Senior Software Engineer had the quickest hiring process (on average 30 days), whereas Senior Software Engineer roles had the slowest hiring process (on average 30 days).
Applied via LinkedIn, and got a response via email. Sent CV and cover letter and got a response some weeks later. Scheduled a intro meeting with recruiter and did not receive feedback
Interview questions [1]
Question 1
Tell me about yourself, what are your best strengths
I applied online. The process took 2 weeks. I interviewed at Coolblue (Frankfurt am Main) in Jul 2024
Interview
Ein simples und ungezwungenes erstes Kennenlernen.
Nach einer kurzen Vorstellungsrunde hatte der Recruiter ein paar einfache Fragen zu meinem Lebenslauf, ich konnte im Anschluss Fragen zu Unternehmen und Position stellen.
Zum Ende des Gesprächs wurde eine erste Rückmeldung nach ca. 2 Tagen angekündigt.
Rund 10 Tage später hatte ich noch keinerlei Feedback erhalten und eine Mail an den Recruiter verschickt.
Er besuchte nach weiteren 10 Tagen zwar nochmal mein LinkedIn Profil, hat mir aber nie geantwortet.
Absolut keine Empfehlung wenn so mit Bewerbern umgegangen wird.
Interview questions [1]
Question 1
Hast du Führungserfahrung?
Welche Teamgrössen hast du bereits geleitet?
I applied online. The process took 3 weeks. I interviewed at Coolblue (Amsterdã) in Apr 2023
Interview
The first interview was with one of their HR staff, Eva. Despite being unwell, she was warm and the interview went smoothly.
Afterward, they sent me a task. It involved implementing a solution for a complex TSP problem using several microservices.
Following is their response:
Positive
1) The solution is complete in terms of the functionality and features it implements.
2) The parts that are tested cover sad-flows as well as some happy-flows.
Points of improvement
1) The code contains a lot of duplication for the different implemented cases. A cleaner solution would have been to put common code in an abstract class and use it as much as possible.
2) The implementation of the different methods in helpers.py do not re-use logic but instead re-implement the distance calculation, and also contain bugs in them (time = distance / speed, not speed / distance).
3) The messaging service is implemented in an async way, but the API is not. Making both sync or async looks like a more logical step.
4) The code uses typing and good formatting habits in some places, but skips it in some places where typing would make the code a lot easier to understand.
Overall, they rejected me due to the issues mentioned in the improvement section. Although the API section was optional and I completed it, they did not take it into consideration.
Interview questions [1]
Question 1
1) Describe yourself.
2) Tell me about one of your failures. How did you handle it?