Engaged via an unsolicited LinkedIn request for interview. While I'm happily employed already, I thought I'd see what they had to offer. The initial phone interview was somewhat technical, lasted about 50 minutes (scheduled for 30), with the first 25 being the interviewer asking questions about my experience and resume. Nothing tricky, just what I'd put on the resume. T This interviewer was an electrical engineer with an iPad / iPod team. There weren't any technical questions except those derived from my resume. Next I did an in-person interview with 8 people, each for around 30 minutes, except for the lunch slot which was 1 hour (including a trip to the Apple cafeteria.) These interviews were highly technical, involved a lot of white-boarding, and are designed to see how a candidate thinks as well as what they know. It was clear that all the interviewers were very intelligent, and they came off as friendly and able to mentor other engineers. I would be please to work with them (except 1, who arrived late and was completely unprepared. He asked me for a paper copy of my resume (which I didn't have! Who brings paper to an interview these days? Every other interviewer carried an iPad and iPhone.) In summary, they will find the limit of your knowledge: be prepared for that, and answer their questions to the best of your abilities, but know your limits and state when you don't know an answer. Remember, they want to know how you THINK too. They will encourage you think and try and solve it on the spot given tidbits of knowledge. There was also one really excellent "scenario" question. I've elected not to share it. However, the majority of questions were on technical concepts coming out of my resume (tradeoffs in synchronous buck regulator design, I2C pullup sizing, bandwidth constraints, DRAM estimation) and my ideas of product development (describe the product design flow.) I also whiteboarded the exact same block diagram of a previous design I'd built for 3 or 4 of the reviewers, each who asked their own questions about design decisions, implementation, tradeoffs, testing, etc. In summary, I found the interview process challenging but enjoyable. I came away feeling like I could work with these guys and really learn something. However, I did get the impression that, without years of background in product development, one would be stuck at a "junior" level for several product development cycles.