Bold Penguin logo

Bold Penguin Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 6 interview experiences · FREE TO READ

3 Rounds average
Average Typical difficulty
33.3% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Bold Penguin.

Showing 3 of 6
Bold Penguin logo
Bold Penguin

Software Engineer

Engineering · more than a year ago

Mid Easy Positive experience No offer 3 rounds
Interview process
Recruiter call Technical screen Onsite Offer
Interview formats
Technical Coding Behavioral

Got referred for the role. They said the process is way shorter now, all remote. Took less than a month total. First up was a basic screening call about my background and skills. Got an email with a PDF outlining the whole process. Then, a technical interview for a Ruby dev role. It was a 1-hour live coding session with two senior engineers. Pretty practical, no crazy DSA stuff. Last was a behavioral chat with the hiring manager and product owner. Nice conversation. Didn't get an offer, but heard back pretty quickly. Overall, it was a smooth, pleasant experience.

Confirmed questions2 questions
  • Could you describe implementing classes and methods for a real-world game, focusing on a Test Driven Development approach?
  • How did you approach object-oriented design during the coding exercise?
Bold Penguin logo
Bold Penguin

Senior Software Engineer

Engineering · more than a year ago

Senior Average Negative experience Decline offer 5 rounds
Interview process
Recruiter call Phone screen Take home Onsite
Interview formats
Technical Coding

The interview process at Bold Penguin felt a bit off. Their compensation was below market. Most interviewers, aside from HR, were white men with anime posters in their home offices. The process involved a take-home assignment, followed by three phone screens (one HR, two technical), and then an onsite interview. They seem to look for candidates with over 5 years of Ruby/Rails experience, but then their questions push for code that isn't standard Ruby.

Confirmed questions1 question
  • Write non-idiomatic Ruby code, avoiding specific built-in methods.
Bold Penguin logo
Bold Penguin

Software Engineer

Engineering

Mid Easy Negative experience No offer 2 rounds
Interview process
Take home Technical screen
Interview formats
Coding

The interview process was reasonable and well-thought-out with polite interviewers. However, the scheduling and communication from the company were terrible. It involved a couple of video calls with engineers and a take-home project. The questions were good and targeted specific skills and experience. But, the main point of contact was unresponsive and insulting. They canceled final-round interviews at the last minute without a clear explanation, showing no respect for candidates' time.

Confirmed questions1 question
  • Given a project with starter code, implement the requirements and write test code.

Bold Penguin Software Engineer Interview Questions

Quoted word for word from Bold Penguin interview reports.

Write non-idiomatic Ruby code, avoiding specific built-in methods.

Read reports

Given a project with starter code, implement the requirements and write test code.

Read reports

Could you describe implementing classes and methods for a real-world game, focusing on a Test Driven Development approach?

Read reports

How did you approach object-oriented design during the coding exercise?

Read report

Can you tell me about a challenging problem you encountered and how you resolved it?

Read report

Formats, difficulty and experience

Across all 6 Bold Penguin interview reports.

Interview formats

Coding 38.5%
Technical 30.8%
Behavioral 23.1%
Presentation 7.7%

Interview difficulty

Easy 33.3%
Average 50%
Difficult 16.7%

Candidate experience

Positive 33.3%
Negative 50%
Neutral 16.7%