I don't how it feels to work in the company. But the, with a few pitfalls, the interview process is really good. Guys who are trolling the company should question themselves on their loyalty levels. Especially when they are at least calling you to an interview process that takes days (took three full days for me). I've uploaded my resume in almost every job portal and never got a call from a single company. Most of the private sector is now outsourcing the HR process and are encouraging a black market for employment. Most of the startups wouldn't even have a HR. Even in such scenario, with an employee strength of around 10 employees, they have a HR. So there is someone who can listen to you! Coming to the interview, it took me three days to complete the whole interview process like i said previously. The first day, I had a Written test which is mostly basic quantitative and English aptitude. Another half day was spent on HR interview on knowing about me. The second day started with a technical interview. I was surprised that the HR knew a lot about the intuition behind lot of techniques which employees rarely knew. All she asked was intuition behind different statistical and predictive modelling techniques. It really boosts your morale when your HR interviewer knows a lot about the intuition behind the work we are supposed to do. I have seen HRs working based on keywords. So the HR of this company will be beyond your expectations. The afternoon of the second day was domain interview by the CEO himself. He test your expertise to a very deep level, when it comes to domain. He just nails the interviewee with a lot of domain-based questions. I personally liked both of the rounds. The third day (and round as well) is the hardest part. You will be given real-time analytics dataset and will be asked to work on it using R. I don't want to reveal what the technique is as that's the best as well as the worst part of the interview. Being a fresher, we are normally trained in implementing several independent analytical techniques. Combining it altogether into a single problem solving task might be known to an employee who worked for at least an year, for at least that particular project. Being a fresher it became a nightmare for me. It took a full half-day to understand what that project was all about. And I wasn't given any time horizon to complete the task. Had it been an internship, I would have done better. But the time pressure was intense and I failed in the coding test even though I was fairly proficient in R. So my only suggestion to the company is to go with internships covering meager travelling expenses rather than the coding round if you feel that the candidate has anticipated technical knowledge. Overall, this is the only interview I liked the most.