*Agree w/ using the SAR format... particularly the outcomes are a big deal. First, if you aren't looking up what questions they are going to ask on the interne

*Agree w/ using the SAR format... particularly the outcomes are a big deal. First, if you aren't looking up what questions they are going to ask on the internet you're doing it wrong. Obv, not every company has had people post the questions online, but if they're up you should read through them. When you tell your stories, make sure each story has a beginning, middle, and end... too often people lose track of their point towards the end and just keep on going on. Depends on the company, but dropping the names of packages and frameworks gives companies some familiar ground to evaluate you. The guy that hired me at my last company actually referenced that as a deciding factor for him. I think we can all admit there is a trendiness to our work sometimes. It's also really important to force the interview into a conversation... you need to be asking questions throughout the process as well, and making them have to think about how they should be impressing you too. You should be "Interviewing the Interviewer"... This is important because talented people are more worried where they will end up for a few years. It's also a signal that you aren't desperate.