Aller au contenuAller au pied de page
  • Emplois
  • Entreprises
  • Salaires
  • Pour les employeurs

      Boostez votre carrière

      Découvrez votre salaire potentiel, décrochez des emplois de rêve et partagez vos témoignages de manière anonyme.

      employer cover photo
      employer logo
      employer logo

      Coolblue

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Coolblue | Offres d’emploi chez Coolblue | Salaires chez Coolblue | Avantages sociaux chez Coolblue
      Entretiens chez CoolblueEntretiens d’embauche pour Senior Software Developer chez CoolblueEntretien chez Coolblue


      Glassdoor

      • À propos
      • Récompenses
      • Blog
      • Nous contacter
      • Guides

      Employeurs

      • Compte employeur gratuit
      • Centre employeur
      • Blog pour les employeurs

      Informations

      • Aide
      • Règles de la communauté
      • Conditions d'utilisation
      • Confidentialité et choix publicitaires
      • Ne pas vendre ni partager mes informations
      • Outil de consentement aux cookies

      Travailler avec nous

      • Annonceurs
      • Carrières
      Télécharger l'application

      • Parcourir par :
      • Entreprises
      • Emplois
      • Lieux

      Copyright © 2008-2026. Glassdoor LLC. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Glassdoor LLC.

      Entreprises suivies

      Tenez-vous au courant des dernières opportunités et profitez de conseils d’initiés en suivant les entreprises de vos rêves.

      Recherche d’emplois

      Obtenez des recommandations et des mises à jour personnalisées en démarrant vos recherches.

      Entretien pour Senior Software Developer

      29 mai 2019
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien difficile

      Candidature

      J'ai postulé via la recommandation d'un employé. Le processus a pris 2 semaines. J'ai passé un entretien chez Coolblue

      Entretien

      1) First we have a skype phone talk with HR. It was about who am i? what am i doing? Why i want this job? ..etc Easy phase 2) After phone call i got second interview two days later with HR and a general manager. The second interview was basically about my former/current experiences,hobbies etc.. Easy phase 3) The important one was the third interview. A week later i got third interview which was technical and i guess the most important one. I had interview with two team lead guys. Bruno and Wendil. (sorry for misspelling if there is one). The technical part was basically like that. First they give you a github repo address, you download it to your local, then share your screen with them. Then you begin talking about the project. What can be done to design it better? If there is any bad implementation , what can be done and why ? They expect you know SOLID,Defensive Programming,Dependency Injection,Sql injection problems in codebase ...etc . But the weird part was there was a code which connect database in the ui project. They asked me what can be done to do it better? I solved like the below a) Make a class library for Data entity layer(To connect db, make crud operations) b) Create a new class library for Business Layer.(This layer is for my business logic,rules. Also make connection between Entity layer and ui layer. I make interaction between Business and Entity via interfaces. So our projects would be loosely coupled. If i want to change my DB provider to another provider in the future, there will be no change in my business layer. That makes our codebase robust,flexible ...etc I explained all that stuff to them. In the interview they said good,ok , we got it. Some answers like that. I never got any negative comments in the interview. Although when they return to me, they said i did not do well. Especially in a question (the former question i described above ) i create new project, violates single responsibility. That is not an approach of senior developer... some comments like that. Actually the interview was not bad for me. Also in the interview i got responses like ok,good,we got it. But when they returned to me the answer was a bit different :) Anyway it was an experience for me.

      Questions d'entretien [1]

      Question 1

      They give you a github repo, then you try to explain the codebase to them. What can you do to design it better? Any problem or anti-pattern in codebase?
      Répondre à cette question
      10

      Autres retours d’entretien d’embauche pour un poste comme Senior Software Developer chez Coolblue

      Entretien pour Senior Software Engineer

      28 févr. 2026
      Candidat à l'entretien anonyme
      Rotterdam
      Aucune offre
      Expérience négative
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Coolblue (Rotterdam)

      Entretien

      Je solliciteert eerst online met je CV en een enthousiaste motivatie via de werken-bij website van Coolblue. Daarna volgen er één of twee gespreksrondes met een recruiter en je toekomstige team, waarbij je vaak ook een praktijkgerichte case oplost. Het proces wordt afgesloten met een «cultuurklik» om te kijken of je echt bij de bedrijfscultuur past, gevolgd door een officieel aanbod.

      Questions d'entretien [1]

      Question 1

      Vertel eens over een moment waarop u een meningsverschil had met een collega of leidinggevende. Hoe heeft u dit opgelost?
      Répondre à cette question

      Entretien pour Senior Software Engineer

      5 janv. 2024
      Employé (anonyme)
      Offre acceptée
      Expérience positive
      Entretien facile

      Candidature

      J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez Coolblue en nov. 2023

      Entretien

      I got a response less than a week after applying online. The whole process took about 2 weeks. First was an introductory call with the recruiter. Professional and definitely knows his stuff. Didn't beat around the bush, which I really liked a lot. The second was an interview with the manager and this was more a cultural and soft skills interview. The third was a take home assessment afterwhich was a code review interview with senior developers who really know their stuff. They cared very much about code quality and ensuring you understand what it is you're doing exactly. Finally was a call with the recruiter informing of the decision. All in all, based on availability, the process was very quick, challenging, and thorough

      Questions d'entretien [1]

      Question 1

      Soft skills questions were centered around work culture and work ethic. There is a huge focus on ensuring a fun and friendly work environment. Tech interview was centered around code quality and knowledge depth e.g. the decision for going a certain approach so make sure to think long and hard about it
      Répondre à cette question
      3

      Entretien pour Senior Software Engineer

      26 juill. 2023
      Employé (anonyme)
      Rotterdam
      Offre acceptée
      Expérience positive
      Entretien difficile

      Candidature

      J'ai postulé en ligne. Le processus a pris 4 semaines. J'ai passé un entretien chez Coolblue (Rotterdam) en juill. 2023

      Entretien

      Interview consists of 4 steps. All the people I've met during the process were friendly and helpful. There might be some differences in your case but here how it goes. First step is a short chat with the recruiter about your background and expectations that lasts about 15 minutes. Second step is an extension of the first. For about an hour, you will be asked more in-depth questions about your past experiences with follow-ups. Additional to the recruiter, a development manager will be present in the meeting. I advise you to think about your stories beforehand and be honest. Third step is the techincal case-study. You will be given a project with requirements and a deadline. I advise you to aim for a clean code and utilize SOLID principles, architectural and design patterns. Last step is the code review. Subject of the review will be the project you've submitted in third step. This is your chance to get to know some of your potential team members. Don't get lost in your thought process. Just calmly justify your decisions, brainstorm with the developers, respect the feedback and communicate clearly. The recruiter will set up another meeting to let you know about the outcome of the interview (in my case there was a feedback which is cool). Good luck!

      Questions d'entretien [2]

      Question 1

      Mentoring colleagues, communicating with your manager, strengths and weaknesses, self sustain, influencing others, BDD
      Répondre à cette question

      Question 2

      Reasons behind design, architecture and algorithm decisions
      Répondre à cette question
      6