Summary: Think Amazon SDE I interview with happier engineers. I did well on the interview but had little development experience. I interviewed for a Software Engineer position and was made an offer for Software Engineer in Test which I accepted. Interview process: -initial phone screen -2 day homework assignment -1 week homework assignment -technical phone interview -on site interview -technical phone interview #2 My interview experience: I had a great experience. It was awesome, although a bit nerve wracking waiting for the results of all the different phases. The response for the week long homework assignment took the longest. I think they are moving as fast as they possibly can given the volume of applicants and the small size of the company. From start to finish it was about three or four weeks. The on site interview was similar in difficulty to an SDE 1 interview I had at Amazon in Seattle. The biggest difference was the Opower team seemed like they were in a better mood. Part of that was probably due to the fact that I was better prepared for the Opower interview and solved the problems much more quickly than I did at Amazon. I think that was really the key. You have to get the questions right and you have to do it fast enough so that you can chit chat with your interviewers afterwards. I did well on all the questions, but I didn't have any "real" experience at the time despite being in industry for 4 years. Everything I had ever built (lame insurance software, low traffic government websites ) was stupid compared to the work they're doing at Opower (these are my words, not theirs). Opower offered me a position as a Software Engineer in Test instead of the Software Engineer position, and I was very excited to accept it. This place seems to be about as cool as it possibly gets. Giant videogame murals for wall art, no dress code, very friendly engineers, massages, it goes on and on. Interview preparation: -Study like you're going to Amazon - A week or two before your on-site interview, stop using Eclipse at work. Start using Ant + emacs (or some other editor). This really helped me nail the whiteboard coding parts because I knew exactly what to write. -care about the goal of the company -read their development blog -don't pretend to know things