Taro Logo

Engineering Interview Experience - Bengaluru, India

June 1, 2012
Negative ExperienceGot Offer

Process

I was referred to Inmobi through an ex-colleague. I was called for an onsite interview. The schedule was for four 1-1 interviews. The interviews were to start at 11 am, I went there 10 minutes early. It's a startup so the office was pretty small with lots of activity going on. I could see people involved in discussions everywhere, the walls had posters detailing different scrum terms and diagrams related to scrum methodology. I was asked to wait in a room for the interviewer.

Round - 1: The interviewer came in half an hour late, he told that he was just informed about the interview and wasn't prepared for taking one. He started with general discussion on my experience, different styles of working (scrum, waterfall) etc. The abstract discussion went on for more than 15 minutes. After that he started a discussion on a problem which he said the company is facing currently, and wanted to know my approach in solving it. It was about managing user identification on a large scale ad serving system. The adserving system may get requests from different sites, with each request having a variable number of attributes (ID's was the term he used) uniquely identifying the user. He was not able to explain the exact problem for which he wanted a solution.

I had to ask lot of questions to understand the problem - firstly it was about how to have a unique ID to which all the ID's from requests from different sites get mapped. I gave some solutions, he said that's not the problem and asked how 'how will you solve it' if it was on a large scale. Here again he wasn't sure about what he is looking for - i assumed he wanted an architecture which can scale up and solve the user identification for different requests. I answered by telling a few approaches for persistence (NoSQL based) and serving (cache). He said - before you go to architecture tell me how many bytes would it take for an ID if the number of ID's were billions. I said if we use a binary sequential approach it would be log(number of users).

I proposed a few other options to reduce the number of bytes for the unique ID. This ended the interview. Duration was 30mins. Most of the discussion was abstract.

Round-2: Another round where the interviewer spent most of the time talking about my previous experience. He asked me to explain the architecture of my most recent project, which i explained. He asked one question regarding distributed transaction. If we have two web services exposed by two different systems which don't talk to each other, how would you implement a distributed transaction. This round went on for 40 minutes.

Round-3: This interviewer was also told about the interview last minute, but this was much better than the previous ones as it had some concrete technical problem instead of a discussion on abstract topic. In this round too, some time was spent on my previous projects. Questions were: How will you implement a spatial database to hold map data. How will you implement spatial queries. Given a set of unique points in a plane give an algorithm to find out maximum number of points which are collinear.

The fourth round was supposed to be with the CTO, I was told that he is not in office and I would be called for another discussion later.

I was called for the CTO discussion about two weeks later. After this round had a 15-minute telephonic round with the HR. HR asked me how excited I am to join Inmobi, what do I know about the company etc. HR also asked me if my current employer gives a better counter offer will I still join Inmobi. Two days later I get the offer by mail - which to my surprise offered me a pay less than my current salary :).

I think they should definitely improve on the interview process.

Questions

Give an algorithm to find the maximum number of collinear points given a set of points as input.

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the InMobi Engineering role in Bengaluru, India.

Success Rate

0%
Pass Rate

InMobi's interview process for their Engineering roles in Bengaluru, India is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral0%
Negative100%

Candidates reported having very negative feelings for InMobi's Engineering interview process in Bengaluru, India.

InMobi Work Experiences