Coolblue Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 27 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Coolblue.
Coolblue
Software Engineer
Mid Average Neutral experience Decline offer 4 rounds
Interview process
Recruiter call Technical screen Take home Technical screen
Interview formats
Behavioral Technical Coding
The interview steps were pretty straight forward. It started with an online meeting with the recruiter, followed by another online meeting with the recruiter and a person from the technical team. Then, I had a take-home assignment, and finally, a technical interview. A big downside was the time it took between each interview, which was almost 2 weeks between each step.
Confirmed questions2 questions
- Can you tell me about software development methodologies and principles?
- What are your thoughts on testing strategies like TDD?
Coolblue
Software Engineer
Senior Easy Positive experience Accept offer 5 rounds
Interview process
Recruiter call Technical screen Take home Technical screen Offer
Interview formats
Behavioral Technical Coding Presentation
Got a reply back in under a week after submitting my application online. The whole thing wrapped up in about two weeks. Started with a quick intro chat with the recruiter, who was really professional and knew their stuff. They got straight to the point, which was great. Then, I had an interview with the manager focusing on culture and soft skills. After that came a take-home task, followed by a code review with some senior engineers who were clearly experts. They were super focused on code quality and making sure I understood my work inside and out. The process ended with the recruiter letting me know the decision. Overall, considering how busy everyone was, it moved pretty fast, was a good challenge, and felt really comprehensive.
Confirmed questions4 questions
- Questions about soft skills focused on our work culture and how we approach work.
- There's a big emphasis on making sure we have a fun and friendly place to work.
- The technical interview questions were mainly about code quality and how deep your knowledge is.
Coolblue
Software Engineer
Entry Average Neutral experience Accept offer 5 rounds
Interview process
Recruiter call Take home Technical screen Offer Background check
Interview formats
Coding Technical Behavioral Other
The interview journey with Coolblue was long, stretching over three months. It started with an HR screening, then a managerial round, both of which went well. After that, I was given a take-home coding challenge, which I also passed. This was followed by a coding interview, essentially based on the take-home challenge, and again, I received positive feedback. An offer letter was extended and signed on September 13th. A cultural round also took place on November 12th, which was positive. But then, surprisingly, Coolblue rescinded my offer just three days before my start date. They said it was because I applied for another role within the company, which they saw as a sign of distrust. This happened after a lot of back and forth about relocating, salary, and regular talks with their relocation person, which took up a lot of my time. They could have brought up any issues earlier. Telling me this so late felt really sudden and not very professional. It was a bummer, but I guess it's good it happened before I started, as it showed some communication issues and that our expectations might not have matched up.
Confirmed questions3 questions
- What are some typical coding questions you ask?
- Can you describe questions related to design patterns?
- What kind of behavioral questions do you typically ask?
Coolblue Software Engineer Interview Questions
Quoted word for word from Coolblue interview reports.
“Can you discuss the pros and cons of using an ORM like Hibernate?”
Read reports →“Could you review the code in the provided Github link and give us your feedback?”
Read reports →“What are your thoughts on testing strategies like TDD?”
Read reports →“What are your thoughts on Agile content in general?”
Read reports →“How do you view the importance of quality and testing in applications?”
Read report →“can you explain your application of clean architecture in your code?”
Read report →“Can you tell me about software development methodologies and principles?”
Read report →“Were there questions about design patterns in your technical review, like composition versus inheritance?”
Read report →“Are there any problems or anti-patterns within the codebase, and if so, how would you address them?”
Read report →Formats, difficulty and experience
Across all 27 Coolblue interview reports.