Follow-up tech interview
Hi!
I'd like some feedback on this. Got approached by a top company, got a coding phone interview, then an on-site interview, where all coding/tech questions really went well but one. On that one, I solved the problem in 30 sec. but the interviewer wanted an optimized solution. Let's say that I eventually got there but with too many hints. That was somewhat of a red flag because they'd like a follow-up phone tech interview to determine the final outcome.
So I will naturally prepare (I was a little rusty on algo, but I reviewed them as much as I could prior to the interviews - Gayle's book was very effective at that), but I wanted to get some thoughts about this situation.
It can at least two different things:
1) I have to do exceptionally well, not just good, to get an offer
2) They mostly agree that I can deliver, but want to make sure the questions I properly answered were not just luck. So answering good would be enough.
Either way, I will fully prepare and aim for an A+ on this, but I'd like to know if anyone got into that situation, how they prepared, how it went, etc.
I've been developing for many years, got some apps to be very popular across multiple platforms, no problems at all coding in C/Obj-C/C++/Java, very comfy with any data structures, but not the smartest / brightest / quickest when it comes to algo (although I usually always find a way, not necessarily the best way).
Thanks!
Jack
First, why do you think that all the questions went really well except for the one where you struggled? How do you know if you took more hints than other people on that question, and fewer on the others? Did the company *tell* you that you did well on all but that last question?
- Gayle L McDowell May 02, 2013In my experience, candidates have absolutely zero ability to understand how well they did in an interview. After all, they aren't privy to how well other candidates are doing, and that's what you'll be compared to.
Second, there are a lot of reasons why you might be brought in for additional interviews. It could be that you really struggled in one interview but did very well in other interviews. I doubt that's what it is. After all, what would one more interview tell them here that your other four or five interviews didn't?
It's more likely that something else is doing on:
-- There were some personality red flags that they need confirmed. For example, one interviewer thought you came off as arrogant.
-- They didn't feel you got enough questions on a particular topic (system design, coding, etc).
You're looking for an easy answer, and there isn't one. You're dealing with decisions by groups. Have you ever been in a meeting (even for a school project) where you were asked to make a decision, your team debated for a while, and ultimately put off making a decision (to get more info, etc)?
This happens for hiring decisions too. A bunch of people might sit around, some who want to hire you and some who don't (for any number of reasons), and then someone suggests "Why don't we bring him/her in for another interview?" And, just like that, everyone's mostly satisfied because that decision doesn't conflict with their views.