1 Screening with HR 1 Screening with team leader 1 coding challenge 1 meeting with 4 people to explain your challenge The whole process didn't take longer than 3 weeks. It was smooth and reasonable. There were no such things as tough questions. Like mentioning errors you made in the past, and how you solved it. Or any like that.

process: external recruiter -> hiring manager -> 4 online technical sessions -> 4 onsite technical sessions. Describing whole experience exceeds glassdoor chars length limitation. So here are a few important points. I was interviewed for Lewisville, TX - They are corporate; don't think they are startup given their growth; with a very slow delivery pipeline. This doesn't mean bad, just align expectation. - However, given their size and spread, their interview process deserves to be improved a lot. For such a company, I've definitely expected a much better interview experience. Also, most of the things are handled by the external recruiter and she is great and really caring about her candidates. -- They don't have any real structure for interviews. Plan was online sessions will be pure technical and onsite will be mostly discussion and meeting team. But the reality was different. One interviewer for the online session (manager) came totally unprepared and interview was over like in 10mins. -- I showed up 15mins ahead of the interview (though reached 25mins ago in the premise). I was taken in ~30mins after first interview scheduled time; and no explanation whether it was deferred or anything else. No apologies either. -- Among 4 hours on-site, I got like 5 minutes to ask questions. The plan was the all technical assessment will be online (hence 4 sessions there) and onsite it'll be just about meeting the team and getting a sense of the workplace. But rather it was like the online technical session didn't happen, and was kind of surprising! It was also stressful given flight delay and lack of sleep. - Their Lewisville office is a big premise but mostly call center and other non-eng. sections. There are only a few engineers there. It's a satellite office for eng. So you may not get real eng./tech culture there. - They use rails so try to learn as much as possible and as deep as libraries and implementation details. - Practicing whiteboarding will be helpful though not sure you'll do that much in real life as they mostly collaborate with other offices (so a software-based diagraming will be more useful). I should have done better in this regard though. Suggestions to interviewers: - Have a clear agenda and set up expectations for an interview so that all parties understand what to expect. - Allow candidates to ask questions. An interview is not a one-way evaluation. - When you get in the room, of course, say hi, introduce yourself, set a friendly tone and go on asking hard questions. This was quite big 'no' to me. While I was very excited during the first session, by end of the 2nd session (given the interviewer is the manager) I've already made my mind about not working here. - Respect the time of the candidate and if there is a delay, please communicate that as soon as possible. - Please try to articulate your expectation as clearly as possible. I had real trouble to understand the expectation of the interviewer. (I was asked to create a facebook newsfeed experience. based on initial clarification, it seemed UI. when I was working on it, I was asked about its persistence; when I was working on it (db & model), I was asked to do (draw) interfaces between them (ui->model->db); then en-route of that, I was asked to design notification system. It was really tough to follow along and do everything in ~20mins.). - Thanks for lunch.