NOTE: I am not going to give away the exact questions that were asked. However, I will try to give enough details that will help with your interview preparation and also give you a sense of what to expect. Application: I applied online and one of the recruiters contacted me after a couple of weeks. I had two technical phone screens and an onsite interview. First phone screen: Shortly (~20 mins) before the first phone interview, the recruiter sent me a pdf file with code for two programs in it. The recruiter asked me to read and understand what the code does before the interview. For the next 20 minutes I read the programs. The first one was very simple string manipulation program (took about 5 mins to understand) while the second one was a bit more involved (took about 15 minutes to understand). During the phone interview, the interviewer asked me what the program does and how I would improve it. Then I was asked to write a small program in an online collaboration tool (which the interviewer had access to). Again, it was a relatively simple program related to string manipulation. A couple of days later, the recruiter emailed me that I did well in the first interview and that they would like to do another phone screen. Second phone screen: The interviewer asked me a design question (i.e The question was related to designing a suitable data structure(s)) for a specific task. The interviewer gave all the details on what the task is and what the requirements were). This was not too complicated but it would require a good understanding of some basic data structures and algorithms (HashTables, Priority queues/Heaps and linked lists (single v/s double), and basic search structures like binary search tree. Nothing too complicated. A couple of days later, I was invited for an onsite interview. Onsite Interview: I met with four engineers (for 1 hr each). In each interview, I was asked one coding question and one design question. The coding questions were not too complicated (i.e they do not require any 'aha!' insights - like the questions some of the other companies ask). However, the design questions were a bit intense. The design questions were related to the work currently being done by the team I was interviewing for (just simplified versions of some of the real problems they solved). I did a reasonable job here but now that I look back, I probably said gave some totally ridiculous answers :). The engineers were very polite and extremely nice. They were very understanding. [My advise to anyone applying is to focus on your coding skills first and once you know the team you are interviewing with, do some research in the areas and educate yourself. Read the white papers, look at any open source implementations etc..If you are a complete novice in that field, don't bother applying - because you will certainly fail the interview!] The recruiter called me a couple of days later and politely told me that I did not make it !. I felt dissapointed but again, the whole experience made me respect Hulu a lot more. It has incredibly smart and good engineers and excellent recruiting team