Software Engineer applicants have rated the interview process at Habito with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 75% positive. To compare, the company-average is 46.4% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 11 days to get hired, when considering 4 user submitted interviews for this role. To compare, the hiring process at Habito overall takes an average of 17 days.
Common stages of the interview process at Habito as a Software Engineer according to 4 Glassdoor interviews include:
Group panel interview: 29%
Phone interview: 29%
Drug test: 29%
Presentation: 14%
Here are the most commonly searched roles for interview reports -
I applied online. I interviewed at Habito (London, England) in Jul 2018
Interview
Really poor experience, think twice before applying here. Upon entering the office I was greeted with cold stares and no one greeted me properly. I was just told to wait in a seat.
Feedback after the interview regarding technical questions was worded in an incredibly unprofessional manner and was unhelpful.
Although the process was a dreadful experience I am somewhat thankful that I realized very clearly that I would never ever want to work in such a place.
Consisted of phone Screen and then an onsite.
Talked with a recruiter, then got to the applied platform that asked some basic work place competency questions in an interview format. For example the general list of questions that ask behavioural/situational questions like “what would you do if X and you wanted to do Y”,
I applied online. The process took 1 week. I interviewed at Habito (London, England) in Sept 2018
Interview
* Phone call with engineer: a casual discussion about our programming history/how we got into FP/stuff we're interested in.
* 2hr face-to-face - a technical interview and a tour of the office/discussion of the culture. The technical interview was split into two parts. The first part was quite an interesting architectural discussion, and the second a more traditional coding task.
Interview questions [1]
Question 1
Questions about architecture & a haskell programming task.