Engineering applicants have rated the interview process at BaubleBar with 2 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 37.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Engineering roles take an average of 26 days to get hired, when considering 2 user submitted interviews for this role. To compare, the hiring process at BaubleBar overall takes an average of 21 days.
Common stages of the interview process at BaubleBar as a Engineering according to 2 Glassdoor interviews include:
Group panel interview: 25%
Phone interview: 25%
One on one interview: 25%
Personality test: 13%
Skills test: 13%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 4 weeks. I interviewed at BaubleBar (New York, NY) in Jun 2015
Interview
I was not actively looking, but found an interesting post from recruiter so I applied, then contacted by the recruiter to set up the phone screen with HR.
HR is a very nice person. Typical phone screen with HR just want to make sure you are a normal person.
First in-person is with the CTO, who is a very energetic person with a lot of enthusiasm in what he is doing. This is a big plus to me. We talked about some high level design and my past experiences. Then HR showed me the office.
Second in-person includes 3 rounds. First round is with an engineer in a coffee shop. We had some technical questions and chats about my past experiences. Second round is with 2 engineers. To me this round focuses more on culture fit. Then the last round is with CTO again and he wanted to make sure I don't have other questions.
I applied through a recruiter. The process took 3 weeks. I interviewed at BaubleBar (New York, NY) in Oct 2014
Interview
After a brief phone call, I met with the Director of Engineering at a coffee shop. We had a relaxed conversation about my experience, what I wanted to improve on the website, and how I would go about doing that. The interviewer spoke candidly about his experience, what he planned on improving, and how I would help with that process. After that round, I was called in to meet everyone on the team, which took a bit long, but was a great experience over all. I accepted an offer a few days later. There were no whiteboard exercises as they had already seen plenty of my code, articles, and projects.