Software Developer applicants have rated the interview process at Bloomerang with 3.3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 63.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Developer roles take an average of 14 days to get hired, when considering 3 user submitted interviews for this role. To compare, the hiring process at Bloomerang overall takes an average of 26 days.
Common stages of the interview process at Bloomerang as a Software Developer according to 3 Glassdoor interviews include:
Presentation: 33%
Phone interview: 33%
Group panel interview: 17%
Skills test: 17%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 2 weeks. I interviewed at Bloomerang (Indianapolis, IN) in Feb 2020
Interview
The process was an all-day interview with different groups of people, about different aspects of the company. There were technical and non-technical aspects to the interview which was good, because even the most tech-oriented job is going to have non-technical parts.
Interview questions [1]
Question 1
How would you react to someone modifying, or even removing, code that you had written?
I applied online. The process took 1 week. I interviewed at Bloomerang (Indianapolis, IN) in Mar 2020
Interview
Very quick and prompt with replies in setting it up. They did the online assessment first, which helped to more quickly assess the proficiency for the job. Likewise, the feedback was very quick.
Interview questions [1]
Question 1
The questions for the quiz covered a variety of topics and each question quizzed more than one quality. One required you to try out email correspondence with a coworker while solving a handful of bugs in their code.
I applied through an employee referral. The process took 3 weeks. I interviewed at Bloomerang (Lawrence, IN) in Jul 2014
Interview
I started with a phone interview with the COO. That went well, so we segued into a phone interview with the R&D team.
I went back the following week for an in-person interview. It took all morning, as I interviewed with several different people. I also attended a product meeting, where I got to see the various projects that were in the pipeline and see how priorities were determined.
I was invited out to lunch, but declined since I had to get back to my then-current job.
Interview questions [1]
Question 1
The interview had both personal and technical components, and included some practical work (writing pseudo-code). I don't remember any of the specific questions, though.