
bol Software Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 70 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at bol.
Software Engineer
The hiring process involves a CV screening to assess if you have a bachelor's/master's degree and less than 1 year of experience post-graduation, with a Java/Kotlin background. Then, there's an HR Assessment that includes personality, inductive logical thinking, and deductive logical thinking tests. Finally, a 60-minute first interview with an engineering manager will evaluate your assertiveness, self-starting ability, and core competencies.
- Can you tell me about your recent experience?
Senior Software Engineer
First I spoke with a recruiter to align on expectations. Then there was a code review, which was pretty straightforward for senior folks. The third round involved live coding, and I was given a sample scenario beforehand. I had to pass 5 unit tests, with the last two being a bit tricky. I managed to complete all of them. Even though I passed the technical parts, I didn't move forward because the position was filled internally. I've heard this happens quite often here. The whole process took about a month of my time.
- Could you describe your experience with live coding, particularly focusing on Java streams operations?
- How would you approach solving 5 unit tests during a live coding session?
- Tell me about your strategy for tackling the more difficult unit tests, like the last two in a set of five.
Software Developer
The interview process started with an HR interview. Following that, there were two online tests to assess character and problem-solving skills. Then, we had a code review session. After the review, I was given a project to develop (Mancala). Once I completed the project, I prepared for another interview, but they postponed it. Although I didn't mind and continued my preparation, they unexpectedly decided to halt the hiring process. After investing nearly two months in this process, I asked for feedback on my code, but unfortunately, no one provided it, which was quite disappointing.
- Regarding the code review, they shared their screen to show a notification system for order updates. They asked for suggestions on bug fixes, code improvements, and how to implement abstraction in certain areas.
bol Software Engineer Interview Questions
Quoted word for word from bol interview reports.
“Considering Mancala is a two-player game, is making the game generic, as in this implementation, truly necessary?”
Read reports →“Regarding Java 17, why are you not utilizing its features?”
Read reports →“Could you review this code snippet and tell me what might be wrong and how to fix it?”
Read reports →“Regarding the technical assignment, could you explain your decision not to use Spring Boot?”
Read reports →“In your technical assignment code, where did you implement the service class?”
Read report →“For the game assignment, how would you approach allowing more players to participate?”
Read report →“Do you have time for the next step on day xxx?”
Read report →“How do you provide feedback to others, and how do you react to feedback you receive?”
Read report →“How would you approach solving 5 unit tests during a live coding session?”
Read report →Formats, difficulty and experience
Across all 70 bol interview reports.